Build pages explain the public mental model and the module-owned invariants that an integration should respect.
Sections
- Architecture — custom DAG consensus, execution, canonical heads, and privacy.
- Smart contracts — EVM, Wasm, Velocity, precompiles, and adapter boundaries.
- Modules — capability-by-capability public reference.
Design principle
RP1 keeps accounting logic in the module that owns the invariant. A wallet, agent, Router, EVM contract, or relayer should prepare and call that boundary; it should not duplicate the chain’s math or bypass authorization with a second implementation.
Implementation access
The chain source repository is private. This site is the public protocol and integration reference; approved binary distributions and their provenance will appear in RP-ONE/rp1-releases. Internal source and operator documentation are not automatically public product or protocol guarantees.