Build the mechanism. Make the evidence inspectable.

Read the construction first

The white paper defines monetary state, native transitions, independent controllers, proofs and failure outcomes. Appendix A describes canonical objects and reference bounds. Its conditional arguments are the starting point for implementation and review, not evidence that older code already realizes the design.

Work on a named implementation

The protocol repository maintains node code, requirements and source-specific records. Follow its current local instructions and build guidance. Earlier candidates keep their own protocol identities and no-value evidence; a manuscript revision does not upgrade them. The Earth testnet guideconcerns that separately scoped testnet.

Where implementation and review matter

• Exact monetary execution, unique issuance slots and funded fees.
• Controller cancellation/release exclusion, durable locks and one-time redemption.
• Authenticated proof programs, complete current material and practical resource costs.
• Independent custody, succession, incident handling and archive recovery.
• Bounded discovery, durable carriage and explicitly scoped physical adapters.

Report the exact source, changed behavior, assumptions and remaining limitations. Preserve failed observations and distinguish compilation from runtime evidence. Keep experiments isolated from valuable assets and real monetary keys.

Contribute a correction or technical review

Use the protocol repository’s contribution workflow for code and mechanism review. Discuss public questions in the Nodes & Development forum. Website changes belong in the website repository and its issue tracker. The author’s published contact is dengrunlai@gmail.com. Keep signing material, backups and private node state out of public reports.