Documentation · 03 / 06
ABI confidence model
Verified, reconstructed, ambiguous and unresolved, and what each one promises.
Every function and event carries a provenance stamp. The border style and the word carry the meaning, never colour alone.
| Stamp | Level | Meaning |
|---|---|---|
| VERIFIED (solid) | confirmed | The selector appears in a verified ABI (Blockscout or Sourcify) for this address or its confirmed implementation. Names, types and mutability come from that ABI. |
| RECONSTRUCTED · HIGH / MED (dashed) | candidate | Found in bytecode with exactly one public text signature. HIGH when the database marks it as used by a verified contract, MED otherwise. Input types are inferred; names, outputs and mutability are unknown. |
| RECONSTRUCTED · LOW (dashed) | ambiguous | Found in bytecode with several matching signatures. All are listed; none is preferred. ENTROPY will not call it. |
| UNKNOWN (hatched) | unresolved | Found in bytecode with no known signature. Only the selector is shown. |
| LIVE @ BLOCK n | read | A value read from the chain at the stated block. |
Disclaimer Link to Disclaimer
A match is evidence, not proof
Selectors are extracted heuristically from dispatcher patterns and may be incomplete. A matching 4-byte selector does not prove a function's identity; only verified ABIs are confirmed.
Reading reconstructed functions Link to Reading reconstructed functions
A single-match candidate can be read: ENTROPY builds the call from the text signature as a view function with no declared outputs, and returns the raw return data. It never decodes outputs it cannot know.
Resolution meter Link to Resolution meter
Resolved = verified + reconstructed (single match). Total = every function entry. Ambiguous and unresolved selectors count as not resolved.