Attestation Explainer

WHAT IT DOES

Attestation Explainer takes an attestation contract address and an attestation ID, and provides a complete, plain‑language explanation of the attestation's current state. On-chain attestations are verifiable statements made by an attester about a recipient—often used for identity verification, credential issuance, or claim verification. If the attestation is revoked, expired, or invalid, it should not be relied upon. This tool reads the contract's state via public view functions—getAttestation, hasAttestation, isValid, isRevoked, expiry, attester, recipient, metadata, schema, name, symbol, and ownerOf. It fetches the current block timestamp and computes whether the attestation has expired (if time‑bound). Historical attestation events (AttestationCreated, AttestationRevoked, AttestationExpired, AttestationUpdated) are fetched using chunked, backoff‑aware log scanning to provide context on past changes. The output includes the recipient, attester, metadata, schema, validity status, revocation status, expiry date and time remaining, a status badge (Valid, Revoked, Expired, Invalid, or Does Not Exist), and a plain‑language explanation of the attestation's state and whether it is sufficient for a transaction.

HOW TO USE

Enter the attestation contract address followed by a colon and the attestation ID (e.g., 0x123...:5), select the network, and click "Explain attestation". The tool connects to your wallet via the EVM bridge (read‑only; it never signs or sends anything) to fetch the attestation state. It attempts multiple common attestation function signatures to maximize compatibility with different implementations (e.g., EAS, Verax, and custom attestation contracts). It fetches the current block timestamp for expiry calculations. Historical events are fetched in chunks (500 blocks per request) with automatic backoff and halving on failure to avoid public RPC caps. The AI layer generates a plain‑English explanation of the attestation's state, including whether the attestation is sufficient for a transaction. You can click on the contract, recipient, or attester addresses to view them on the block explorer.

CHUNKED LOG SCANNING WITH BACKOFF FOR ATTESTATION EVENTS

Attestation events (AttestationCreated, AttestationRevoked, AttestationExpired, AttestationUpdated) are essential for confirming attestation history, revocations, and expiry. However, public RPCs aggressively cap eth_getLogs block ranges; a full‑range request over 10,000 blocks will fail with a "block range too large" error. This tool automatically chunks log requests into 500‑block slices to stay within safe limits for all major RPC providers. If a chunk fails (due to timeout or provider‑specific caps), it halves that chunk and retries recursively—ensuring that even with aggressive caps, the tool reliably retrieves all relevant attestation events. The tool also filters logs by the specific contract address and relevant event topics to minimize data transfer and processing time. This is essential for detecting revocations and ensuring the attestation's current validity status is accurate.

WHAT IT CANNOT SEE

This tool cannot detect attestation validity that depends on off‑chain state (e.g., attestations that are verified by an off‑chain service, or attestations that rely on external data sources for validity). It cannot predict future revocations or expiry events that might occur before the transaction is mined—the verification reflects the current state, not the future. It cannot verify that the sender intended to present or interact with the attestation—the tool reads what is on‑chain, not the user's intent. It cannot detect risks for attestations that use non‑standard patterns (e.g., custom verification logic not exposed via view functions, or attestations that are bound to external identities). It cannot guarantee that a transaction will succeed even if the attestation appears valid, as other conditions (e.g., paused state, expired, or revoked) may also need to be met. It cannot detect if the attestation is blacklisted or flagged by external services (e.g., reputation blocklists). It cannot detect if the attestation contract is a proxy pointing to an implementation that may have been upgraded with different logic, which could change the behavior of validity or revocation functions. It cannot verify the cryptographic soundness of signatures or other verification methods—the tool relies on the contract's view functions to report validity and does not perform cryptographic verification itself. It also cannot detect if the attestation's metadata URI points to a valid or accessible off‑chain resource, or if the attested claims have been tampered with off‑chain.

PLEASE NOTE

This tool works only for EVM‑compatible chains (Ethereum, Polygon, BSC, Arbitrum, Optimism, Avalanche, etc.) and relies on standard attestation function signatures (getAttestation, hasAttestation, isValid, isRevoked, expiry, attester, recipient, metadata, schema, ownerOf). It does not support custom attestation logic that does not expose these functions as public view methods. All explanations are AI‑generated from data the app reads on‑chain—the AI synthesizes the attestation state, metadata, event history, and transaction context into plain English, but it does not have special access to private contract logic or off‑chain data. Always review what you are actually signing in your wallet before approving any transaction; an attestation explanation does not replace your own verification of the transaction details, including the target contract, the attestation ID, and the function you are calling. This tool is provided free of charge, with no warranty of accuracy or completeness.