§ TRUST · MULTISIG A / B · Mainnet beta · unaudited
Security & governance
The contract is currently upgradeable and unaudited. This page states plainly who holds what power, where the limits are, and what happens if something goes wrong.
Network
Mainnet beta · unaudited
Audit
Unaudited
Upgradeable
Yes (multisig A)
Lock
Planned after audit
Roles
| Role | Can | Cannot |
|---|---|---|
| Multisig A Code upgrade rights | Publish and upgrade contract code | Operational switches (those belong to B) |
| Multisig B Governance account | Emergency pause, approve room creation, force-close rooms, set global parameters, hand itself over in two steps | Touch player balances or the house bankroll, change RTP or multipliers, make withdrawals fail, change session authorizations |
| Operator Room host | Create rooms (requires B's approval), fund and withdraw unlocked funds, adjust their own rooms' parameters, close rooms | Touch player balances, take locked funds |
| keeper | Call sweep to clear due shots (anyone can call it) | Everything else |
| Player | Fire, withdraw, authorize bots | — |
Pausing stops only firing, taking seats, holding seats and room creation; withdrawals, sweeps and room closing continue as usual.
Upgrade process
01Advance notice
The announcement channel and waiting period will be published before launch.
02A proposes
Only the payload's hash is stored on-chain.
03Independent checks
Other members rebuild the payload themselves from the same code commit and approve only if the hashes match.
04Execute
Executed once the threshold is reached. After the audit passes and operation is stable, it becomes non-upgradeable.
Contract addresses
| Name | Address |
|---|