Separate vault accounting
The interface reads principal from the TicketVault deployment and keeps it separate from the displayed prize balance.
The interface points each major system role to a public deployment. Explorer links are the source of truth; product claims still require independent technical review.
The interface reads principal from the TicketVault deployment and keeps it separate from the displayed prize balance.
The DrawManager exposes the draw identifier, epoch start and epoch duration used by this interface.
The Morpho adapter has its own deployment address so the proposed strategy route can be inspected independently.
Every address used by the interface links directly to its Robinhood Chain Blockscout record.
Select an address to open its Blockscout record in a new tab.
0xA10DbDb13008bFf67a2B2702BC45667c3738164BPotCollectorPrize balance0x2d303aDBB47D8C447d56eA8219374a22B8e8D58aDrawManagerEpoch + draw state0x83180C5468d6237Cd95944c99FE8699943b62288MorphoAdapterStrategy adapter0xc41704C3eC1FC1eB927ABBD939E21dDEC99B82E0FeeForwarderFee routing0xF79F4c016B9cb0b87c1afE44ccB4801470614596Interface status is not an audit · verify bytecode, ownership and withdrawal conditions before use
The deployed TicketVault reports decimals() = 18 for its TICKET share token, but share balances are actually carried in 6-decimal USDG base units. Any wallet, explorer or aggregator that trusts the reported value will scale a TICKET balance by 1018 and show a figure that is a trillion times too small. This site and direct contract reads apply the correct 6-decimal scaling, so treat them as authoritative and ignore TICKET balances rendered elsewhere.