Verify a satchel

Before you buy or accept one, check what its previous owners could have kept back. No wallet needed.

1
The contract can't sign behind the record
The contract account has no access keys, runs the reproducible build, and signs only through NEAR's canonical Chain Signatures contract. Nobody, its deployer included, can request a signature for a satchel's key except through sign_evm and sign_raw.
2
No signed transaction is still pending
The contract records the highest nonce it ever signed on each chain. Once the address's nonce at a finalized block is above it, every transaction a previous owner signed is either on chain or void.
3
No approval left behind
Every approve, increaseAllowance, setApprovalForAll and Permit2 approval the contract signed is itemized. Each one must read as revoked on chain: allowance 0, operator off, approval cleared.
4
Nothing the record can't explain
Raw signatures, calls the contract can't classify (multicalls, swaps, ownership transfers) and approvals over the cap are counted. Any one of them makes a satchel unprovable, and the report says so instead of guessing.