What exists today
The current public technical foundation is the eCoin White Paper v0.1 and this documentation set. Version 0.1 proposes cryptographically authorized transactions, a peer-to-peer node network, stake-secured Byzantine Fault Tolerant validator consensus, a shared ledger, self-custody support, ECIPs, and a staged path toward testnet and mainnet.
A production node, SDK, RPC service, public testnet, final transaction serialization, and final network parameters are not represented here as already available.
Recommended reading order
- Read White Paper v0.1 for the system-level design.
- Read Ledger & Consensus to understand state and finality.
- Read Transactions and Wallets.
- Review P2P Network and Validators & Consensus.
- Use the Reference and Examples sections when prototyping.
How status language works
Prototype without coupling to unfinished details
Developers can model eCoin integrations around stable conceptual boundaries: prepare a transaction, authorize it, submit it to a network interface, observe its status, and act only after the required finality state. Keep address formats, field encodings, method names, timing assumptions, and fee rules configurable until the production specification is published.