RP1 is a Cosmos SDK-based Layer 1 with a custom DAG consensus runtime and an application surface designed for high-throughput settlement, private finance, unified trading, and machine-operated workflows.
These docs are written for people and agents who need to decide whether RP1 fits a workflow, connect safely, or operate a node. They describe public capabilities and trust boundaries; they do not publish private validator topology, secret-dependent implementation techniques, or unreleased partner details.
Find your path
| You want to… | Start here |
|---|---|
| Send a first testnet transaction | Getting started |
| Build a wallet, service, or agent | Integrate |
| Understand the chain runtime | Build |
| Evaluate a product workflow | Use cases |
| Run or monitor infrastructure | Operate |
| Join the live testnet validator set | Join as a validator |
| Check an exact public fact | Reference |
What RP1 brings together
A settlement-oriented runtime
RP1 uses Narwhal workers, a DAG of certificates, Bullshark ordering, a consensus executor, and QUIC networking around a Cosmos SDK application. The public mental model is simple: transactions enter a lane-aware admission path, are ordered by DAG consensus, execute through the application, and become observable through canonical RPC and API surfaces. See consensus and execution.
Native financial primitives
The chain includes an AMM and order-book DEX, frequent batch auctions, universal trading accounts, lending, liquidity aggregation, oracle feeds, stablecoin/CDP surfaces, fee burn, validator momentum, and halving-aware supply behavior. The market infrastructure guide shows how these pieces fit together.
Privacy and programmable interoperability
Groth16 shielded pools, nullifiers, commitments, viewing-key controls, native EVM execution, CosmWasm/Velocity workflows, IBC, and InstaWrap connectors make it possible to compose private and cross-chain settlement flows without pretending that every external runtime executes inside RP1. Start with private finance or cross-chain settlement.
Agent-ready commerce
The AI module exposes discoverable capabilities and intent-shaped operations. The native MPP charge rail lets a service create a charge, publish a payment challenge, settle a native RP1 transfer, and return the off-chain API or tool response. Agentic commerce documents the flow and its deliberately narrow V1 boundary.
Availability language
Throughout the site:
- Public means the source and interface are documented for external use.
- Testnet means the flow is intended for the public testnet reference and still requires environment-specific verification.
- Preview means the surface exists in the product or source tree but should not be treated as a universal production guarantee.
- Planned means a design direction or typed boundary, not an executable promise.
- Excluded means a deliberate safety or scope boundary, not a missing documentation task.