Airdrop Lockup Extension Tool

WHAT IT DOES

This tool allows the owner or administrator of an airdrop lockup contract to modify key time-based parameters after deployment. You can extend unlock timestamps, adjust vesting durations, modify cliff periods, or pause and unpause the entire lockup contract. The tool reads the current unlock time, vesting duration, cliff duration, paused state, and owner role from the contract, then executes the appropriate update transaction. It supports multiple lockup patterns including token lockups, vesting contracts, and time-locked distributions that implement standard functions like setUnlockTime, extendVesting, setCliff, pause, and unpause.

HOW TO USE

Connect your EVM wallet to the network where the lockup contract is deployed. Enter the lockup contract address. Choose the extension mode: "Extend unlock timestamp" to set a new unlock time, "Extend vesting duration" to increase the vesting period, "Extend cliff period" to modify the cliff duration, or "Pause / unpause lockup" to temporarily halt or resume unlock activity. For unlock, vesting, and cliff modes, enter the new value in seconds (Unix timestamp for unlock, duration in seconds for vesting and cliff). For pause mode, select whether to pause or unpause. The tool will automatically fetch and display the current parameters, paused state, and owner information. Review the preview showing the current and new values, then click Execute Extension. The tool will send the transaction, wait for confirmation, and display the result with gas cost.

TECHNICAL MECHANISM

The tool dynamically probes the lockup contract for multiple common function signatures using ethers.js. For unlock time extension, it uses setUnlockTime(uint256) to update the absolute unlock timestamp. For vesting extension, it uses extendVesting(uint256) to increase the total vesting duration, which shifts the vesting end date forward while preserving the start date. For cliff extension, it uses setCliff(uint256) to modify the cliff duration, which affects the initial waiting period before any tokens become unlockable. For pause control, it uses pause() and unpause() following the OpenZeppelin Pausable pattern, which prevents any unlock or claim operations while paused. The tool performs static calls to owner() to verify that the connected wallet is authorized, displaying a warning if not. It uses the provider's fee data for gas estimation and post-EIP-1559 receipts to report effectiveGasPrice. Current parameters are fetched via view functions before execution and updated after the transaction is mined. The tool handles both timestamp and duration inputs, converting to appropriate units for the contract calls.

WHAT IT CANNOT SEE

This tool cannot verify off-chain reasons for lockup extension, such as regulatory compliance, market conditions, or participant requests—it only acts on the parameters you provide. It cannot prove that an extension is fair to all participants or that extending lockup periods will not disadvantage those who expected earlier unlocks. It cannot adjust tokens that have already been unlocked or claimed—only future unlocks are affected. It cannot guarantee that extending lockup periods will not affect other smart contract integrations that depend on the original schedule. It cannot detect if participants are unable to unlock due to external factors beyond the contract's control, such as wallet issues or network congestion. It cannot predict the impact of extending lockup periods on token price or liquidity. It cannot revert an extension once executed.

PLEASE NOTE

EVM chains only. This tool works with any EVM-compatible network. Only execute extensions if you are the authorized owner or administrator of the lockup contract. Changing lockup schedules can have significant implications for participants—communicate changes clearly to your community. Always test on testnet first with small amounts and verify that the new timestamps or durations are in the future. The tool does not store any data; all state is on-chain. Gas costs vary by network and contract complexity. For contracts with custom parameter functions not covered by the standard signatures, you may need to interact directly via a custom script.