Economic control
Reserve Engine
RS-FLOW Reserve Controller/Vault foundation and Keeper reserve operations are implemented and exercised through accepted test and rehearsal paths with fail-closed safety controls. The engine is not an active production Mainnet controller.
Separation of roles
01
Platform
Authenticated economic events and settlement requests originate here.
02
Reserve Controller
Policy, command validation, and safety checks before any vault action.
03
Reserve Vault
Enforcement boundary. Issuance is not a discretionary platform mint.
04
RS-FLOW primitive
The utility token. It holds no governance authority and no reserve logic of its own.
Safety controls
Authenticated economic settlement binding
Reserve actions bind to authenticated settlement intent, not an unverified client request.
Reserve Vault enforcement
The vault is the enforcement point for issuance, not an informal operator script.
CPI-only Reserve issuance
Issuance is constrained to program-derived calls rather than open minting.
Replay / idempotency protection
A command cannot be applied twice as two issuances.
Rolling issuance controls
Issuance can be bounded across time windows.
Oracle safety checks
External price or state inputs are treated as fail-closed inputs, not trusted blindly.
Circuit breakers
Abnormal conditions can halt issuance.
Founder 3-of-5 multisig governance
Founder governance is targeted to a 3-of-5 Squads vault. Local cloned-program creation and semantic verification passed; the real Devnet Founder multisig is not yet created.
Immutable audit lineage
Commands and outcomes are intended to form an append-only operational record.
Command expiration
Stale commands do not remain indefinitely valid.
Atomic rollback
Failed or partial application is designed to revert rather than leave a half-applied economic state.
Founder RS-FLOW channel
Founder RS-FLOW allocation channel
Founder RS-FLOW circulation is a separate channel from Reserve-controlled economic issuance. Delivery is restricted to the designated Founder Circulation Wallet. The platform records intended allocation configuration for audit; it does not publish operational keys or private endpoints.
What this page does not disclose
Private operational keys, KMS secrets, private endpoints, and other security-sensitive implementation details are not published on this website.