Modules
Choose from the 12 modules below, then use the examples to see how they connect to an application.
Core modules
| Module | Cargo package | Role in Alpha 1 |
|---|---|---|
| Coins | nunchi-coins | Coin and account models and their operations |
| Common | nunchi-common | Shared address, state-database, and runtime abstractions |
| Crypto | nunchi-crypto | Wrappers and primitives built on Commonware cryptography |
| RPC | nunchi-rpc | Interfaces for composing module RPC surfaces |
| DKG | nunchi-dkg | Distributed key generation, resharing, and consensus coordination |
| Bridge | nunchi-bridge | A consensus extension for verified foreign finalization certificates |
| Mempool | nunchi-mempool | A nonce-aware transaction pool used by admission, proposal, and finalization paths |
| Oracle | nunchi-oracle | Namespaced data storage for interpretation by application modules |
Network and execution modules
| Module | Cargo package | Role in Alpha 1 |
|---|---|---|
| Authority | nunchi-authority | Proof-of-authority network configuration |
| Narae | narae | Local testnet processes and a terminal log dashboard |
| Chain | nunchi-chain | Reusable chain runtime and application composition |
| CLOB | nunchi-clob | Central limit order book, deterministic matching, and validator replay |
Read the implementation boundary
CLOB
The CLOB module accepts signed order intents into validator-local books and verifies proposer match batches. It records fills; your application supplies settlement, balances, margin, funding, and liquidation logic.
ApplyMatchBatch is a consensus-extension payload. Submitting it through the normal transaction runtime is rejected.
Mempool
The pool keeps nonce-ordered queues by module and account. Admission uses committed nonce state, and proposals select executable nonce runs. The application's networking integration determines transaction propagation.
Data and cross-network input
Oracle stores namespaced records for application modules to interpret. Bridge carries verified foreign finalization certificates. Your application defines which publishers or foreign networks it trusts and how it uses those inputs.
Select a module set
| Starting point | Modules to inspect |
|---|---|
| Application-native assets | Coins, Crypto, RPC |
| External data | Oracle, Authority, Crypto |
| Threshold control | DKG, Authority, Crypto |
| Order-book market | CLOB, Coins, Oracle, RPC |
| Cross-network input | Bridge, DKG, Authority |