VERIFYClaims, contract, evidencereading the chain…

Don't take
our word for it.

Each claim on this site, its status, and the first on-chain transaction that shows it working. Contract facts below are read live with eth_call; activity numbers are counted from the contract's own event log.

01The contract
Status
Loading…
02Claims and evidencefirst transaction for each
Loading…
03What the owner key can and cannot do
Can
  • Set the charter tokenonce, ever
  • Set the charter minimumsetCharterMin
  • Choose where fees gosetFeeRecipient
  • Hand over ownershiptransferOwnership
Cannot
  • Move account, vault or queued fundsno function exists
  • Pause the bank or an accountno function exists
  • Change the fee rate or capconstants
  • Upgrade the codeno proxy
04How the numbers are counted

Open data: /api/proof · /api/stats · /api/activity

05Source and tests
.sol

BlackveilBank.sol

Solidity 0.8.28 · MIT · single file, no imports

The exact source deployed on chain. Verified on Sourcify (exact match) and Blockscout (full match) — the Sourcify status above is fetched live.

Read source
test

20 tests, one against real USDG

forge test · fuzzed accounting · fork of Robinhood Chain

Unit tests for every path (fees, handles, charter, mandates, queue, revoke, requests), a fuzz test that the USDG held always equals what the contract owes, and a fork test that runs the full flow against the real USDG token on Robinhood Chain.

Passing
plan

Encrypted balances

not deployed

Hiding amounts needs zero-knowledge circuits and an on-chain verifier. They are not live, and no page on this site says they are. When they ship, the verifier address and circuit source will be listed here first.

Planned