master.parity
- Version
- 0.1.0
- Desk
The rate at which a StablePair pool pins two issuers' tokens of the same stock to each other.
Changelog
| Version | Date | Change |
|---|---|---|
0.1.0 | 2026-11-11 | First version. |
What it measures
For each StablePair pool between a Robinhood token and an Ondo token of the same stock, the reference rate the pool's hook stores: sibling tokens per one of the token being checked (reference_rate). It does not measure the rate the pool trades at, and it does not say that the two tokens are worth the same.
Inputs
feeConfig(poolId)on the StablePair hook (0xd061f665d1c4816787fceaa168fa66c59d3abcc0). The fourth word of the answer isreferenceSqrtPriceX96: the square root of token1 per token0, in raw units, as a Q96 number.- The pools found by
master.pools, read daily. - The decimals of both tokens, as stored with each token:
- a Robinhood token's is the registry's
tokenDecimals, read every 6 hours bymaster.registry-sync. The token's record is written in full from one registry response, the one itslistingfigure names, so that response states the stored decimals. No decimals are ever assumed: an entry that does not statetokenDecimalsas a whole number from 0 to 36 is not read, and nothing is written from it. - an Ondo token's is the answer of its own
decimals(), read every 6 hours bymaster.ondo-sync. It is stored with the block of a read that gave it: the block moves only together with an answer, and a read that fails, or adecimals()the run's call did not read, changes neither the value nor the block.
- a Robinhood token's is the registry's
The rule
Price of token0 in token1, in raw units: (referenceSqrtPriceX96 / 2^96)^2. It is adjusted for the two tokens' decimals and, when the token being checked is token1, inverted. The result has 18 decimal places, rounded down.
No decimals are assumed. When either token's decimals have no stored read, for example because its record could not be read with the pool, no parity record is given for the pool. The pool is still listed among the token's pools.
The rate is a stored value, not a feed. It is not 1.0 for every pair: on 2026-11-10 seven of the eleven pools held another value, from 1.000939 (NVDA) to 1.017138 (GME) Robinhood tokens per Ondo token.
On 2026-11-10 one externally owned account held every role on this hook on Robinhood Chain, including the one that changes a reference rate, as read at the head that day. No job reads the roles again, so this page states them as of that day only. A changed rate is recorded on the parity record with the block it was read at. It is not a notice in Phase 1.
Thresholds
None.
Terms
None.
Evidence
Every value the rate rests on has an evidence item. reference_rate, keyed by the pool ID, names in this order:
- the call
feeConfig(bytes32)on the hook with the pool ID, at its block; - the read of token0's decimals, then the read of token1's: for a Robinhood token, the registry response its record was written from (URL, fetch time, SHA-256), which states
tokenDecimals; for an Ondo token, the calldecimals()on the token at the block of the read that gave the stored value.
The figure's window runs from the first of its chain reads to the last. The parity record's readAt is the block and time of the feeConfig read.
Recomputation
pnpm tool packages/master/recompute.ts --envelope answer.json --rpc <endpoint> reads feeConfig and decimals() of both tokens of the pool again, and recomputes the rate from the side of the token in the answer. A Robinhood token's decimals are the registry's statement, which the figure names by its SHA-256: the script reads the token's own decimals() in its place, so a registry that states other decimals than the token answers shows as a mismatch. No free endpoint serves past state, so without an archive endpoint the script re-reads at the head block and says so.
Ways to game it, and what the method does
| Way | What the method does |
|---|---|
A pool built with another hook to look like a parity pool | Only pools with the StablePair hook's key and a stored reference are parity records. |
The hook's role holder changes the rate | The new rate is recorded with its block at the next daily read. Who held the role on 2026-11-10 is stated above. |
An Ondo token whose decimals() changes or stops answering | A new answer replaces the stored value and its block together, at the next 6-hourly read; a failed read leaves both as they were. The rate follows the stored value, and the evidence names the read that gave it. |
Limits
- The rate is read once a day: a change and its reversal within a day are not seen.
- Only StablePair pools between the two issuers' tokens of one stock are read.
- A Robinhood token's decimals are the registry's statement. This method does not compare them with the token's
decimals(); the recomputation script does. - When a registry response does not state
tokenDecimalsfor a token, the entry is not read (master.listing, "An entry that cannot be read"). A token stored from an earlier response keeps the decimals that response stated, and its rate keeps naming that response. A token that was never stored has no record, and so no parity record. Every token of the recorded response of 2026-11-10 states 18. - Decimals are re-read every 6 hours: a rate shown between a token's change of decimals and the next read uses the decimals stored before it.
What overlaps elsewhere
The rate a StablePair pool stores is public on chain, through the hook's feeConfig(poolId), and explorers show a pool's state. This method reads that rate for each pool of a listed token, gives it from the side of each of the two tokens with both tokens' decimals, and names the read behind each figure.