The reference Kanon network runs on Besu.
A permissioned Ethereum L1, purpose-built for industry-sector and regional deployments. The kanonv2 contracts also run on any public EVM — this is the one we ship as the reference.
Private Ethereum, Hyperledger Besu nodes.
A permissioned Ethereum L1 running Hyperledger Besu 26.5 with the Cancun fork. Standard EVM, standard JSON-RPC — the tools you already use just work.
Proof of Authority via QBFT.
A named validator set produces blocks with deterministic finality. No probabilistic reorganizations and no fee-driven ordering — the chain settles in one block.
Permissioned contract deployment.
Only allowlisted accounts can deploy bytecode. New contracts go through the same governance pipeline as protocol upgrades — proposed, timelocked, executed.
Anyone can run an RPC node.
Validators are permissioned; observers are not. Run a read-only or archive node from anywhere, sync the chain, serve your own apps. No allowlist needed.
Built for regional and sector deployments.
A bank consortium, a national health ministry, a logistics network — each can stand up its own Kanon VDR with its own validator set, its own governance, its own approved issuers.
Native support for did:kanon.
Each network exposes the did:kanon method through DIDRegistry. Format: did:kanon:{networkId}:{id}. Resolvable from any Aries-compatible wallet and the Credo plugin.
No gas fees.
Permissioned validators and approved-issuer access control replace fees for spam protection. Issuance, revocation, and verification are free at the protocol level — issuers don't budget for transaction costs.
BlockScout block explorer.
Full open exploration of blocks, transactions, contract calls, and decoded events. Every issuance, revocation, and governance action is publicly auditable in real time.
Reference network specs.
Stand up your own network.
The same kanonv2 contracts, the same Credo plugin, your own validator set and governance. Sector-scoped or region-scoped.