Skip to content

Institutional settlement

Preview

Build reserve-backed money movement, treasury controls, and evidence-first operator workflows on RP1.

Updated View as Markdown

Institutional systems need more than a token balance. They need reserve accounting, issuance controls, redemption availability, policy approval, transaction evidence, and a clear separation between demo data and live attestation.

Full-reserve issued stables

The RP1 stables surface supports governance-approved institutional stablecoins with a strict one-to-one reserve boundary:

  • configured reserve denom is deposited before circulation is minted;
  • issued supply cannot exceed the configured cap or available reserves;
  • total_supply must equal total_reserves;
  • pausing issuance does not block redemption;
  • the reserved bank/ denom namespace is not available to arbitrary-denom minters.

This is a product and accounting invariant, not a claim that an external bank account is automatically attested by the chain. Off-chain reserve evidence and institutional controls still need their own governance and reporting process.

Treasury and operator surfaces

The enterprise module provides enterprise/member/role, treasury, payment-request, and approval-oriented surfaces. The RP1 Bank application presents an invite-only, evidence-first operator experience for instruments, counterparties, rails, mint/redeem actions, transfers, and reserve posture. Demo data is labeled and must not be presented as live attestation.

Non-custodial conversion

The Router MVP is a browser-owned conversion surface for executable RP1-local DEX and StableSwap routes. It:

  • discovers real pools and reserve coverage;
  • prepares unsigned Cosmos instructions;
  • lets a compatible wallet sign locally;
  • persists activity in the browser;
  • verifies returned transaction bytes before marking execution complete.

It does not hold keys, create liquidity, fabricate quotes, or promise IBC, InstaWrap, or RFQ execution when those connectors are unavailable.

Operational evidence

An institutional integration should persist the signed envelope, transaction hash, chain ID, height, execution code, gas, and the relevant reserve or policy evidence. Use the transaction lifecycle reference to separate submission, observation, and completion.

See issued stables, enterprise and treasury, Router, and RP1 Bank.

Navigation

Type to search…

↑↓ navigate↵ selectEsc close