RP1 preserves the Cosmos SDK application and module model while replacing the default block-production path with a custom DAG consensus runtime. That distinction matters when you operate a node, query a block, or reason about finality.
Runtime map
rp1d start
→ custom DAG start command
→ consensus server and RPC/API services
→ workers + primary + DAG + Bullshark + QUIC
→ consensus executor
→ ChainApp.FinalizeBlock and Commit
→ Cosmos SDK modules and keepersRead next
The public site intentionally stops at the protocol and operator mental model. Recovery WAL details, private topology, internal optimization techniques, and secret-dependent deployment material remain in the appropriate internal engineering context.