Skip to content

Glossary

Public

The RP1 terms used across the public architecture and integration docs.

Updated View as Markdown

DAG consensus

RP1’s production consensus path builds and orders a directed acyclic graph of certificates before the application executor finalizes and commits state. It is not the default CometBFT block-production lifecycle.

Narwhal

The transaction availability and certificate pipeline used by RP1 workers and the primary. Workers batch transactions; the primary creates vertices and certificates that carry the data needed for ordering.

Bullshark

The ordering and commit layer that turns the certified DAG into an ordered execution sequence.

UTA

Universal Trading Account: a unified account for collateral, positions, funding, margin health, and liquidation flows across supported markets.

Instawrap

RP1’s cross-chain wrapping and proof/relayer surface for supported EVM, Bitcoin, and Solana flows. It is not a general-purpose runtime for executing another chain inside RP1.

MPP

Machine Payments Protocol-style charge flow. RP1 V1 creates on-chain native charges and payment challenges; HTTP 402, gateway credential handling, webhooks, and external payment-provider behavior remain off-chain.

Velocity

RP1’s script and intent-oriented workflow surface, including a Solidity-facing EVM precompile for supported Wasm and bridge-related operations. External runtimes remain bounded by explicit adapters.

Vaults V1

A native, idle-only vault kernel with deterministic shares, isolated custody and claim escrow, bounded asynchronous redemption epochs, and role/pause boundaries. It does not connect arbitrary contracts, leverage, DEX, lending, or agents in V1.

Canonical head

The head projection used by RP1’s status and block-specific RPC policy. An application commit may briefly be ahead of a complete retained consensus header; public block data must not be fabricated from that incomplete state.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close