Milestone Payment Explainer

WHAT IT DOES

Milestone Payment Explainer takes a milestone payment contract address and provides a complete, plain‑language explanation of its current state. Milestone payment contracts enable work to be delivered and paid for in phases, with each milestone having its own status (pending, completed, approved, paid). This structure is common for project funding, freelancing, grants, and construction. If milestones are delayed, unapproved, or disputed, payments may be held up. This tool reads the contract's state via public view functions—payer, payee, token, totalAmount, milestoneCount, currentMilestone, milestoneStatus, milestoneAmount, milestoneDescription, milestoneDeadline, isCompleted, isApproved, isPaid, canApprove, canRelease, isPaused, arbiter, and fee. It computes the number of milestones completed, approved, and paid, and displays a progress bar showing overall completion. Historical milestone events (MilestoneCreated, MilestoneCompleted, MilestoneApproved, MilestonePaid, MilestoneDisputed, MilestoneCancelled) are fetched using chunked, backoff‑aware log scanning to provide context on past actions. The output includes the payer and payee addresses, token and total amount, a detailed milestone table with individual statuses and descriptions, a progress bar, a contract status badge (Active, Complete, Paused), and a plain‑language explanation of the milestone state and what the next action should be.

HOW TO USE

Paste a milestone payment contract address into the input field, select the network, and click "Explain milestones". The tool connects to your wallet via the EVM bridge (read‑only; it never signs or sends anything) to fetch the milestone state. It attempts multiple common milestone function signatures to maximize compatibility with different implementations. It fetches the current block timestamp for deadline 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 milestone state: who the parties are, the total amount, how many milestones are completed/approved/paid, and what the next action should be. A progress bar shows the overall completion percentage. A table lists each milestone with its status, amount, description, and deadline. You can click on the contract, payer, payee, arbiter, or token addresses to view them on the block explorer.

CHUNKED LOG SCANNING WITH BACKOFF FOR MILESTONE EVENTS

Milestone events (MilestoneCreated, MilestoneCompleted, MilestoneApproved, MilestonePaid, MilestoneDisputed, MilestoneCancelled) are essential for confirming milestone history, approvals, and payments. 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 milestone 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 completions, approvals, and payments that affect the contract's current state.

WHAT IT CANNOT SEE

This tool cannot detect milestone payment risks that depend on off‑chain state (e.g., work completion that is verified off‑chain, or conditions that rely on external data sources). It cannot predict future milestone completions, approvals, or disputes that might occur before the transaction is mined—the risk assessment reflects the current state, not the future. It cannot verify that the sender intended to interact with the milestone—the tool reads what is on‑chain, not the user's intent. It cannot detect risks for milestone payments that use non‑standard patterns (e.g., custom milestone logic not exposed via view functions, or payments that are managed by a multisig with complex validation). It cannot guarantee that a payment or approval transaction will succeed even if the milestone appears complete, as other conditions (e.g., paused state, dispute, or time locks) may also need to be met. It cannot detect if the milestone contract is blacklisted or flagged by external services. It cannot detect if the milestone contract is a proxy pointing to an implementation that may have been upgraded with different logic, which could change the behavior of approvals or payments. It cannot detect off‑chain work quality or completion status—the tool relies on the contract's view functions to report milestone status and does not perform independent verification of work deliverables. It also cannot detect if the payer has sufficient funds to pay all milestones, as that requires checking the contract's balance or the payer's token balance separately.

PLEASE NOTE

This tool works only for EVM‑compatible chains (Ethereum, Polygon, BSC, Arbitrum, Optimism, Avalanche, etc.) and relies on standard milestone function signatures (payer, payee, token, totalAmount, milestoneCount, currentMilestone, milestoneStatus, milestoneAmount, milestoneDescription, milestoneDeadline, isCompleted, isApproved, isPaid, canApprove, canRelease, isPaused, arbiter, fee). It does not support custom milestone 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 milestone state, progress, 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 milestone explanation does not replace your own verification of the transaction details, including the target contract, the milestone ID, and the function you are calling. This tool is provided free of charge, with no warranty of accuracy or completeness.