Linear Unlock Schedule Explainer

WHAT IT DOES

Linear Unlock Schedule Explainer takes a linear token unlock contract address (e.g., a token lockup, vesting schedule, or streaming unlock) and provides a complete, plain‑language breakdown of the unlock’s current state. It reads the contract’s state via public view functions—beneficiary, token, totalAmount, claimedAmount, releasedAmount, startTime, endTime, duration, amountPerSecond, cliffDuration, revocable, revoked, lastClaimedAt, and claimableAmount. It fetches the current block timestamp and computes the elapsed time, remaining time, unlock progress, cliff status, the linear release rate (total ÷ duration), and the amount currently claimable (released - claimed). It also retrieves the token’s symbol and decimals for human‑readable amounts. Historical unlock events (UnlockCreated, UnlockClaimed, UnlockRevoked) are fetched using chunked, backoff‑aware log scanning to provide context on past claims and revocations. The output includes the beneficiary address, token name, total unlock amount, amount already claimed, currently claimable amount, linear rate, start and cliff/end dates, unlock progress, revocation status, and a plain‑language explanation of the unlock’s state and whether a claim transaction will succeed.

HOW TO USE

Paste a linear unlock contract address into the input field, select the network, and click "Explain unlock". 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 unlock function signatures to maximize compatibility with different implementations (e.g., LinearVesting, TokenLockup, and custom unlock contracts). 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 unlock state, including whether a claim transaction would succeed. A visual progress bar shows the unlock progress. You can click on the contract address or any address to view them on the block explorer.

CHUNKED LOG SCANNING WITH BACKOFF FOR UNLOCK EVENTS

Unlock events (UnlockCreated, UnlockClaimed, UnlockRevoked) provide essential context—for example, confirming that an unlock was created, tracking when claims were made, and detecting if the unlock 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 unlock 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 unlock progress and claimable amounts.

WHAT IT CANNOT SEE

This tool cannot detect linear unlock schedules that depend on off‑chain state (e.g., unlocks that are managed by an off‑chain service or based on external data feeds). It cannot predict future unlock 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 unlock schedule—the tool reads what is on‑chain, not the user's intent. It cannot detect linear unlock schedules in contracts that use non‑standard patterns (e.g., custom unlock logic that is not exposed via view functions, or schedules that use complex 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 unlock 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 schedules where the unlocker has insufficient balance to fulfill the remaining schedule. It also cannot detect linear unlocks that are part of a larger contract with multiple beneficiaries, unless the specific unlock 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 linear unlock function signatures (beneficiary, token, totalAmount, claimedAmount, releasedAmount, startTime, endTime, duration, amountPerSecond, cliffDuration, revocable, revoked, lastClaimedAt, claimableAmount). It does not support custom unlock 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 unlock state, release rate, 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 linear unlock 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.