Vesting Cliff Risk Explainer

WHAT IT DOES

Vesting Cliff Risk Explainer takes a vesting contract address and provides a focused risk assessment of the cliff period—the critical time before which tokens cannot be claimed and may be forfeited if the schedule is revoked. Many token vesting contracts include a cliff (e.g., 6 months) during which no tokens are released; if the schedule is revoked before the cliff ends, the beneficiary loses all unvested tokens. This tool reads the contract's state via public view functions—startTime, cliffDuration, totalAmount, claimedAmount, vestedAmount, releasableAmount, revoked, beneficiary, and token. It fetches the current block timestamp and computes the cliff end timestamp (startTime + cliffDuration), whether the cliff has passed, how much time remains (or has elapsed), and the amount at risk (total unvested tokens that would be forfeited upon revocation). It assigns a risk level: High if far from the cliff, Medium if approaching, Low if the cliff has passed, or Revoked if the schedule has already been revoked. Historical vesting events (TokensReleased, VestingCreated, VestingRevoked) are fetched using chunked, backoff‑aware log scanning to provide context on claims and revocations. The output includes a visual progress bar, a risk level badge, and a plain‑language explanation of the risk.

HOW TO USE

Paste a vesting contract address into the input field, select the network, and click "Assess cliff risk". 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 vesting function signatures to maximize compatibility with different implementations. It computes the cliff end timestamp, time remaining, amount at risk, and assigns a risk level based on the proximity to the cliff and revocation status. 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 risk assessment: whether the cliff has passed, the amount at risk, the risk level, and what the beneficiary should consider before taking action. A progress bar visualizes the vesting progress. You can click on the contract address or beneficiary address to view them on the block explorer.

CHUNKED LOG SCANNING WITH BACKOFF FOR VESTING EVENTS

Historical vesting events are critical for assessing risk—for example, confirming whether tokens have already been claimed or if the schedule 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 vesting 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 time‑to‑cliff and risk levels.

WHAT IT CANNOT SEE

This tool cannot detect vesting risks that depend on off‑chain state (e.g., off‑chain agreements that override the vesting schedule, or external factors that could trigger an early revocation). It cannot predict future revocation events or governance actions that might occur before the transaction is mined—the risk assessment reflects the current state, not the future. It cannot verify that the sender or beneficiary intends to take any specific action regarding the vesting schedule—the tool reads what is on‑chain, not the user's intent. It cannot detect vesting risks in contracts that use non‑standard patterns (e.g., vesting logic that is not exposed via view functions, or custom revocation logic that is not easily queryable). It cannot guarantee that a token transfer or claim will succeed even if the cliff has passed, as other conditions (e.g., paused state, balance, allowance) may also need to be met. It cannot detect if the vesting schedule has been revoked unless the contract exposes a public revoked() view function. It cannot detect token transfer restrictions that may prevent claiming (e.g., frozen tokens). It cannot detect if the beneficiary has already transferred or sold their vested tokens, which could indicate reduced risk exposure. It also cannot detect vesting schedules that are implemented as part of a larger token distribution contract without dedicated view functions.

PLEASE NOTE

This tool works only for EVM‑compatible chains (Ethereum, Polygon, BSC, Arbitrum, Optimism, Avalanche C‑chain, etc.) and relies on standard vesting function signatures (startTime, cliffDuration, totalAmount, claimedAmount, vestedAmount, releasableAmount, revoked, beneficiary, token). It does not support custom vesting 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 cliff state, risk level, event history, and contract data 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 risk assessment 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.