Token Vesting Scheduler

WHAT IT DOES

Token Vesting Scheduler gives project teams, token issuers, and beneficiaries full control over token vesting contracts. It reads live on-chain vesting state including total vested amounts, released amounts, releasable amounts, cliff and duration parameters, start timestamps, and revocation status for each beneficiary. You can create new vesting schedules with custom cliff and duration periods, release vested tokens as they become available, and revoke unvested tokens where permitted. The tool shows you in real time how much has been vested, how much has been released, how much is currently releasable, and where the schedule stands relative to cliff and completion—so you never have to guess or rely on event logs that only prove past releases happened.

HOW TO USE

Connect your EVM wallet. Enter the vesting contract address and token address you want to manage. Provide the beneficiary address and the total amount to vest (in human-readable units). Set cliff duration in seconds (e.g., 2592000 for 30 days), vesting duration in seconds (e.g., 15552000 for 180 days), and optionally a start time as a Unix timestamp or 0 to start immediately. Use "Check schedule" to see the beneficiary's vesting details including total amount, released amount, releasable amount, cliff, duration, start time, and revocation status. Click "Create schedule" to deploy a new vesting schedule—this requires the vesting contract to have allowance for the tokens. Beneficiaries can call "Release tokens" to claim vested tokens as they become available after the cliff. The "Revoke unvested" button sends unvested tokens back to the contract owner (if permitted). Each action generates a transaction you review and sign in your wallet.

TECHNICAL APPROACH

This tool queries live contract state using ethers v5.7.2, not historical event logs. It calls getVestingSchedule() to fetch the full schedule struct and releasableAmount() to get the current claimable amount directly from the contract—avoiding the trap of assuming a schedule exists based on events alone. All RPC calls are wrapped in a robust error handler that extracts the actual failure reason from Ethers error objects, digging three levels deep to avoid showing "[object Object]" when a transaction reverts. For transaction costing, it uses receipt.effectiveGasPrice post-EIP-1559 rather than tx.gasPrice, which overstates actual spend. When creating schedules, it checks token balance and allowance before submitting the transaction, providing clear error messages for insufficient funds or approvals. The tool also converts human-readable amounts to the correct decimals based on the token's decimals() call.

WHAT IT CANNOT SEE

This tool cannot detect off-chain vesting intent, verify beneficiary identity, or guarantee that tokens will be available for release at schedule maturity. It cannot ensure that the vesting contract has sufficient token balance to fulfill all schedules. It cannot simulate execution or test whether the cliff has passed before allowing releases. It cannot see pending vesting operations that are not yet broadcast to the public mempool, nor can it detect contract-specific vesting rules beyond the standard schedule interface. The tool manages vesting schedules and releases, but it does not guarantee that tokens will be claimable if the vesting contract is not properly funded.

PLEASE NOTE

This tool supports EVM‑compatible chains only (Ethereum, Goerli, Sepolia, Arbitrum, Optimism, Polygon). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. This is a read‑write tool that requires signing transactions—always verify the vesting contract address, token address, beneficiary address, and all vesting parameters before approving. No contract addresses are hardcoded; you paste the contract you are using, so you are responsible for verifying its safety and ensuring it implements the expected vesting interface. Revoking unvested tokens is irreversible—proceed with caution. The tool is free and open under the BotGentz PLAYBOOK‑C specification.