Nervos Network Guide: Building Layered Solutions for Web3

Web3 is moving toward modular, layered architectures where security, execution, and data availability can be combined flexibly. Nervos Network was early to this design with a layered stack that separates a secure, flexible Layer 1 from scalable Layer 2 environments. This guide explains how Nervos works, why its model matters for developers and users in 2025, and how to build and secure assets across its ecosystem.

What is Nervos Network?

Nervos is a public blockchain ecosystem built around a general‑purpose Layer 1 called CKB (Common Knowledge Base). CKB is designed to store and verify the most important on-chain facts, while Layer 2 solutions handle high‑throughput execution. This mirrors the broader industry trend toward modular blockchain design, where Ethereum rollups and Bitcoin extensions concentrate execution while anchoring into a secure base layer. For context on the rollup-centric roadmap and recent upgrades like Dencun that improve rollup data availability, see the overview from Ethereum.org on the Dencun upgrade.

• Overview of Nervos Network and CKB on Wikipedia provides a high‑level introduction to the project and its goals.
• Nervos homepage includes links to the latest ecosystem updates.

Authoritative references:

• Nervos Network overview: Nervos Network (Wikipedia)
• Project site: Nervos.org
• Ethereum modular roadmap context: Ethereum Dencun upgrade

Layer 1: CKB as a secure, flexible base layer

CKB is a Proof‑of‑Work Layer 1 with a unique Cell model, a generalized version of UTXO. Every unit of state is a “cell” that stores data, controlled by scripts. Cells can hold native capacity, assets, or application state. This design cleanly separates verification from computation: any logic that can be validated deterministically can be written as a script, while heavy computation can be performed off‑chain and then verified on‑chain.

Key properties:

• Cell model and programmability: Capabilities are defined in the Cell model RFC.
• VM and language flexibility: CKB uses a RISC‑V virtual machine; see the CKB‑VM specification.
• Native token model and long‑term storage: CKB capacity functions like state rent; you occupy on‑chain space by holding CKBytes.
• On‑chain token standard: The Simple UDT (sUDT) RFC defines a minimal, flexible token format.
• Economic alignment: Long‑term holders can participate in the CKB DAO mechanism.

Because CKB retains a UTXO‑like structure with programmable verification, it is well suited to verifiable bridges, token standards, and cross‑chain protocols. Developers can build custom logic directly in scripts, avoiding heavy reliance on complex virtual machines.

Further reading:

• Cell model RFC
• CKB‑VM spec
• Simple UDT RFC
• CKB DAO RFC

Layer 2: Scaling with Godwoken and sidechains

Nervos encourages execution to move to Layer 2 while anchoring security and settlement to CKB. The ecosystem includes:

• Godwoken: An EVM‑compatible rollup that lets Solidity developers deploy contracts with familiar tooling. See the official Godwoken documentation.
• Axon: A high‑performance sidechain framework designed for application‑specific chains that can settle to CKB. Explore the codebase on Axon’s GitHub repository.

This layered approach fits a post‑Dencun Ethereum world where rollups are the default scaling path, and developers want to reuse EVM tooling while tapping into different security bases. With Godwoken, teams can ship dapps quickly and later choose settlement strategies that match their trust assumptions.

References:

• Godwoken docs
• Axon on GitHub
• Rollup context: ZK rollups explained (Ethereum.org)

Interoperability: Bridges and cross‑chain flows

Nervos has focused on interoperability since the early days:

• Force Bridge: A cross‑chain bridge framework that connects CKB to external networks such as Ethereum. Review the architecture and security model in the Force Bridge repository.

As the 2024–2025 cycle brings renewed attention to Bitcoin‑native assets and Ethereum L2s, projects are converging on safer bridging patterns: lightweight proofs, minimize trusted components, and simple escape hatches. Nervos’s Cell model is a good fit for verifiable bridge logic, where on‑chain scripts validate succinct proofs of off‑chain events.

Bridge operations always carry risk. Developers should follow security checklists, limit trust in multisigs, and prefer designs with on‑chain verifiability when possible.

Reference:

• Force Bridge on GitHub

UX and identity: Passkeys and account abstraction

Wallet UX is improving across chains, with passkeys and account abstraction reducing friction. In the Nervos ecosystem:

• JoyID enables WebAuthn-based, seedless wallet experiences for dapps and users who prefer passkeys over seed phrases. Learn more at JoyID.

For developers, combining passkey login with CKB scripts or EVM contracts on Godwoken can deliver near‑Web2 onboarding without compromising non‑custodial control.

Reference:

• JoyID

Developer workflow: From idea to mainnet

If you are evaluating Nervos for a new dapp or protocol, here is a pragmatic path:

1. Choose your execution environment

   • EVM‑compatible: Deploy to Godwoken using Solidity and existing tooling. Start with the Godwoken docs.
   • Native CKB pipeline: Implement application logic as verification scripts and build user flows around the Cell model.

2. Scaffold your stack

   • JavaScript/TypeScript SDKs and utilities: Lumos helps you construct transactions and work with CKB’s Cell model.
   • Command line: ckb-cli supports local dev cycles and interaction with nodes.
   • Sidechains: For high‑throughput or app‑specific needs, explore Axon.

3. Asset strategies

   • Mint sUDT on CKB using the sUDT standard.
   • Bridge to and from Ethereum via Force Bridge if you need liquidity or composability with EVM ecosystems.
   • Consider settlement flows: finalize on CKB for verifiable state, while running high‑frequency activity on a rollup or sidechain.

4. Security and audits

   • Prefer minimal, well‑audited scripts or contracts.
   • Use on‑chain verification for critical invariants.
   • Treat bridges and cross‑chain messages as adversarial environments.

5. Wallet integration

   • Support both the UTXO‑style Cell model and EVM accounts where appropriate. For a refresher on these models, see a primer on UTXO vs account-based models.

Why Nervos’s layered model matters in 2025

• Modularity is winning: Ethereum’s rollup‑centric architecture and upgrades like Dencun have validated a layered model where base layers secure data and proofs, while execution scales off‑chain. Nervos anticipated this split, giving developers flexibility to choose execution and settlement layers without sacrificing security guarantees. See the Dencun overview for broader context.

• Multi‑ecosystem interoperability: As Bitcoin‑native standards, Ethereum L2s, and app‑specific chains evolve, teams need a base layer where verifiable logic can anchor cross‑chain state. CKB’s Cell model is expressive enough to validate proofs across systems.

• Developer choice and longevity: CKB scripts can be lean and audit‑friendly; Godwoken offers instant EVM familiarity; Axon supports specialized performance needs. This optionality is useful when protocols must evolve without forcing users to migrate chains or change trust assumptions.

Risk management: What to watch

• Bridge complexity: Favor designs with on‑chain verification and limit reliance on guardians or multisigs. Study the architecture of Force Bridge and similar systems before moving large value.

• Finality and UX: Different layers have different confirmation times and failure modes. Communicate these clearly to users, especially for cross‑chain operations.

• Smart contract and script audits: Whether you deploy to Godwoken or write CKB scripts, keep the attack surface small and plan for upgradability with explicit governance.

Quick start checklist

• Read the high‑level history and purpose: Nervos Network (Wikipedia)
• Decide execution environment: Godwoken docs or native CKB scripts
• Understand the data model: Cell model RFC
• Tokenize assets: sUDT standard
• Tooling: Lumos SDK, ckb-cli
• UX upgrade: JoyID passkey wallet
• Bridge plan: Force Bridge

Securing keys across layers

Whether you operate on CKB, Godwoken, or across Ethereum L2s, private key hygiene is non‑negotiable. A hardware wallet helps isolate keys from web threats while supporting multi‑chain flows. If you need a device that is open‑source, integrates with popular wallets and dapps, and is designed for both UTXO and account‑based networks, OneKey is a practical choice for builders and power users alike. It aligns well with Nervos’s layered approach: you can sign transactions on CKB, interact with EVM dapps on Godwoken, and manage assets across multiple chains without changing your security model.

Explore Nervos, pick the right layers for your use case, and pair them with a secure key management setup to ship resilient, user‑friendly Web3 products.