Most payment networks are islands. Fiber is being built to reach the biggest one next door. Fiber and Lightning share the same basic machinery, payment channels and multi-hop routing, so a Cross-Chain Hub can sit between them and link a payment on one network to a payment on the other. Say Alice holds assets on Fiber and wants to pay Bob, who only takes BTC over Lightning. The hub accepts her Fiber-side payment and makes the matching Lightning payment to Bob, and the two are tied together by the same cryptographic secret, so revealing it to settle one side is what settles the other. The hub provides liquidity and connectivity, not custody. It cannot claim the incoming payment without making the outgoing one, because if the condition is not met in time, both sides unwind. See what's being built on Fiber 👉 fiber.world/showcase

People ask why we'd build a Fiber SDK that helps projects beyond our own wallet. 🌱 Because we're not just building on Nervos, we're building for it. Bitcoin and Nervos are both first-class here, and shared tooling makes the whole ecosystem stronger. @NervosNetwork

$CKB’s token does two jobs at once. It’s money. It’s space and the rent system is properly clever. Here’s a clever bit of how CKB works. Its token basically does two jobs, and behind that sits one of the smartest economic designs in crypto. If you saw my storage video, you’ll remember the $CKB token isn’t just money, it’s also space. You lock CKB to store data on the chain, one token roughly equals one byte. So it’s gas and it’s storage, in one. Here’s where it gets interesting. CKB has two kinds of new supply. The first is just like Bitcoin, capped, halving over time, paid to miners. The second is a small, steady inflation, and it does a genuinely clever job. It works like rent. If you’re hogging loads of storage on the chain, that inflation charges you for it over time. You pay for the space you use. But if you’re just a long-term holder not using storage, you don’t want to be diluted by that. So there’s a shelter called the Nervos DAO. Lock your idle coins in it, and you earn back exactly what the inflation would’ve taken. So you’re not diluted. So the same token is Bitcoin-like and deflationary for holders, but charges rent to the people using space. Pretty clever

Paying for something with crypto shouldn’t have to mean publishing every purchase to a permanent public ledger. With payment channels, individual payments happen through signed balance updates exchanged off-chain. Thousands of payments can take place without creating thousands of public blockchain transactions. That offers a privacy benefit, though it isn’t perfect anonymity: routing nodes can still observe some information, and timing or network activity can reveal more. Our guide explains how payment channels reduce what gets published, and how the blockchain still protects the funds 👇 nervos.org/knowledge-base/ho…

⚠️ Notice for UTXOSwap Liquidity Providers: Withdraw Before 10 October 2026, 16:00 UTC UTXOSwap has announced that its service will shut down on 10 October 2026 at 16:00 UTC. If you have liquidity in UTXOSwap pools, remove all of it before this deadline. Please act well in advance. CKBA does not operate UTXOSwap and is not managing its shutdown. We are sharing UTXOSwap’s notice to raise awareness and help liquidity providers act in time. Read the original notice on the UTXOSwap website 👉 utxoswap.xyz/info/overview

A Fiber node can now run entirely inside a Chrome extension, with no separate app or server behind it. Chrome normally puts an extension’s background worker to sleep when it’s idle, which is a problem for a node handling payments. Fiber gets around this by running in a Chrome Offscreen Document: a hidden browser page that keeps the node active even when you close the extension’s popup. Under the hood, this setup requires SharedArrayBuffer access, cross-origin isolation, and a content security policy that permits WebAssembly and worker threads. For now, it’s limited to Chrome-based browsers. Firefox and Safari don’t yet support the same extension setup. Check the full build walkthrough👇 fiber.world/docs/build/brows…

The basic logic behind payment channel networks like Lightning or Fiber is based on a simple question: why involve the whole network? If two parties want to make 10,000 micro payments to each other, does the entire blockchain need to process all 10,000? With scaling solutions like Lightning and Fiber, it doesn’t. The parties commit funds onchain, then exchange signed updates to their balances directly. The blockchain remains available to settle the channel and enforce those balances if cooperation breaks down. This allows crypto to move quickly and inexpensively while preserving a non-custodial setup. Although not with without trade-offs, it’s arguably the best solution we have for permissionless micro and streaming payments—payment modalities that the machine economy will be built on. Dive deeper into the ins and outs of offchain payments with our latest guide 👇 nervos.org/knowledge-base/ho…

Rollups and payment channels both move activity off the base layer, but they optimize for different jobs. A rollup executes transactions in a separate environment, batches them, and submits data and proofs or state commitments to the base chain for verification or challenge. That makes rollups a good fit for applications where many users interact with shared state, such as decentralized exchanges, lending markets, and games. Payment channels take a more specialized approach. Two parties lock funds in an on-chain contract, then exchange signed balance updates directly. The blockchain steps in to open or close the channel, or enforce a valid balance if needed. If the goal is scaling a shared application, a rollup is a natural fit. If the goal is moving value between parties frequently, quickly, and inexpensively, payment channels are built for the job. Fiber brings that channel model to CKB. Try it yourself 👇 fiber.world/docs/build/inter…

$CKB’s builder scene is busier than you think. Dozens of open-source projects live on the CKBuilders tracker. Right now. The CKBuilders tracker just updated and there are dozens of projects on there. All open source, all being built on $CKB right now, and honestly, some of them are properly cool. There’s a top-down survivor game running on Fiber, actual gaming on a Bitcoin-secured payment layer. There’s a football prediction market where you can bet on matches. There’s a jobs marketplace, and a brand new orderbook exchange being built. That’s just scratching the surface. You’ve got inheritance vaults that lock funds on a timer, identity tools, proof-of-participation systems. Games, finance, identity, the lot. Now, to be fair, a lot of these are early, MVPs and proof-of-concepts, not finished mass-market apps. That’s not the point. The point is the builders are actually here, building. That’s what’s making CKB stronger.

Our CKBuilder tracker has now been updated! Check out the latest things the CKBuilders are working on, including a top-down survivor game on Fiber, a football/soccer prediction market, a work/jobs marketplace, plus 👀 a new orderbook DEX! And so much more. All open source, all on CKB 🔥 Check out the updated list below: github.com/Nervos-Community-…

Work continues on the Fiber SDK we've talked about. 🛠️ The aim is simple: let any Nervos builder add Fiber payment channels without solving the same problem from scratch. Still in development, and still something we believe in. @FiberDevs @NervosNetwork

$CKB explained to a kid. Bitcoin’s the unbreakable safe. CKB is the brain bolted onto it. This is my try to explain $CKB like you’re five. Imagine Bitcoin is a big, heavy safe. Most secure thing in the world. Everyone trusts it. But that safe can basically only hold money. It can’t run apps. It can’t run smart contracts. It’s a vault, and that’s it. Ethereum is the opposite. It can do the clever stuff. It’s just not as rock-solid and simple as that Bitcoin safe. CKB’s whole idea is both. Keep the unbreakable safe as the foundation, and build a clever brain alongside it. That’s why they call it the Contract Kernel of Bitcoin. The brains bolted onto Bitcoin’s muscle. It’s not built on top of Bitcoin. It’s not a copy either. It’s its own chain, own miners, own network. Same Proof of Work. More like a cousin. And because it’s so Bitcoin-like, it can connect Bitcoin in directly, without a risky bridge. The base is deliberately simple and a bit slow, so anyone can run it on a normal computer. That’s what keeps it decentralised. The fast stuff happens on Fiber, like Lightning sitting on Bitcoin. Extensions on a house. Foundations untouched. Cells are little Lego bricks that hold what’s true right now. Money, data, rules. Spend some, old Cell gets used up, a fresh one is created. Owning one $CKB is owning a little plot of land on the chain. Want to hold a token, run an app, store data? You need that space. Digital real estate. Lock spare CKB in the Nervos DAO and earn a return. That’s CKB. The safe and the brain, working together.

Can Bitcoin run smart contracts? RGB++ is a non-EVM Bitcoin layer that combines Bitcoin’s UTXO model with the RGB protocol and the Nervos blockchain to create native Bitcoin smart contracts. Our research team wrote a beginner’s guide to how it works. Check it out below: info.arkm.com/research/rgb-p…

Post-quantum security may be early, but preparing before it becomes urgent matters. CKB is one ecosystem worth watching closely as blockchain infrastructure evolves. $CKB @NervosNetwork @ckba_build

🚴 Fiber Dev Log 36 🚴 Moving past the v0.9.0 release, this cycle covers release maintenance, creating better docs for builders, and laying the groundwork for the next batch of features. This cycle brings: - fiber-js default config for faster onboarding & fiber-pay v0.3.2 - Expanded docs w/ interactive tutorials for devs - Ongoing designs for multi-tenant hosted LSP and liquidity management - Listening on multi-address & QUIC support under review Full dev log: github.com/nervosnetwork/fib…

Vitalik's bigger point here isn't just that SNARKs could become dramatically cheaper. Across several posts this week, he's describing a future where signatures, ZK proofs and other expensive checks can increasingly be compressed into proofs, and where "cryptographizing" computation eventually becomes as routine as using HTTPS. If that happens, it changes what we should want from a blockchain VM. If more of the base layer's job becomes verifying proofs of computation happening elsewhere, its cryptographic capabilities shouldn't be frozen around the primitives that happened to matter when the chain launched. Interestingly, that was one of CKB's earliest architectural bets. CKB is designed as a universal verification layer. CKB-VM runs RISC-V and hardcodes no cryptographic precompiles, so new signature schemes, SNARK/STARK verifiers and other cryptographic constructions can be implemented as software at the smart contract or script layer rather than added one by one to the base protocol. We've already seen this flexibility in practice. Groth16 and other ZK proof verifiers have been implemented directly on CKB-VM without modifying the underlying chain, and NIST-standardized SPHINCS+ is already live on mainnet as an opt-in Lock Script. The point is, nobody knows which cryptographic primitives will dominate ten years from now. So if Vitalik is right that cryptography is about to evolve much faster than most expect, the advantage isn't predicting the winners today. It's crypto agility: being able to adopt whatever wins tomorrow.

@apltang just wrapped a four-part series on CKB and the quantum threat, and the conclusion contains the most interesting line: “Nervos solved the hard problem and hasn’t done the easy part.” The hard problem is architectural: can a blockchain adopt new cryptographic schemes as the field evolves, without requiring a network-wide upgrade every time? CKB solved that. New schemes can be deployed through Lock Scripts without changing the base protocol, and SPHINCS+ / SLH-DSA is already live on mainnet. The “easy” part is everything required to turn that architectural capability into ecosystem adoption: tooling, documentation, wallet support, and making the opt-in migration accessible to users. That work is still underway. The full series is well worth reading for one of the clearest public explanations we’ve seen of the distinction between being architecturally quantum-ready and making that readiness usable in practice.

An AI agent rarely knows what a task will cost before it starts. It might call a model ten times or ten thousand times, and a compute job might finish in thirty seconds or run for hours. The service is consumed incrementally, but payment usually is not. Money moves upfront as prepaid credits or afterwards as a bill, and someone carries the gap in between. Streaming payments close that gap by letting money accrue or move in small increments as usage happens. We broke down how AI agents pay as they go 👇 nervos.org/knowledge-base/wh…

CKB is native in BitcoinLight. 🔑 You can send and receive CKB from the same mobile wallet you use for Bitcoin. Same self-custody principle: your keys stay with you. Try it now 👉 bitcoinlight.app/

CKB Off-Chain is coming to Vietnam! 🇻🇳 In collaboration with @bps_club, we will be hosting a builder-focused event involving CKBuilders, local blockchain developers and students for an evening of education, exploration and networking! We will discuss what makes CKB interesting and unique for blockchain developers, ways to get started on CKB, as well as presentations from current CKBuilders about their own experiences. It promises to be an enlightening event!