Nervos en español

Blockchain PoW-UTXO-RISC-V Impulsada por la comunidad
*ninguna de las publicaciones en esta página es recomendación o consejo financiero*

[Common Knowledge Base Association (CKBA) @ckba_build]

CKB Has No Plan — But We Do.

Our previous posts about roadmaps generated some controversy.

We’re grateful to have your attention.

Because this distinction matters.

CKB doesn’t have a roadmap because it is public infrastructure, not a product operated by a company.

The goal of any serious blockchain is not endless reinvention. It is to become a stable, secure, and predictable infrastructure that others can build on for decades.

That said, CKBA absolutely has plans.

CKBA exists to coordinate stakeholders and grow the CKB ecosystem across the areas that matter most.

That means organized work to attract builders, identify use cases, improve developer onboarding, fund ecosystem initiatives, pursue partnerships, clearly communicate CKB’s value, and actively engage the teams, companies, and communities that can drive real usage on the network.

Having reorganized and unified several teams under a single structure puts us in a stronger position than ever to execute on these goals.

A ton of work is already underway, especially on the Fiber front: improving the stack and documentation, advancing Lightning interoperability and liquidity management, and identifying and removing blockers for adoption.

Work is also ongoing on the design and implementation of the DAO's on-chain treasury and voting mechanisms.

And while there are many other initiatives in the pipeline that we’ll share when the time is right, there’s one that demands immediate attention 👇

Three months ago, Google Quantum AI published a bombshell paper showing that quantum attacks against secp256k1—the elliptic curve behind the signatures used by most blockchains—may require far fewer resources than previously estimated.

In simple terms, the paper made the quantum threat to cryptocurrencies harder to ignore.

The industry conversation that followed was, as expected, hard to miss — and yet it missed CKB.

No mention in the paper, no mention in the con im versations on X and various forums, no mention anywhere.

To put it bluntly, this is a huge communication failure on our part.

CKB is the only cryptographically agile blockchain in existence, and therefore one of the few that’s already quantum ready.

It’s the only chain where devs can bring new post-quantum signature schemes permissionlessly.

No need for soft or hard forks. No need to pick a single PQ scheme and bake it in as a precompile.

CKB is the only chain that can switch between different crypto primitives without disrupting operations or requiring significant infrastructure redesign.

It’s the true embodiment of crypto-agility — yet barely anyone was aware of it.

So, our first course of action on the communication front is to remedy that.

We’ll run a comprehensive marketing campaign that’ll put CKB at the forefront of the Quantum x Blockchain discussion and position it as one of the few projects with a future-proof solution.

And we want all of you involved.

If you care about CKB and want to help push this forward, reach out.

If you’re a developer, researcher, writer, designer, translator, community organizer, content creator, or just someone willing to help amplify the message, we want to hear from you.

This campaign should not be about what CKBA has to say.

It should be about making CKB impossible to ignore.

We’ll be opening channels for community participation soon. In the meantime, reply here, DM us, or join the discussion on Nervos Talk.

[Common Knowledge Base Association (CKBA) @ckba_build]

Membership isn't the only way to participate in CKB. https://t.co/U1TpYees17 now has a general enquiry form. Questions about CKB, General Member interest, or anything else for the team to know.

We read every one 👉 https://t.co/xNZE7ZG4Va

[Common Knowledge Base Association (CKBA) @ckba_build]

In our last post, we covered the idea of a roadmap for CKB, and made clear that in many ways, the idea of a roadmap is antithetical to blockchains.

Blockchains, if designed correctly, strive toward the opposite: ossification.

For the uninitiated, ossification, in the blockchain context, refers to the process by which a protocol’s foundational rules become exceptionally resistant to change, ensuring ultimate stability, security, and predictability.

It represents the maturation of a decentralized network from experimental technology to a rigid digital institution.

A classic example of this from outside our industry would be the TCP/IP protocols that govern the internet.

They have remained fundamentally unchanged for over 40 years.

And that stability is precisely why the internet became what it is today. Because TCP/IP remained boring, predictable, and stable, billions of devices, applications, companies, and networks could coordinate around the same basic assumptions without asking anyone for permission.

Email, streaming, messaging, cloud computing, social networks, and everything else evolved above the protocol—not because the base layer kept reinventing itself, but because it stopped changing enough for the world to build on top of it.

That is the goal of public infrastructure: to remain simple, stable, predictable, and open and accessible.

CKB is designed with this insight in mind: it remains conservative at the protocol layer, and optimizes for flexibility at the application layer.

[Common Knowledge Base Association (CKBA) @ckba_build]

Okay, let’s talk about roadmaps.

It’s a question we’ve had to deal with for years now.

“What is CKB’s future plan? Is there a clear roadmap? What’s on the roadmap?”

CKB is not a product operated by a company. It’s public infrastructure.

And the fact that people think about blockchains in ‘roadmap’ terms is worrying.

Years of high-time-preference teams shilling centralized products as “decentralized” have conditioned the industry to think about blockchains in corporate terms: Who’s the CEO? Who’s on the cap table? What’s the roadmap?

These teams use “the roadmap” as an upselling technique—a product in itself, used to capture attention, manufacture hope, and ultimately distract from the task of improving the safety, user-friendliness and utility of these systems.

What’s worse, it worked. They brainwashed much of the industry to see blockchains as products in need of constant iteration, when precisely the opposite is the goal.

But getting that point across has now become almost impossible.

CKB was designed from the start to evolve without hard forks, to accommodate changing requirements without intervention from a specialized group of developers.

We can all realize the potential of CKB today, and it’s important to start thinking in these terms.

[Common Knowledge Base Association (CKBA) @ckba_build]

Neuron is now maintained and supported by CKBA. Part of that responsibility is keeping you safe, so here's an important heads up.

⚠️ A fake site, neuron-wallet[.]com, is impersonating Neuron and ranking near the top of search results right now. ���️
This is a phishing scam. Don't download anything from it, and never enter your seed phrase into any website.

Neuron only ever comes from one place, the official GitHub.

If you need help, contact the team in the #support channel on the Nervos Network Discord.

https://t.co/QnJAJFmYBq

[FiberDevs @FiberDevs]

Our UX designer Yuqi just published another interactive walkthrough. Follow Pico the duck through an airport and you'll see two of the things payment channels are actually good at:

1. Pay-by-the-minute via off-chain channels.
Pico naps for 20 minutes and pays for 20 minutes. The payment updates off-chain while he's napping and settles when he wakes; no fixed packages and no minimum charges.

2. Asset-agnostic routing through a single payment hub.
Pico's luggage storage accepts CKB; the massage chair accepts sats. He pays once and Fiber handles the liquidity routing and asset swaps in the background.

[FiberDevs @FiberDevs]

🚴Fiber Dev Log 29🚴

We're moving through the v0.9.0 release cycle, with Fiber v0.9.0-rc1 out. This brings together updates across routing, funding, transport, and overall stability.
This release candidate also introduced a unified migration system, laying a clearer framework for future database and protocol upgrades.

We also improved the Network Actor stability, with updates to keep channel actors alive across peer disconnects.
Better observability is also now in place with the addition of debug and trace logs throughout the channel funding flow.
Community feedback continues to be a big help! Input from the WASM testnet recently helped us catch and fix an invoice payment rejection case involving zero-balance channels. Thanks to the community member who reported it.

Moving forward, our focus shifts more on security hardening and finalizing the x402 end-to-end flow.

Full log: https://t.co/Pjwoa7FPBg

[Common Knowledge Base Association (CKBA) @ckba_build]

1/

Same Foundations. New Association.

Today, we’re announcing the establishment of the Common Knowledge Base Association (CKBA): a Swiss Verein created to serve as the new coordination layer for the CKB ecosystem.

It’s an open, membership-based, contributor-driven structure built to outlast any one team.

Full announcement 👉 https://t.co/K6IUQvcP58

[FiberDevs @FiberDevs]

Happy to see Fiber Link move from engineering prototype to product-ready!
It's now a fully deployable community tipping layer over CKB, allowing members to support each other without running their own nodes.
Product overview: https://t.co/RqQp80QUGJ

Fiber-Pay v0.2.5 also keeps evolving—simpler connect flows, passkey support, new demos, and AI agent use cases.

🏗️ More community-led experiments on Fiber here in Pulse 05: https://t.co/g0HHi35ROR

[Common Knowledge Base Association (CKBA) @ckba_build]

Censorship-resistance & decentralization are often discussed, but longevity may be the most important quality of a blockchain.

Work is underway on the protocol treasury of Nervos CKB described in the positioning paper, follow progress on Nervos Talk!👇

https://t.co/2mYdXpu48d

[Common Knowledge Base Association (CKBA) @ckba_build]

Are you tired of endless upgrade discussions about hard forks?

Are you interested in playing with the latest advances in post-quantum cryptography or zk proofs?

Check this out to learn more about CKB & unleashing maximum flexibility with RISC-V👇

https://t.co/Jt8W4Da0HX

[Common Knowledge Base Association (CKBA) @ckba_build]

CKB is already prepared for a future that necessitates post-quantum cryptographic methods.

No hard forks are needed, no governance debates.

If you're concerned about the impact of quantum computing, you should learn about CKB.

https://t.co/R7RJsCRFH1

[Common Knowledge Base Association (CKBA) @ckba_build]

With Bitcoin and Quantum Computing trending, check out "How Bitcoin's Path to Quantum-Resistance Could Look" on the Nervos Knowledge Base🧠

https://t.co/x2Rv7WeImE

[Pocket Node @PocketNodeCKB]

Pocket Node v1.5.0 is live.

Milestone 3 complete: multi-wallet, key storage redesign, and per-wallet sync.

Here's what shipped 👇

[CKB Dev↾⇃ @CKBdev]

👷 Latest updates of CKB from the engineering side:
Another month of refining the core and pushing optimizations, including improved CKB-VM ARM64 performance and ML-DSA work to help prepare for post-quantum standards.
Also strengthening CKB-VM with a new differential testing framework to validate future optimizations.

Other updates:
- AI Tooling: Added SKILL.md for AI agents in ckb-debugger to streamline script debugging
- Connectivity: Continued QUIC support for Tentacle to provides faster handshakes and better resilience against connection migration
- Governance: Multiple DAO Treasury designs & voting directions under discussion
- Maintenance: Upgraded toolchain to 1.95.0 and synced ckb-musl with upstream

Full log: https://t.co/eRRFTTeyzp

@NervosNetwork @CKBDevrel

[CKB Dev↾⇃ @CKBdev]

CKB is entering a mature phase. Our work is shifting toward deeper optimization, faster verification, and reproducible infrastructure.
Recent highlights:
- Optimized SP1 verification: Reduced cycles from ~6000M to ~63M (~100x improvement)
- SMT verification performance reached a production-viable level
- ARM64 optimizations: streamlined Zba instruction handling by removing redundant ops

Meanwhile, a new discussion is underway: Activating the Nervos DAO Treasury, exploring a shift to an on-chain, governance-controlled model

Dev Logs will now move to a monthly cadence, reflecting a more focused, incremental development cycle.

More in the full update ↓
https://t.co/K7f7sbeggT

@NervosNetwork @CKBDevrel

[FiberDevs @FiberDevs]

We've been working to lower the entry barrier for Fiber even further.
Introducing Fiber Demo Startup — a complete local dev environment for the Fiber Network. One-click start. Hours of setup saved.
Everything runs out of the box with Docker:
- CKB Dev Chain
- Bootnode
- 3 Fiber nodes
- Fund distribution tool

Plus a built-in interactive demo app.
Two modes included:
- Quick Start (beginners): from P2P connection to your first payment in 3 steps
- Control Panel (advanced): a sandbox to experiment and see how Fiber works under the hood

Who it's for:
- Learning Fiber
- Building Fiber apps
- Demoing Fiber features
- Exploring CKB payment channels hands-on

GitHub: https://t.co/oqFspkv8pE
Dev notes: https://t.co/7qafBtt5rw

[Common Knowledge Base Association (CKBA) @ckba_build]

🤖Agentic payments are trending following @tempo's release of the MPP standard, which uses "payment channels" instead of on-chain transactions

Get your questions in for the @PolyCrypt_ team, who has been extending their Perun channel framework to CKB!👇

https://t.co/3saV4jVrWZ

[Common Knowledge Base Association (CKBA) @ckba_build]

🌊Sonami AMA is starting on Reddit, get in your last minute questions!

🔗https://t.co/SUjsiFAV2k

Sōnami is actively developing several projects in the Nervos ecosystem:

🌉Rosen Bridge, originally introduced through the @UtxoAlliance, is cross-chain infrastructure connecting Nervos CKB to Cardano, Ergo, Ethereum, and other networks.

🫂Community Fund DAO v2.0 reimagines decentralized governance on CKB by introducing a delegated representative model designed to address shortcomings observed in existing approaches.

🤖CKB AI provides AI-powered developer tooling for Nervos with the goal of accelerating the speed of development on the network. The team has also begun early efforts on AI agent infrastructure and applications.

[Common Knowledge Base Association (CKBA) @ckba_build]

🧙‍♂️As many of you know, RISC-V zkVM's continue to grow in prominence every day.

It has been a pleasure over the last few months to work with the @LimeChainHQ team to approach this question:

"Can we build a zkVM to verify blocks on CKB?"

Check out this article to learn more about the project. Still much work remains, but preliminary benchmarks will be published soon!