Every position witnessed. Disclosure only when asked.
Monad testnetReading chain…
Check this without trusting it
Every claim below names the call that confirms it. The register is 0xeBBA114d…A09AF1CA on Monad testnet (chain 10143), and each line is a read — nothing here needs a key, a wallet, or this site.
The order that matters is request before answer. Block numbers below are read from the transaction receipts, not from this bundle, so a reordered or back-dated claim would show up as an answer at or before its own request.
Requests with no answer
These were posted on chain and never closed. A proof cannot be produced for a claim that is false, so the register does not answer them — and auditAnswered still reads 0 for each, which is the contract saying so rather than this page saying so.
no proof exists — the request stays openrange disclosure
“is this position inside the 100–400 reporting bracket?”
no — no proof exists for this claim, so the request stays open
One row per closed request. The claim column is the figure the auditor named, hashed into the contract before a proof for it existed — the English question is bound to that hash, not captioning it.
Audit requests answered on chain, with the block each was requested and answered in
Question
Claim hashed in
Requested at block
Answered at block
Blocks between
is this position at most 500 SAKSIAZEV?yes — position <= 500, figure not disclosedrequest tx → verification txcast call 0xeBBA114d9870c98250239aCaFbcccc4dA09AF1CA "auditAnswered(uint256)(uint8)" 14748143691984800385519342567067184548374653976624912528944939287094902489264 --rpc-url https://testnet-rpc.monad.xyz
disclose this position in full459.9 SAKSIAZEVrequest tx → verification txcast call 0xeBBA114d9870c98250239aCaFbcccc4dA09AF1CA "auditAnswered(uint256)(uint8)" 15295565607428034115248977872195151026313000968512020945728292918132337157695 --rpc-url https://testnet-rpc.monad.xyz
is this position inside the 400–500 reporting bracket?yes — inside the bracket, figure not disclosedrequest tx → verification txcast call 0xeBBA114d9870c98250239aCaFbcccc4dA09AF1CA "auditAnswered(uint256)(uint8)" 7412764500531938265613304780261123397322939960196952595700843105723467459546 --rpc-url https://testnet-rpc.monad.xyz
is total exposure across all 4 registered positions at most 2,000 SAKSIAZEV?yes — sum of 4 positions <= 2,000, no individual position disclosedrequest tx → verification txcast call 0xeBBA114d9870c98250239aCaFbcccc4dA09AF1CA "auditAnswered(uint256)(uint8)" 12659808586463579490234724969239328805969036007299787163214811606579396264640 --rpc-url https://testnet-rpc.monad.xyz
is this position at most 600 SAKSIAZEV?yes — position <= 600, figure not disclosedrequest tx → verification txcast call 0xeBBA114d9870c98250239aCaFbcccc4dA09AF1CA "auditAnswered(uint256)(uint8)" 11992816547940957941462159611436375381387009486915845928999542522128103545058 --rpc-url https://testnet-rpc.monad.xyz
is total exposure across all 3 registered positions at most 2,000 SAKSIAZEV?yes — sum of 3 positions <= 2,000, no individual position disclosed
Correction — The register held FOUR live positions when this was answered. The enumerator reclassified the fourth — belonging to another holder — as retired, because its retirement count was derived from what this ledger could open, which is circular. The answer is true of the three it names and is NOT a statement about the register. The guard now counts retirements from the chain and refuses rather than trimming.
The files this page ships with were written by an operator; the right-hand column is read from Monad in your browser, now. Where they differ, the chain is the record.
cast is Foundry’s read tool; every command above is a view call that costs nothing and signs nothing. The same values are on 0xeBBA114d…A09AF1CA if you would rather click than type.