Security and trust
The settlement value is a public number anyone can check at the New York Fed. RSTAR's job is to copy it faithfully, give a window to catch a bad copy, and never let any key touch the money that backs the tokens.
Who can do what
| Role | Can | Cannot |
|---|---|---|
| Anyone | mint and redeem pairs, fold ready prints, settle a finished month, redeem settled tokens, settle by fallback 45 days after month end | post, dispute, correct, list, claim fees |
| Keeper | post prints, dispute a pending print | correct or void prints, list markets, claim fees |
| Authority | list markets; post, correct and void prints inside their window; claim fees; rotate roles; close finished markets | move vault USDC, change the fee, the collar width, the window or the fallback |
| Upgrade authority | call init_config once, upgrade the program | anything else |
Constants no key can change: the 10 bp mint fee, the 24-hour window, the plus and minus 2.5 pp collar, the 7-day seed lookback, the 45-day fallback and the 25% rate ceiling.
Handing over authority takes two steps: update_config names a pending authority and only that key's own accept_authority signature completes the handover, so a typo cannot lock the protocol.
Money paths
- Vault. Owned by the market PDA. Only
redeem_pairandredeem_settledpay out of it, and only to the redeemer. - Treasury. Owned by the config PDA. Only
claim_protocolpays out of it, capped by what each fee share has accrued. - No freezing. The tokens have no freeze authority, so no key can lock a holder's balance.
- Fee rounding. The mint fee rounds up per mint, so splitting a mint into small pieces pays more, never less.
- Account substitution. Config and market accounts are checked by owner and kind byte; vaults, mints, the treasury and the quote mint are compared to the addresses stored on chain; token and system programs are compared by id. The engine's tests swap each one and get an error.
- Initialization race.
init_configmust be signed by the program's upgrade authority, read from its ProgramData account, so nobody can initialize first after deployment. - Pre-funded addresses. Creating a PDA tops up, allocates and assigns, so lamports sent to a future market address cannot block its listing.
The print oracle
| Risk | What happens |
|---|---|
| The NY Fed revises a print | Revisions happen only until about 2:30 p.m. ET on the publication day. The program refuses a post before 19:30 UTC on the next day, so the keeper always copies the revised number. |
| The keeper posts a wrong rate | Inside 24 hours the keeper or authority disputes it and the authority corrects it. A disputed print stays open to the authority until resolved and blocks later prints from folding. |
| The keeper posts a wrong date | The authority voids from that entry and the keeper posts again in order. |
| The keeper goes quiet | Nothing folds and nothing breaks; the month waits. The keeper resumes from chain state and catches up 8 prints per window. The authority can also post. |
| Keeper and authority both gone | 45 days after month end anyone can settle with the last folded rate carried forward, or the listing midpoint if no print ever folded. |
Measured history: 1 revision in 2,724 official prints from January 2016 to November 2026 (May 31, 2017).
Closing a finished month
close_market is the authority's way to recover the market and vault rent (the two mints stay, since they have no close authority). It requires that the market settled at least 90 days ago and that no LONG or SHORT worth more than $0 is still outstanding, checked against the live mint supplies. USDC left in the vault at that point is rounding dust (each redemption rounds down by under one base unit) or a donation, and it moves to the treasury as fee. A holder can never lose a claim to a close. A closed month can never be listed again: its two mints still stand at their addresses, so a new listing for that month fails, and no old token can ever meet a new vault.
Tests behind these claims
The engine runs 20 unit tests, a 129-month history replay, 13 LiteSVM lifecycle tests that cover every instruction and its error paths, and a validator crash test that kills the chain mid-month and finishes the month from chain state alone.