- Tweets 1,141
- Following 428
- Followers 146
- Likes 8,645
tea retweeted
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!
4
28
109
3,475
tea retweeted
A forgotten HTTP status code from the 1990s is becoming a checkout layer for machines.
402 Payment Required was reserved for digital payments long before the web had money software could actually use.
Now it does.
x402 turns a 402 response into something an AI agent can understand: here’s the price, here’s how to pay, send proof and get the resource.
L402 applies the same basic idea to Lightning: pay the invoice, prove payment, access the service.
Different protocols, same shift.
Instead of sending software to a checkout page, the web itself can tell it what something costs and how to pay for it.
That makes payment part of the HTTP request, not a separate workflow that necessitates a human in the loop.
What still matters underneath is the rail that actually moves the money.
That’s where Fiber comes in: settling the tiny, frequent payments these protocols are designed to create 👉fiber.world/showcase
3
15
61
1,461
tea retweeted
One of the more encouraging things this year is that CKB’s builder ecosystem kept expanding while much of the industry was doing the opposite.
Teams were shrinking, budgets were being cut, and a lot of speculative activity disappeared.
Meanwhile, more developers kept showing up to experiment on CKB.
Today, over 100 are working on or exploring the network:
- 70 formal CKBuilders working through a structured program
- ~40 more coming in through Build on CKB, an open group for developers curious about the chain
- 45 projects now listed on the CKBuilder tracker, with 23 added in a single quarter and 15 submitted for technical review by core CKB developers
Claw & Order, a two-week AI Agent hackathon, closed with 22 open-source submissions; 16 came from CKBuilders, including the top two prize winners
- The work spans a surprisingly wide range: ZK key recovery for AI agents, a Groth16 zkSNARK verifier, a Fiber desktop client, an ML-DSA post-quantum implementation, a DID reference dashboard, lending primitives, prediction pools, and more
Some of these builders are now graduating from experimentation into independent projects.
But the more important signal is that all of this happened during one of the bleakest periods for the industry.
If this is what the builder pipeline looks like when capital and attention are scarce…what happens when they aren’t? 👀
2
30
88
3,547
tea retweeted
Quantum computing stopped being a science project somewhere along the way, and announcements like this are how you can tell.
Helios is being deployed through Oracle Cloud Infrastructure. Quantinuum has signed a manufacturing partnership to help build future systems at scale. Revenue grew 279% year-over-year. Sol is on the roadmap for 2027, Apollo for 2029.
For years, the skeptical case was that quantum computing might never escape the research phase; that the papers, prototypes, and laboratory demonstrations would never become machines that can be error-corrected, manufactured at scale, deployed reliably, and improved generation after generation.
Announcements like this chip away at that argument.
Quantinuum has not built a cryptographically relevant quantum computer. But more of the obstacles between today’s machines and a CRQC are becoming engineering problems: fault tolerance, manufacturing, systems integration, cloud deployment, and successive hardware generations with explicit roadmaps.
Enormous hurdles remain, but betting the security of long-lived cryptographic systems on those hurdles never being cleared is becoming harder to defend.
For blockchains, the relevant timeline is not the date a quantum computer can break secp256k1.
It is that date minus the time required to replace secp256k1 across a live network.
Replacement cryptography has to be selected, implemented, audited, integrated into wallets and infrastructure, and adopted by users whose assets remain protected by vulnerable keys. None of that happens instantly.
There is another problem too: we do not yet know which post-quantum schemes will prove durable enough to rely on for decades.
That is exactly what makes CKB different.
CKB does not need to wait for the industry to settle on a single post-quantum winner. Cryptographic verification lives in programmable Lock Scripts running on CKB-VM, so new schemes can be introduced without changing CKB’s consensus rules.
SPHINCS+ is already live on mainnet.
If a better scheme emerges, it can be added alongside it. If cryptanalysis weakens one, users can migrate again without redesigning the protocol underneath them.
For CKB, the post-quantum migration does not start when Q-Day gets close.
It has already started, and if circumstances change, we can change direction on the go instead of starting over.
We believe the future of enterprise computing will bring AI, HPC, and quantum together.
That’s why, today, Quantinuum and @Oracle have announced a multi-year strategic partnership to bring quantum computing to Oracle Cloud Infrastructure customers and accelerate the commercial adoption of hybrid quantum-AI computing.
As part of the collaboration, our Helios quantum computer will be deployed in a U.S.-based Oracle AI data center, alongside OCI’s HPC and GPU infrastructure, and made available through OCI’s quantum service to give OCI customers a practical and secure way to explore how high-fidelity quantum computing can complement existing AI and HPC workloads—using the governance and access controls they already rely on.
Read the joint announcement: quantinuum.com/press-release…
2
23
72
3,190
tea retweeted
There’s an interesting connection between two of the biggest changes in Vitalik’s updated Ethereum roadmap.
The first is that quantum safety has clearly moved up the priority list.
The work being discussed is substantial: leanSPHINCS, signature aggregation, zkzk frames to make post-quantum signatures economical, and formal verification as part of the path toward getting there.
The second is architectural.
Vitalik suggests that those zkzk frames could eventually expose a simpler ISA such as leanISA or RISC-V, with the EVM becoming an IR on top rather than something permanently enshrined in the base protocol.
These may look like separate roadmap items, but they point toward the same underlying lesson: the less you permanently bake into the base protocol, the easier it is to change the things above it.
That is especially relevant now that quantum safety is becoming a concrete engineering priority rather than a abstract concern.
CKB was designed around this idea from the beginning.
CKB-VM has used RISC-V since mainnet launch, but RISC-V itself is only part of the story. The VM is deliberately crypto-agnostic, so cryptographic verification can be implemented as ordinary executable code in Scripts rather than hard-coded into the protocol.
That’s what gives CKB crypto agility. A new signature scheme such as SPHINCS+ can be deployed as a Lock Script without changing CKB’s consensus rules, and users can migrate when they need to.
Interestingly, when Vitalik first proposed replacing the EVM with RISC-V in 2025, he pointed to CKB-VM as one of the precedents.
Ethereum is now treating quantum safety as a major protocol priority.
Different architectures and different paths, but the direction is familiar:
Keep the base protocol simple, general and stable.
Make everything that may need to evolve programmable.
I updated my 2023 roadmap diagram to overlay where the items that were there sit in the current Strawmap ( strawmap.org/ ).
In general, a lot of overlap, but:
* Some things got reshuffled in order (eg. quantum safety up-prioritized)
* Some things deprioritized (eg. VDFs; many EVM improvements)
* Some things replaced with superior constructions (eg. Verkle -> unified BT -> PBT; state expiry -> new state types)
What's most striking, however, is that some completely new things are in the strawmap that are NOT in this diagram, because they were not in the 2023 roadmap at all. These reflect changing priorities.
Notably:
* First-class attention to strong privacy. This covers: keyed nonces and recent roots, aspects of FOCIL, lean privacy pool & wormholes
* Aggressive scaling in the context of post-quantum. This covers: leanSPHINCS signatures and aggregation, zkzk frames (see ethereum-magicians.org/t/eip… )
* Lean-ification of the spec, to assist in formal verification (full FV of everything is only possible because of modern AI)
* Blob and gas futures (this idea just didn't exist back in 2023)
* Native rollups (SNARKs were nowhere near mature enough to even consider this back in 2023)
* A more open design space for the "future of the EVM". zkzk frames already implies that the protocol will expose to users some ISA that's not the EVM - current leading candidates are leanISA and RISC-V. These ISAs are more simple, modern and efficient than the EVM. Once they're there, why not expose them to developers everywhere? (And then, why not turn the EVM into being an IR on top of that ISA, instead of an enshrined feature massively complicating the base protocol?) Though much of the deeper exploration here is too early even for the strawmap.
* New state types are not just a replacement for expiry, they're a fundamentally different paradigm to how Ethereum does scaling
A common theme in scaling, found in both state types and zkzk frames (both new ideas), is that instead of trying to maximally scale ALL ethereum activity, we try to create specialized mechanisms that have more restrictive properties that make them more scaling-friendly, while supporting the heaviest loads incurred by users and applications today (eg. token transfers, swaps) and tomorrow (eg. privacy protocols).
The other common theme is treating STARKs and AI-accelerated FV as first-class objects, that we are okay betting the technical future of Ethereum on. There are recursive STARKs in many layers of the protocol, one particular primitive (the "aggregate to union verified dependencies" primitive) is expected to be used in *three* places in the protocol: EL, CL and DL. This can only be safe with formal verification, which is itself only feasible with modern AI tools.
In general, many steps forward in maturity. And a huge amount of hard work by many dozens of Ethereum researchers and developers on all of these features.
Ethereum will be quantum-safe. Ethereum will put users' privacy first. Ethereum will be secure. Ethereum will be censorship-resistant. Ethereum will be highly performant and scalable while satisfying the above. And Ethereum will be Lean.
1
25
63
3,282
tea retweeted
Bitcoiners deserve a lot of credit for pioneering many of these ideas (see Utreexo).
But yes, this is what the current proposed Ethereum scaling strategy looks like in action.
We want Ethereum to have the best of UTXO-style state, dynamic state, and everything in between, allowing the great majority of Ethereum's activity to be hyperscaled without sacrifice to decentralization, ease of node running and censorship resistance.
firefly.social/post/x/208898…
501
354
1,977
408,895
tea retweeted
The easiest payment infrastructure to use is often the infrastructure that puts one company in control.
And, if we’re being honest, the convenience and UX benefits are real. So are the trade-offs.
A managed provider can abstract away liquidity, settlement, compliance, and technical complexity while offering businesses a predictable experience, customer support, and a single accountable counterparty.
For many businesses, that is precisely what makes new payment rails usable in the first place.
But convenience comes with dependency. Businesses rely on the provider to keep supporting the assets, markets, and payment flows they need. If the provider changes its pricing, restricts access, suffers an outage, or discontinues the service, users cannot simply route around it.
Fiber explores a different model.
Fiber is open payment infrastructure that anyone can use, build on, or help operate.
Connect to the network and pay across it. Or strengthen the network by opening channels, providing liquidity, routing payments, running watchtowers, and helping connect Fiber with other payment networks.
There is no single company controlling every payment, route, or service. Fiber grows through the independent participants who use it, operate it, and build businesses on top of it.
It is less like a product owned by one company and more like a living economic network—one that becomes more useful, resilient, and valuable as more people contribute to it.
Try Fiber today 👉 fiber.world/docs/build/inter…
Or, build on it 👉 fiber.world/docs/build/toolc…
1
20
56
1,448
tea retweeted
🚴 Fiber Dev Log 34 🚴
v0.9.0 is live 🟢
After weeks of release hardening, the final milestone cleanup is complete, and Fiber v0.9.0 is released, making nodes more reliable, recoverable, and easier to operate.
Highlights:
- A unified database migration system with backup and restore support
- Stronger payment recovery with Cross-Chain Hub improvements
- More reliable reconnect and channel recovery flows
- Smoother node onboarding with new install and quick-start scripts
Full dev log: github.com/nervosnetwork/fib…
3
13
52
1,004
tea retweeted
The payments industry is arriving at a shared conclusion, and it is worth stating plainly: the digital economy needs faster, smaller, more frequent, and more flexible ways to move value than either legacy rails or individual onchain transactions can provide.
Look at what is being built.
Circle Gateway offers gas-free USDC nanopayments through offchain authorizations and batched settlement.
Stripe and Bridge are building stablecoin infrastructure for payments, payouts, treasury, and global money movement.
Tempo’s MPP Sessions let customers pay continuously through offchain vouchers, while x402 gives applications and agents an open standard for requesting payments over the internet.
Different projects, different approaches, one direction: more value is moving offchain, into smaller and more programmable payment flows.
Fiber belongs to this movement, but tackles a different layer of the problem.
x402 and MPP help software request and authorize payments. Tempo makes repeated payments inside a bilateral service relationship more efficient. Circle and Stripe make stablecoin payments operationally convenient through managed infrastructure.
Fiber is building the open network those payments can travel through.
Rather than requiring a separately funded relationship with every recipient, Fiber routes payments through shared network liquidity. Anyone can connect, run a node, provide liquidity, route payments, or build applications on top—and payers can reach recipients across the network without opening a direct channel with each one.
The simplest way to understand Fiber:
Connect to the network. Pay across it.
Read how Fiber routes value, what open payment infrastructure changes, and what becomes possible when payments become programmable 👇
nervos.org/knowledge-base/fi…
18
60
1,932
tea retweeted
Great ideas are always worth learning from. ⚡️
Inspired by Lightning's WebLN, a new community experiment explores an important question:
When websites can request payments, how to make sure users remain in control?
A web payment interface is never just about making API calls easier. It also about building the right boundaries between websites and users:
→ What should a website be allowed to do?
→ Which actions need user confirmation?
→ How can users stay in control of their payment capabilities?
Fiber WebLN explores a browser-facing interface where websites can request: Fiber actions, while users decide what is allowed.
It creates a trust boundary between the page and the Fiber node: Fiber moves the money. Fiber WebLN governs how the web asks.
It also shows how different Fiber node setups can work through the same interface, so websites don't need to care where the user's node is running.
Try the demo: fiber-webln-docs-mu.vercel.a…
GitHub: github.com/HappySonnyDev/fib…
Dev's thoughts: talk.nervos.org/t/from-webln…
1
18
56
1,364
tea retweeted
Fiber is being built as an open network where people, businesses, applications, and machines can exchange value continuously, without a payment processor sitting at the center of every relationship.
In practice, that means creators can be paid as their work is consumed rather than waiting on monthly platform payouts.
Applications can charge a fraction of a cent per request instead of forcing subscriptions on occasional users. Devices can pay for the exact bandwidth or electricity they use, as they use it.
These are payments that card fees and per transaction settlement rule out today, and they become practical the moment value moves offchain and flows at internet speed.
How the network makes that possible 👇
nervos.org/knowledge-base/wh…
24
62
1,652
tea retweeted
Businesses accepting stablecoin payments from AI agents is the clearest signal yet of where payments are heading: software buying services in real time, in amounts cards were never built for.
The open question is what carries those payments at scale.
One API call or one minute of compute is too small for card fees and too frequent to settle onchain individually.
Payment channels were designed for exactly this: open once, pay continuously offchain, settle when done.
That's the domain Fiber is being built for. An open, peer-to-peer payment network on CKB, built in public, designed to support emerging machine payment standards like x402 and MPP.
The complete guide 👇
nervos.org/knowledge-base/wh…
AI Agents Can Now Pay Businesses Directly Via Coinbase
Coinbase (@coinbase) now lets businesses accept USDC payments from autonomous AI agents through the x402 payment standard.
The rollout expands the exchange’s push into AI powered finance and digital payments.
Coinbase also introduced AI trading tools and a developer kit aimed at building applications for the growing agentic economy.
The company says the products are designed to support an economy where AI agents can transact on behalf of users.
13
47
2,296
tea retweeted
The recent Fiber Network Infrastructure Hackathon yielded an unprecedented level of participation, with around 100 participants and 66 final submissions.
It might be a bear market, but developer activity on CKB and Fiber is surging. Read the full roundup and project summaries on Nervos Talk
talk.nervos.org/t/gone-in-60…
4
38
91
3,721
tea retweeted
Are Bitcoin and Ethereum quantum resistant?
Not today.
Both networks authorize transactions with ECDSA over secp256k1, the signature scheme a sufficiently powerful quantum computer running Shor's algorithm could eventually break.
More than 7 million BTC sit in addresses with public keys already visible onchain.
Ethereum has an even broader exposure because users keep using the same account for years. Once an Ethereum account sends its first transaction, its public key can be recovered from the blockchain permanently.
That means an attacker can harvest those public keys today and simply wait until quantum hardware is powerful enough to derive the corresponding private keys.
Both ecosystems are preparing.
Bitcoin has BIP 360 and BIP 361 on the table, with the replacement algorithm and migration framework still up for debate.
Ethereum has a structured roadmap built around native account abstraction, targeting milestones through 2029.
Under optimistic assumptions, either path takes years to complete.
And that's only the first migration.
Today’s post-quantum algorithms likely won't be the final ones blockchains adopt. As PQ cryptography evolves, blockchains will need to keep evolving with it.
Which raises the deeper question: can a blockchain keep replacing its cryptography as the landscape shifts?
The primitives being standardized now will age like every generation before them, and the systems that endure are the ones able to adapt each time it happens.
That property has a name: crypto agility.
The full breakdown, including where CKB fits, is here: nervos.org/knowledge-base/ar…
1
12
43
958
tea retweeted
The crypto industry has spent the past week telling the press it is preparing its defenses against quantum computing.
The same coverage carries a warning from the same executives: moving early is dangerous, because post quantum cryptography is still evolving; move too late, and it’s game over.
So the industry finds itself stuck between two risks. Wait too long and exposed keys pile up, the attack surface becomes massive, and the pressure to rush a migration at any cost balloons.
Move too soon and you risk welding tomorrow's legacy algorithm into your consensus rules.
That bind exists for one reason: on most blockchains, cryptography is hardcoded at the protocol layer, and changing it means a fork the entire ecosystem has to coordinate around.
CKB was designed without that constraint. Signature verification lives in programmable Lock Scripts, which means anyone can deploy new signature schemes permissionlessly and without waiting for a network-wide consensus.
A SPHINCS+ Lock Script has been live on mainnet since 2025. A self custodial quantum resistant wallet built on it shipped in February.
If the standards ever move past SPHINCS+, a new PQ scheme can be deployed the same way: quickly and without technical or social disruptions.
1
11
33
881
tea retweeted
Quantum risk is not the same for every crypto holder.
The first thing that matters is exposure.
If your public key has never appeared onchain, a future quantum attacker has nothing to work with. But once your public key is revealed, it becomes part of the permanent public record, and a future attacker can copy it today and wait indefinitely for quantum hardware to catch up to attack it.
Therefore, preparing for Q-Day requires some forethought.
You need to think about the level of your exposure and how to migrate your assets to a quantum-safe environment on time.
Read the full article to learn more: nervos.org/knowledge-base/ho…
1
10
37
923
tea retweeted
“Harvest now, decrypt later” is one of the most under-appreciated risks facing crypto today.
The phrase usually describes an attack where an adversary collects protected data now and stores it, waiting for future technology that can break the cryptography protecting it.
In crypto, the problem is simpler, as blockchains make the “harvest” part trivial.
The data is already permanent, publicly visible, and therefore easy to archive.
1
8
31
1,672
tea retweeted
Here's a fun little exercise for crypto bros:
Open the quantumtracker.org/ website by the legends @tectonicxyz
Select "Blockchains" in the sidebar.
Sort by "Tier."
Notice who sits at the top with the most green check marks :)
Cheers 🍻
6
30
71
4,956
tea retweeted
While the Fiber Dashboard shows you that Fiber is alive, Echo gives that quietness a pulse—letting you experience the network through motion, rhythm, and sound. 🎶😌
Vibe-coded by our UI designer (who also designed the Fiber Dashboard—and sings great karaoke😍), Echo is a visual and sonic take on network liveness.
As for the name, an echo only exists when there's connection, response, something beyond yourself.
That felt right for Fiber. A network only becomes alive when people join, connect, and interact.
Sense Fiber's pulse: echo-web-eight-alpha.vercel.…
Designer's note: talk.nervos.org/t/echo-a-son…
GitHub repo: github.com/yfeng2824/echo
4
16
70
2,864