Grant Vesting Schedule Explainer

WHAT IT DOES

Grant Vesting Schedule Explainer takes a grant vesting contract address (e.g., from a DAO or grant program) and provides a complete, plain‑language breakdown of the grant's vesting state. It reads the contract's state via public view functions—grantId, recipient, token, totalAmount, claimedAmount, releasedAmount, startTime, cliffDuration, vestingDuration, revocable, revoked, lastClaimedAt, nextClaimableAt, and claimableAmount. It fetches the current block timestamp and computes the elapsed time, remaining time, vesting progress, cliff status, and the amount currently claimable (released - claimed). It also retrieves the token's symbol and decimals for human‑readable amounts. Historical grant events (GrantCreated, GrantClaimed, GrantRevoked) are fetched using chunked, backoff‑aware log scanning to provide context on past claims and revocations. The output includes the recipient address, token name, total grant amount, amount already claimed, currently claimable amount, start and cliff/end dates, vesting progress, revocation status, and a plain‑language explanation of the grant's state and whether a claim transaction will succeed.

HOW TO USE

Paste a grant vesting contract address into the input field, select the network, and click "Explain grant". The tool connects to your wallet via the EVM bridge (read‑only; it never signs or sends anything) to fetch the contract's state. It attempts multiple common grant vesting function signatures to maximize compatibility with different implementations (e.g., OpenZeppelin's VestingWallet, DAO grant contracts, and custom grant programs). It fetches the current block timestamp for schedule 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 summary of the grant state, including whether a claim transaction would succeed. A visual progress bar shows the vesting progress. You can click on the contract address or any address to view them on the block explorer.

CHUNKED LOG SCANNING WITH BACKOFF FOR GRANT EVENTS

Grant events (GrantCreated, GrantClaimed, GrantRevoked) provide essential context—for example, confirming that a grant was created, tracking when claims were made, and detecting if the grant was revoked. 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 grant events. The tool also caches the current block timestamp at the start of the scan to maintain consistency across all calculations and event fetches, preventing off‑by‑one errors when the chain advances during the scan. This is essential for accurately computing vesting progress and claimable amounts.

WHAT IT CANNOT SEE

This tool cannot detect grant vesting schedules that depend on off‑chain state (e.g., grants that are managed by an off‑chain service or based on external data feeds). It cannot predict future grant revocations or modifications that might occur before the transaction is mined—the check reflects the current state, not the future. It cannot verify that the sender intended to interact with the grant—the tool reads what is on‑chain, not the user's intent. It cannot detect grant vesting schedules in contracts that use non‑standard patterns (e.g., custom grant logic that is not exposed via view functions, or grants that use complex vesting calculations). It cannot guarantee that a claim transaction will succeed even if tokens are claimable, as other conditions (e.g., paused state, balance, allowance) may also need to be met. It cannot detect if the grant has been revoked unless the contract exposes a public revoked() or isRevoked() view function. It cannot detect token transfer restrictions that may prevent claiming (e.g., frozen tokens). It cannot detect grants where the grantor has insufficient balance to fulfill the remaining grant. It also cannot detect if the grant is part of a larger vesting contract with multiple grants, unless the specific grant ID is queried.

PLEASE NOTE

This tool works only for EVM‑compatible chains (Ethereum, Polygon, BSC, Arbitrum, Optimism, Avalanche C‑chain, etc.) and relies on standard grant vesting function signatures (grantId, recipient, token, totalAmount, claimedAmount, releasedAmount, startTime, cliffDuration, vestingDuration, revocable, revoked, lastClaimedAt, nextClaimableAt, claimableAmount). It does not support custom grant 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 grant state, vesting timeline, 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; a grant vesting explanation does not replace your own verification of the transaction details, including the target contract and the function you are calling. This tool is provided free of charge, with no warranty of accuracy or completeness.