Proof

Check every number without trusting us.

Every address, the treasury read straight from Robinhood Chain by your own browser, every dollar in and out, and the source code with the steps to rebuild it. Where something is not live yet, this page says so.

Addresses

Who is who on chain

Steward and council are read from the contract itself, not from this server. Each address links to the explorer.

Reading the chain…
Live state

The treasury, read in your browser

These numbers come from a public Robinhood Chain RPC, called by this page. Our server is not in the path.

Status
…
Treasury

Every dollar in and out

Every Funded, WithdrawalAnnounced, WithdrawalCancelled and Withdrawn event. Loans and repayments are on Agents.

EventAmountFrom / toWhen (UTC)Tx
Loading…
Source code

Rebuild it yourself

One Solidity file, no proxy, no upgrade path. Build it with the settings below and the result must match what is on chain, byte for byte.

Compiler settings

Source
contracts/src/RoundTable.sol
Compiler
solc 0.8.28
Optimizer
on, 200 runs
EVM version
cancun
Metadata hash
ipfs
Constructor
usdg, registry, steward, council

Tests

Run with Foundry: forge test

Result
36 passed, 0 failed
Unit and fuzz
34, including 2 fuzz tests at 1,000 runs each
Handler smoke
1
Invariants
1 suite, 4 invariants, 256 runs × depth 64

The invariants: the books balance to the last unit, outstanding principal always equals lent minus repaid minus lost, no agent ever owes more than its line or holds a line above the ladder, and idle USDG always covers every open line.

Compare the deployed bytecode

The deploy transaction's input is the compiled creation code followed by the four constructor arguments. Rebuild, encode the arguments, and compare. The runtime code (cast code) differs from deployedBytecode only where the two immutable addresses are filled in, so the creation code is the cleaner check.

cd contracts
forge build
forge test                    # 36 tests passed

# the steward and council at deploy are in the deploy transaction's
# StewardAccepted and CouncilSet events
CODE=$(forge inspect RoundTable bytecode)
ARGS=$(cast abi-encode "constructor(address,address,address,address)" \
  <USDG> <REGISTRY> <STEWARD_AT_DEPLOY> <COUNCIL_AT_DEPLOY>)
INPUT=$(cast tx <DEPLOY_TX> input --rpc-url <RPC>)
[ "$INPUT" = "$CODE${ARGS#0x}" ] && echo MATCH || echo DIFFERENT
Status

Live, and not live yet

Driven by the same configuration the site runs on. Nothing here is typed by hand.

Checking…
The seven checks

Where each check lives

Each knight is one function. Read it, run it, and compare its result with the evidence in any verdict. What each one checks

SeatKnightCodeAlso uses

The verdict is assembled and sealed in server/table.mjs (canonical JSON, keccak256, seal). Outside URLs are fetched through server/fetchsafe.mjs: https only, private addresses refused, size and time limits. The rules the contract enforces are in contracts/src/RoundTable.sol.