ERC-TRUST from
@Oraclizer runs regulatory actions on security tokens: six typed actions, fail-closed, one receipt each. It builds on ERC-8319, which I co-authored with
@robviglione and
@DanSpuller, and our proofs ran on tools from
@certora and
@rv_inc.
github.com/Oraclizer/erc-tru…
ERC-7943 built in, ERC-3643 plugs in.
Dan wrote ERC-8319's policy principles, and ERC-TRUST lives by them: a technical capability is not a legal obligation, the chain carries out decisions made through due process and never makes them, and compliance stays modular, so no market is forced into another's rules.
Certora's Prover checked our rules that the ERC-3643 adapter can never claim Full and that its receipts carry the token's real restriction state. With Runtime Verification's KEVM and Kontrol, we proved on the compiled bytecode that raw freeze and forced-transfer calls stay closed, that failures and non-raising freezes leave state untouched, and that LIQUIDATE moves exactly its amount and ends with its receipt.
Thank you, Rob and Dan, and the Certora and Runtime Verification teams.