KANARIdocs
Network
Documentation
Kanari DocsDeveloper documentation
Kanari DocsDeveloper documentationKanari Docs InstallationSet up a content-driven documentation site with Kanari Docs
Welcome to Kanari Docs
Introduction
Quick StartSetup Node
Architecture
Protocol StackCheckpoints and Mysticeti DAGExecution and State
Operations
Multi-node DevnetRPC Gateway and LimitsSnapshot and Validator Backup
Security
Security HardeningTesting and Audit Coverage
CLI
Kanari Node CLIKanari CLIClient OperationsMove DevelopmentKeytool Operations
API Reference
API Reference
Guides
Transferring CoinsGas Model

Kanari Documentation

Welcome to Kanari Docs

Documentation for the current Kanari Network architecture.

Last updated

Kanari Network

Kanari Network is a Move-based object blockchain with a Mysticeti-style DAG metadata layer, transaction-driven checkpoints, RocksDB-backed state, and JSON-RPC surfaces for wallets, explorers, and SDKs.

The current system is optimized for deterministic execution and long-running validator operations:

  • Checkpoint height advances only when committed transaction work exists.
  • Empty network DAG vertices can be retained and synchronized without minting empty checkpoints.
  • Move execution tracks object/resource state, gas effects, dynamic fields, and deterministic state roots.
  • Nodes can recover with strict snapshots or encrypted full-validator backups.
  • RPC includes bounded heavy-VM execution and per-client protection, while public deployments should still use a real gateway or load balancer.

Key Features

  • Move VM execution: Object, resource, coin, NFT, dynamic-field, and module operations run through the Kanari Move runtime.
  • Mysticeti DAG metadata: Validators exchange DAG vertices and checkpoint evidence through libp2p.
  • Transaction-driven checkpoints: No transaction means no new checkpoint height, which avoids idle block production.
  • Verifiable state: RocksDB state is anchored by an SMT root and checkpoint metadata.
  • Operational recovery: Snapshot export/import and encrypted validator backup/restore cover node recovery paths.
  • Modern RPC surface: Axum JSON-RPC serves explorer, CLI, SDK, and gateway deployments.
Quick Start

Learn how to build and run the Kanari CLI.

Open resource Architecture

See the current layered protocol stack and data flow.

Open resource Multi-node Operations

Run a local 4-validator devnet and understand checkpoint sync.

Open resource Coin Transfer

Understand how to send and receive tokens.

Open resource API Reference

Integrate Kanari Network into your applications.

Open resource Security Model

Review key handling, RPC exposure, backup, and test coverage.

Open resource

Current mental model

One transaction passes through the RPC layer, enters the verified mempool, is selected into checkpoint work, executes in the Move runtime, updates persistent state, records DAG/checkpoint metadata, and becomes queryable through RPC and explorer indexes.

For operators, the most important invariant is simple:

Checkpoint height means committed chain work, not elapsed time.

That is why idle validators should stop producing new checkpoints until real transactions arrive.