RP1 documentation is intentionally capability-forward and mechanism-conscious. Readers should be able to evaluate a workflow, integrate safely, and understand its trust boundary without receiving information whose value depends on secrecy.
We publish
- Public transaction, query, REST, gRPC, RPC, EVM, and SDK surfaces.
- Product capabilities and supported user journeys.
- Security properties, role boundaries, pause controls, failure states, and recovery expectations that integrators need.
- Architecture mental models that explain ordering, execution, privacy, interoperability, and observability.
- Testnet instructions and evidence-backed operational requirements.
We do not publish
- Private keys, mnemonics, credentials, signing material, or secret configuration.
- Private validator topology, undisclosed peer addresses, or access-control details.
- Unreleased partner, customer, deployment, or incident information.
- Internal benchmark fixtures or exact optimization techniques when revealing them would weaken the system.
- A roadmap item as if it were a production guarantee.
How to read availability labels
| Label | Meaning |
|---|---|
| Public | Intended for external use, subject to normal endpoint and governance checks. |
| Testnet | Available on the public testnet or testnet workflow; verify live state before sending value. |
| Preview | Present in the product or source but not a universal production promise. |
| Planned | A designed boundary or future direction; no executable guarantee. |
| Excluded | Deliberately outside the current scope or security model. |
If a page and the chain source disagree, follow the source and open a documentation fix. Do not paper over a mismatch with vague language.