Funding proof
Audit the bundle to inspect transaction-level support.
Audit the chain before trusting the lore.
Address syntax, a transfer, a wallet label, and a contract’s purpose are four different claims. Test each layer independently.
Claim bundle
Editable, source-derived JSON. Add transaction records or citations only when you can inspect them.
READY · source sample loaded
Entity attribution
Audit the bundle to separate labels from ownership evidence.
Purpose inference
Audit the bundle to inspect contract-purpose support.
Four layers.
Four burdens.
Four burdens.
What proves a funding hop?
A complete submitted record needs chain, transaction hash, block, sender, recipient, transferred asset, and amount. A valid address string or repeated appearance in a thread does not establish a transfer.
What proves an entity label?
A transfer can be genuine while a wallet label is wrong. Ownership or control needs an independent, inspectable citation such as an official disclosure, signed message, verified explorer label with provenance, or equivalent primary evidence.
What proves contract purpose?
Deployment chronology alone does not establish an AMD wrapper, peg mechanism, settlement test, or liquidity route. Those claims need bytecode or verified source, event logs, issuer documents, and measured behavior tied to the contract.