The correct order: finish the custom chain and operator platform → harden docs and testnet UX → then build execution features on top.
PoW mining, signed transactions with nonces, mempool policy, P2P block propagation, persistent state, wallet toolkit.
Deterministic key-value state derived from payload transactions. Pending state preview. Counter, registry, profile, todo, notes modules.
Full terminal explorer and operator toolkit. HTTP REST API covering all chain operations. Docker-based 3-node testnet. Automated tests and CLI smoke tests.
Comprehensive documentation. Polished first-run experience. Stable release workflow. Better sync diagnostics. Extended test coverage.
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.
Richer validator economics. Optional gas metering. External tooling integrations. Public testnet deployment. Developer SDK.
That’s intentional. Duglas is a blockchain runtime + deterministic state engine + fixed app modules — not a general-purpose contract platform. Yet.