Documentation index
Docs

/ Module index

BUILD / MODULE INDEX

Choose modules by responsibility.

The repository groups modules by the job they perform. Start with product requirements, then choose the smallest useful set across chain basics, network infrastructure, and financial logic.

01

Read the module map

Module families are a navigation aid. A working application can use components from several families, and each deployment still needs an explicit runtime, participant model, data path, and operating plan.

02

Blockchain Basics

Core components for assets, cryptography, access, data, connectivity, and reusable application behavior.

Coins
Issue and account for application-native assets.
Crypto
Use shared cryptographic utilities for signing and verification.
RPC
Expose application state and actions through an interface.
DKG
Coordinate distributed key generation for threshold-controlled systems.
Bridge
Move messages or assets across system boundaries.
Oracle
Bring signed external data into application logic.
Chat
Study application messaging as a reference implementation.
Factory
Create and assemble reusable application components.
Open Blockchain Basics in the repository
03

Network Infrastructure

Components for authority and proof-of-stake based participation in a specialized network.

Authority
Define how privileged actions and state transitions are authorized.
PoS
Represent stake-based participation and network security.
Open Network Infrastructure in the repository
04

Financial Primitives

Purpose-built components for collateral, issuance, markets, balances, and other financial state.

Margin
Track collateral, exposure, and margin state.
Securities
Represent issued financial instruments and their state.
Vaults
Pool and control assets under defined accounting rules.
CLOB
Add deterministic central limit order book logic.
Derivatives
Represent contracts whose value follows another asset or rate.
Stablecoin
Model issuance, redemption, and stable asset accounting.
Open Financial Primitives in the repository
05

Chain Examples

Reference implementations that show how modules become working application chains and services.

Coins chain
Trace a chain built around asset state and transfers.
Bridge chain
Trace coordination and certificates across two networks.
Custom module
Study the extension path for application-specific behavior.
Open Chain Examples in the repository
06

Select a module set

Begin with the state and transitions that define the product. Add access, data, authority, and connectivity only when the workflow calls for them.

Product requirementModules to inspectQuestion to answer
Application-native assetsCoins, Crypto, RPCHow are assets represented, authorized, and queried?
External dataOracle, Authority, CryptoWho publishes data and how is it verified?
Threshold controlDKG, Authority, CryptoWhich actions require group authorization?
Order-book marketCLOB, Coins, Oracle, RPCWhich state transitions belong in market execution?
Cross-network flowBridge, DKG, AuthorityWhich messages and certificates cross boundaries?
A source-backed compositionSource
use nunchi_clob::ClobExtension;
use crate::CoinsRuntime;

pub type Application =
    nunchi_chain::Application<CoinsRuntime, ClobExtension>;

SOURCE OF TRUTH

Confirm APIs and maturity in the current workspace.

The module index explains responsibilities. The repository source, tests, examples, and lockfile define the exact API and dependency versions available for a build.