Start here
VesLockr is non-custodial token infrastructure on Robinhood Chain. Creators fund ERC-20 allocations in an onchain escrow. Beneficiaries claim as tokens become available. Anyone can inspect a public schedule without a wallet.
Use Robinhood Chain mainnet, chain ID 4663, with ETH for network gas. Wallet connection is needed to submit transactions, not to read public records.
Choose a release model
Airdrop availability depends on its separately configured deployment. If the interface reports that a product is unavailable, do not send funds directly to an address to try to enable it.
Create & fund
- Connect your wallet. Select Robinhood Chain and keep enough ETH for the platform fee, if any, and network gas.
- Choose a token. Select a discovered wallet token or paste its contract address. Check its name, decimals, balance and escrow admission. A matching ticker or logo alone does not identify a token.
- Set the allocation. Enter the beneficiary and amount. Optionally add a public label. Use the amount shortcuts or enter an exact amount.
- Set the dates. Review both your local time and UTC. Dates must still be valid when the transaction executes.
- Review and approve. The first wallet transaction grants the escrow permission to transfer the allocation. An insufficient existing allowance may need a reset first. Approval alone does not create a lock.
- Create the schedule. The second transaction deposits the full allocation and creates its schedule atomically. Wait for confirmation, then open the public schedule link.
Release rules & boundaries
Token locks
Before the unlock timestamp, vested and claimable amounts are zero. At the unlock timestamp and afterwards, the full deposit is vested. Claimable equals the vested amount minus previous claims.
Vesting created in the single-schedule form
Before the start time, nothing is vested. At start, the TGE portion becomes available, including when the cliff is later. From start through the exact cliff timestamp, only that TGE portion is vested. The remainder starts accruing after the cliff; it does not accrue before the cliff.
Continuous release accrues proportionally from cliff to end. Stepped release counts only completed intervals after the cliff. The offered 30-day and 90-day intervals are fixed durations, not calendar months. At or after end, the full allocation is vested, including rounding remainders. A 100% TGE allocation is fully vested at start.
Batch and airdrop schedules
These use the original linear-with-cliff model: linear accrual begins at start, nothing is claimable before cliff, and accumulated vesting becomes available at cliff. They do not use the single-schedule form’s TGE and post-cliff release model. Check the cliff behavior displayed on the record.
Calculations use blockchain timestamps and integer token units. The preview slider is a projection, not the current onchain claimable balance.
Fees & gas
| Action | Platform fee |
|---|---|
| Token lock | 0 ETH |
| One vesting schedule | 0.001 ETH |
| Batch vesting | 0.001 ETH per schedule |
| One vesting airdrop campaign | 0.001 ETH per campaign, covering its recipients |
| Claim | 0 ETH |
Network gas is separate and applies to transactions, including approvals and claims. The fee is fixed in ETH, not USD. Review the fee read from the deployed contract and your wallet’s gas estimate before signing. A failed transaction may still consume gas.
Track & claim
Open My claims or the public schedule page to inspect deposited, vested, claimed and claimable amounts. Claims are simulated before submission and the page refreshes after confirmation.
For individual schedules, anyone can trigger a claim, but the tokens always transfer to the recorded beneficiary. Triggering a claim does not allow the caller to redirect funds. Wallet gas is paid by whoever submits the transaction.
Zero claimable can mean the unlock or cliff has not been reached, the next step is still pending, or all vested tokens have already been claimed. If an RPC read fails, retry; an error is not proof that a balance is zero.
Token discovery & support
Discovery can include tokens launched through launchpads or independently. Listing and escrow admission are separate: only admitted, reviewed token contracts can be deposited. Fee-on-transfer and rebasing tokens are unsupported. An admission or visible logo is not an audit or endorsement.
If the indexer is unavailable, discovery scans bounded ranges of received ERC-20 transfer events. Older holdings can be missing. Load older ranges or paste the token address. Names, tickers and logos are optional metadata; identity is the chain and contract address.
Security & verification
The contracts determine deposits, vesting and claim rights. An indexer, card or browser display cannot grant a claim or change a beneficiary. Never share your private key or seed phrase with VesLockr or anyone claiming to provide support.
The V1 fund-moving paths have been internally reviewed and tested. No independent security audit has occurred. Explorer source verification is different from a security audit and does not guarantee safety.
Use the transaction and contract explorer links attached to a public schedule to inspect its onchain evidence. Smart-contract bugs, malicious tokens, wallet compromise and network failures can cause loss. For general background, see Ethereum’s smart-contract security guide ↗.
Troubleshooting & local data
Pending or failed transaction
Check the transaction in your wallet and explorer before retrying. A replaced or canceled transaction is not a second successful schedule. The interface shows confirmed receipt links; do not assume a signature alone means funds were deposited.
History is empty
Claim history is paginated by block range. An empty page means no claims were found in that range, not necessarily across the schedule’s full lifetime. Load older ranges when needed.
Drafts and privacy
Form drafts and preferences can be stored in your browser. Drafts are not encrypted or synchronized across devices. Clear them on shared devices. Wallet addresses, labels, schedules and transactions submitted onchain are public; do not put private information in schedule labels.