Where we are.
Where we're going.

The correct order: finish the custom chain and operator platform → harden docs and testnet UX → then build execution features on top.

Phase 1 · Complete

Chain Foundation

PoW mining, signed transactions with nonces, mempool policy, P2P block propagation, persistent state, wallet toolkit.

PoWsecp256k1MempoolP2P WebSocketsDocker Testnet
Phase 2 · Complete

State Layer & App Modules

Deterministic key-value state derived from payload transactions. Pending state preview. Counter, registry, profile, todo, notes modules.

State EngineTyped Txs5 App ModulesReceipts
Phase 3 · Complete

CLI & HTTP API

Full terminal explorer and operator toolkit. HTTP REST API covering all chain operations. Docker-based 3-node testnet. Automated tests and CLI smoke tests.

CLI ToolkitHTTP APIFaucetnpm package
Phase 4 · In Progress

Hardened Docs & Testnet UX

Comprehensive documentation. Polished first-run experience. Stable release workflow. Better sync diagnostics. Extended test coverage.

DocsDX PolishRelease Hygiene
Phase 5 · Planned

Execution Layer

Richer payload schemas. Account-owned state partitions. Deployment-like actions. Isolated module execution rules. Contract-like semantics — built on top of the solid chain foundation.

Execution EngineState PartitionsDeploy ActionsVM-lite
Phase 6 · Future

Platform Features

Richer validator economics. Optional gas metering. External tooling integrations. Public testnet deployment. Developer SDK.

SDKPublic TestnetGas Metering
NOT YET — INTENTIONALLY OUT OF SCOPE FOR NOW
Smart contracts / bytecode
VM / gas metering
Ethereum JSON-RPC
MetaMask-native RPC
Public validator economics
Market-priced assets

That’s intentional. Duglas is a blockchain runtime + deterministic state engine + fixed app modules — not a general-purpose contract platform. Yet.