Token Lock Manager

WHAT IT DOES

Token Lock Manager gives token holders, project teams, and investors full control over time-locked token contracts. It reads live on-chain lock state including locked token balances per address, unlock schedules and timestamps, lock durations, total locked amounts, lock status, and revocation status. You can create new token locks with custom durations, extend existing lock durations to delay withdrawal, withdraw tokens after the lock period expires, and revoke locks where permitted. The tool shows you in real time how many tokens are locked, how much is currently withdrawable, when the lock expires, and whether the lock is still active—so you never have to guess or rely on event logs that only prove past lock creations happened.

HOW TO USE

Connect your EVM wallet. Enter the token lock contract address, token address, and beneficiary (lock owner) address you want to manage. Set the amount to lock (in human-readable units), lock duration in seconds (e.g., 2592000 for 30 days), and optionally a start time as a Unix timestamp or 0 to start immediately. Use "Check lock" to see the beneficiary's lock details including locked amount, withdrawable amount, duration, start time, unlock time, active status, and revocation status. Click "Create lock" to deploy a new lock—this requires the lock contract to have allowance for the tokens. Use "Extend lock" to add additional seconds to the lock duration (delaying withdrawal). Beneficiaries can call "Withdraw unlocked" to claim tokens after the lock period expires. The "Revoke lock" button permanently revokes the lock (if permitted by the contract). 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 getLock() to fetch the full lock struct (amount, duration, start, revoked) and withdrawableAmount() to get the current claimable amount directly from the contract—avoiding the trap of assuming a lock 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 locks, 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 and computes unlock timestamps by adding duration to the start time.

WHAT IT CANNOT SEE

This tool cannot detect off-chain lock intent, verify recipient identity, or guarantee that tokens will remain locked if the contract is upgradable or has administrative override functions. It cannot ensure that the lock contract has sufficient token balance to fulfill all locks. It cannot simulate execution or test whether the lock period has expired before allowing withdrawals. It cannot see pending lock operations that are not yet broadcast to the public mempool, nor can it detect contract-specific lock rules beyond the standard lock interface. The tool manages locks and withdrawals, but it does not guarantee that tokens will remain locked if the contract owner has administrative capabilities to override locks.

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 lock contract address, token address, beneficiary address, amount, and duration 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 lock interface. Revoking locks is irreversible—proceed with extreme caution. The tool is free and open under the BotGentz PLAYBOOK‑C specification.