Every written guide for the Inazuma layer-1 blockchain, in one place.
Start with your role, not with our architecture.
| I am… | Start here | Time |
|---|---|---|
| New to Inazuma | What is Inazuma? | 4 min |
| A user with a wallet | Wallet & first transaction | 10 min |
| A validator running a node | Run a validator | 30 min |
| A developer building an app | Build on Inazuma | 15 min |
| Staking INAZ | Staking, rewards & slashing | 8 min |
| Worried about quantum computers | Quantum resistance | 6 min |
| Confused by a word | Glossary | — |
Basics
- Introduction — what the chain is, what it is not, key numbers
- Glossary — every term in plain English
- FAQ — the questions people actually ask
Using the network
- Wallet — install, back up, send, receive, recover
- Faucet — get test INAZ
- Staking — delegation, rewards, unbonding, slashing risk
Running infrastructure
- Run a validator — hardware, install, keys, systemd, monitoring
- Run an RPC node — replicas, caching, WebSockets, rate tiers
Building
- Build on Inazuma — SDK quick start, reading state, sending transactions
- RPC reference — every method, parameters, subscriptions, limits
- Smart contracts — the WASM VM and how to deploy
- State proofs — trustless reads and light clients
Internals
- Architecture — blocks, consensus, state, networking
- Security model — threat model, slashing, key hygiene
- Quantum resistance — the ML-DSA-65 layer, what is live and what is staged
| Chain | Inazuma, a sovereign layer-1 (nothing settles to another chain) |
| Coin | INAZ, 9 decimals, smallest unit rai |
| Block time | 400 ms |
| Minimum fee | 1,000 rai (0.000001 INAZ) |
| Accounts | Ed25519 keys, base58 addresses, ML-DSA-65 quantum co-signatures |
| Consensus | stake-weighted leader election with precommit finality |
| Contracts | WASM |
| Public RPC | https://rpc.inazuma.network · WS wss://rpc.inazuma.network/ws |
| Repo | Purpose |
|---|---|
| inazuma-core | The Rust L1 node: consensus, state, P2P, RPC |
| inazuma-sdk | TypeScript SDK for apps |
| inazuma-wallet | Wallet extension + injected provider |
| inazuma-docs | These docs |
| inazuma-faucet | Test-INAZ faucet service |
| inazuma-contracts | WASM contract examples & tooling |
Docs live as plain Markdown under docs/. Fix anything unclear: open a pull
request, or an issue describing what confused you and where. Rules of the house —
short sentences, no jargon without a definition, every command copy-pasteable,
and every claim true of the current release.
MIT licensed.
Inazuma is a sovereign layer 1 — our own consensus, state machine, networking and VM, not a rollup or a fork. The goal is narrow and deliberate: be the home chain for memes, NFTs, collectibles, games and communities.
That use case is high volume and low value per transaction. A 500-piece mint, a game writing a move a second, a community handing out collectibles — none of them can pay dollars in fees or wait seconds for a confirmation. So the whole design is bent around being fast and near-free:
| Block time | 400 ms, finalised in the same block |
| Transfer fee | ~0.000001 INAZ — fractions of a cent |
| Throughput | ~2,500 tx/s ingest; 20k-36k tx/s execution in bench |
| Tokens & NFTs | first-class chain records — no contract needed to mint |
| Contracts | gas-metered WASM |
| Accounts | Ed25519, base58 addresses, optional ML-DSA-65 co-signature |
| Light clients | sparse Merkle state proofs |
Getting to top-tier means three things, in this order: enough independent validators that nobody can stop the chain, tooling good enough that a first-time builder ships in an afternoon, and fees that stay boring even when a collection goes viral. Every repo below is one part of that.
| Repo | What's in it |
|---|---|
| inazuma-core | The Rust L1: consensus, state, staking, P2P, JSON-RPC, WASM VM |
| inazuma-validator | Node operators: one-command installer, systemd units, health checks, full guide |
| inazuma-sdk | TypeScript client: RPC, keys, signing, sign-in, state proofs |
| inazuma-wallet | Self-custody wallet: browser extension, web and Android |
| inazuma-contracts | WASM contract examples, host ABI and deploy scripts |
| inazuma-faucet | Test-token faucet service |
| inazuma-docs (here) | All written guides, organised by role |
| inazuma-improvement-proposals | INAZIPs — how the chain changes |
| I want to… | Go to |
|---|---|
| Use a wallet and send INAZ | inazuma-wallet |
| Get test INAZ | inazuma-faucet |
| Build an app | inazuma-sdk · inazuma-contracts |
| Run a node or stake | inazuma-validator |
| Understand the internals | inazuma-core |
| Propose a protocol change | INAZIPs |