Documentation status
eCoin is in the architecture and implementation-planning stage described by White Paper v0.1. The documentation is intentionally useful before mainnet while avoiding invented production parameters. Exact serialization, cryptographic primitives, validator thresholds, fee formulas, block timing, RPC endpoints, and SDK interfaces remain subject to implementation, testnet results, security review, and ECIP review.
The proposed system
At a high level, users authorize transactions cryptographically; nodes verify protocol rules; validators establish an accepted ordering and finalized ledger state; applications build payment and future utility experiences on top.
Choose a path
Developer Guides
Understand how the proposed eCoin system is intended to work.
SpecifyReference
Review draft data models, states, responsibilities, and protocol boundaries.
PrototypeExamples
Use implementation-neutral pseudocode to model common flows safely.
UnderstandGlossary
Use consistent language across wallets, nodes, validators, and payments.
Developer principles
- Do not assume mainnet behavior. Draft examples are conceptual until a production specification says otherwise.
- Verify rather than trust. Nodes and clients should validate the information required for their operating mode.
- Security before convenience. A fast interface cannot compensate for weak authorization or ambiguous finality.
- Version everything. Protocol and API changes should be explicit, testable, and documented.
- Use ECIPs for significant changes. The proposed governance path is public documentation, review, testnet implementation, security evaluation, and announced activation.