Imagine: you hold a portfolio of altcoins, and suddenly the price of one project drops 15% in an hour. The reason is a major token unlock you didn't know about. Such events are predictable, but without automation, they are hard to track in time. We create a system that alerts you about unlocks 3 days in advance, giving you time to adjust your strategy. A timely alert allows traders and investors to hedge positions or exit the token before the sell-off. Our experience in blockchain development exceeds 10 years, and we have deployed similar solutions for 20+ crypto funds.
What Risks Do Unlocks Carry?
Each unlock creates predictable selling pressure. Teams, investors, and advisors receive tokens after the cliff — this is a known event. An automated system detects unlocks on average 3–4 days earlier than manual tracking. This time is crucial for decision-making. Data accuracy guarantee is backed by on-chain verification. A timely alert reduces monitoring costs by approximately $2,000–$4,000 per month for investment teams, saving analyst resources.
How Does the Token Unlock Alert System Work?
The system scans on-chain data from vesting contracts every 5 minutes (Ethereum, Polygon, Arbitrum, BNB Chain). We use standard patterns: Vesting from OpenZeppelin, TokenVesting from Gnosis, as well as custom implementations. For each contract, we compute the releasable amount and the end() date. If an unlock is due within 7 days and the volume exceeds a threshold, an alert is triggered.
Example monitoring code using ethers.js:
// Monitoring VestingWallet events const vestingABI = [ "event ERC20Released(address indexed token, uint256 amount)", "function releasable(address token) view returns (uint256)", "function end() view returns (uint256)" ]; async function checkUpcomingUnlocks(vestingAddresses, tokenAddress, provider) { const alerts = []; const now = Math.floor(Date.now() / 1000); const sevenDaysFromNow = now + 7 * 24 * 3600; for (const addr of vestingAddresses) { const contract = new ethers.Contract(addr, vestingABI, provider); try { const endTime = await contract.end(); const releasable = await contract.releasable(tokenAddress); if (releasable > 0n && Number(endTime) <= sevenDaysFromNow) { alerts.push({ vestingContract: addr, unlockAmount: ethers.formatUnits(releasable, 18), unlockTimestamp: Number(endTime), daysUntilUnlock: (Number(endTime) - now) / 86400 }); } } catch (e) { // Contract doesn't implement the interface — skip } } return alerts; } What Data Sources Does the System Use?
There are three main sources: on-chain data from vesting contracts, off-chain schedules from databases (TokenUnlocks, Vesting.vc, CryptoRank), and analytics from primary documents (whitepaper, tokenomics sheets). Comparison of approaches:
| Source | Reliability | Latency | Parsing Required |
|---|---|---|---|
| On-chain (vesting contracts) | High (directly from blockchain) | Instant on transaction | Requires contract ABI |
| Off-chain (aggregators) | Medium (depends on provider) | Up to 1 day | API integration |
| Whitepaper/Slidedecks | Low (may be outdated) | N/A | Manual analysis |
How Are Alert Thresholds Configured?
Thresholds are set as a percentage of circulating supply, not absolute volume. Recommended values:
| Level | % of circulating supply | Example for a project with 100M tokens |
|---|---|---|
| High sensitivity | 0.5% | 500k tokens |
| Standard | 1% | 1M tokens |
| Significant event | 2% | 2M tokens |
For a project with a small supply (10M), even 0.5% equals 50k tokens, which can be critical. The system automatically adapts recommendations.
What Delivery Channels Do We Support?
An alert includes: project name, unlock amount in tokens and dollars (at current price), recipient category, date, and link to the on-chain source. Comparison of channels:
| Channel | Delivery Speed | Reliability | Cost |
|---|---|---|---|
| Telegram | <1 sec | 99.9% | Free |
| 1–5 min | 99.5% | Free | |
| Discord | <1 sec | 99.8% | Free |
| REST API | Depends on integration | 99.9% | Subscription |
The channel priority is user-configurable.
What Is a Vesting Contract?
A vesting contract is a smart contract that locks tokens for a specific period (cliff) and gradually unlocks them according to a schedule. The OpenZeppelin VestingWallet standard allows flexible parameter configuration. We work with both ready-made implementations and custom contracts, ensuring compatibility with any blockchain.
Development Process
- Requirements analysis and data source selection.
- Architecture design: collectors, parsers, message queue.
- Implementation of monitoring and alert dispatch.
- Testing on test contracts (Tenderly, hardhat fork).
- Deployment and monitoring setup.
What's Included
- API integration documentation.
- Access to a test environment.
- Team training on the dashboard.
- 1 month of post-launch support.
- Guarantee of bug fixes within 30 days.
Timeline and Pricing
An MVP monitoring the top 100 projects with Telegram + Email alerts and a web interface takes 6–8 weeks. A full platform with API, support for custom vesting contracts, and analytics takes 3–4 months. Pricing is individual. We will assess your project for free — contact us.
Order the development of an alert system today. Our engineers are ready to help. Get a consultation for a preliminary assessment.