Questions, answered.

Vestream is a cross-protocol, cross-chain tracker for on-chain token vesting. It indexes every public vesting schedule from twelve major platforms – Sablier, Hedgey, Superfluid, LlamaPay, UNCX, Unvest, Team Finance, PinkSale, HoodLock, Magna, Streamflow, and Jupiter Lock – across Ethereum, Base, BNB Chain, Polygon, Arbitrum, Optimism, Avalanche, Robinhood Chain, and Solana, and gives you one dashboard to see every unlock coming to any wallet, plus email and push alerts before each one.

Three audiences: (1) token holders who need to know when their vested allocations unlock so they can claim, decide whether to sell, or plan tax events; (2) funds and team treasuries tracking investor allocations, cliffs, and unlock schedules across multiple positions; (3) developers and AI agent builders who want programmatic access to normalised vesting data via our REST API or MCP server.

Download the free Vestream app (iOS or Android), then add any wallet – an EVM 0x… address or a Solana pubkey – and Vestream automatically scans it across all 12+ protocols and 9+ chains. The Free plan tracks 3 wallets; Pro tracks 10. Prefer your browser? Paste a wallet at /find-vestings for an instant scan, no install.

No. Vestream is strictly a read-only, address-watching tracker – you enter addresses as text, not by connecting a wallet. There is no wallet-signing step, no transaction approval, no access to your keys. You sign into the app with an email one-time code; the web dashboard unlocks by scanning a QR from the app (Pro).

No. When you add a wallet address, Vestream auto-scans all 11+ supported protocols across all 9+ chains (EVM + Solana) and surfaces every vesting stream found – you don't need to know in advance which platform your tokens are on.

Twelve as of today: Sablier (linear and tranched streaming), Hedgey (NFT-based vesting plans), Superfluid (cliff + linear streaming via its VestingScheduler), LlamaPay (per-second token streaming for vesting and payroll), UNCX Network (TokenVesting and VestingManager locker contracts), Unvest (step/milestone vesting), Team Finance (team token vesting + on-chain lock proof, via its Squid subgraph), PinkSale PinkLock (TGE + cycle schedules), Streamflow (Solana's #1 vesting protocol), and Jupiter Lock (time-released token vesting on Solana). Each EVM protocol has its own adapter that normalises into a shared VestingStream shape; LlamaPay's TVL is sourced from DefiLlama's vesting-specific slice while we build out per-wallet stream tracking.

Eight production EVM chains plus Solana: Ethereum mainnet (chainId 1), BNB Chain (56), Polygon (137), Base (8453), Arbitrum One (42161), OP Mainnet (10), Avalanche C-Chain (43114), Robinhood Chain (4663), and Solana mainnet-beta (101). Ethereum Sepolia (11155111) and Base Sepolia (84532) are also supported for testing and contract deployments that haven't yet shipped on mainnet.

For five EVM protocols (Sablier, Hedgey, UNCX, UNCX-VestingManager, Unvest) we query each protocol's official subgraph on The Graph Network – same data source the protocol's own frontend uses. Superfluid is queried via its hosted subgraph. PinkSale has no subgraph, so we read the PinkLock V2 contract directly via viem RPC calls. Streamflow + Jupiter Lock are read directly from Solana via the protocols' SDKs and getProgramAccounts. LlamaPay's TVL is sourced from DefiLlama's vesting-specific slice. All data is public, on-chain, and matches what you'd see on the protocol's native UI.

The dashboard queries subgraphs in real-time when you load a wallet, so for scheduled-data fields (start time, end time, cliffs, unlock amounts) you're looking at live on-chain state. Aggregate stats (TVL, streams-tracked counts) are cached in our own database and refreshed nightly to amortise subgraph costs. Token prices come live from DexScreener on every page load, using the highest-volume trading pair.

Yes. The roadmap prioritises protocols with public subgraphs or well-documented contract interfaces. Vote for what you want by emailing us via the contact page – volume of requests genuinely drives prioritisation.

Yes – use the contact form and tell us the protocol name, contract addresses, and (if known) the subgraph ID or where the schedule data lives on-chain. If it has a subgraph we can usually prototype an adapter in a day.

Turn on alerts in Settings and pick your preferences – email, push, or both, and a lead time (1 hour to 3 days before each unlock). A background cron job scans every tracked wallet against the next 30 days of unlocks, compares against a dedup log, and fires a notification at the chosen lead time. You get one alert per unlock event; we never spam.

Any scheduled time at which a vesting stream moves tokens from locked to claimable – linear stream end, tranche boundary in a stepped vest, cliff release, or scheduled cycle unlock on PinkSale. A continuously streaming Superfluid vest is treated as "fully unlocked at end time" for alert purposes.

No. Notifications only fire for unlock events strictly in the future as of the scan time. If you add a wallet that has an unlock tomorrow, you'll get the alert. If it had an unlock yesterday, you won't be notified – that event is already in the past.

Three lifetime push alerts on Free. Email alerts have no such cap on any tier – free accounts get unlimited email alerts from day one. Pro and Enterprise have unlimited push alerts.

Yes. You can add any Ethereum address – a team treasury, a founder's wallet, an advisor allocation – and receive alerts on it. The data is all public on-chain anyway. You authenticate with your own email; the addresses you track are just configuration.

An optional layer on top of your vesting positions where you log your purchase price (entry) and any individual sales (date, token amount, sell price or total USD received). Vestream automatically splits your P&L into realised (already sold) and unrealised (remaining vested tokens at current market price). All P&L data is stored locally in your browser – it's never transmitted to Vestream or any third party.

A searchable, filterable view of every token we've ever indexed a vesting schedule for, with upcoming unlocks, total TVL locked per token, and per-protocol distribution. Great for finding tokens with heavy upcoming unlocks that might affect price, or for researching how competing projects structure their vesting. Pro and Enterprise only.

Yes. The Export button on the dashboard generates a CSV of every tracked stream including protocol, chain, token, amounts (total, vested, withdrawn, locked), cliff/start/end times, and your logged sell transactions. For printed reports, use your browser's print-to-PDF – the dashboard has print-specific CSS so you get a clean, human-readable document.

Prices come from DexScreener, using the highest-volume DEX pair with liquidity over $1,000. Market cap and FDV match what DexScreener itself displays on the token page. For tokens with no DEX listing at all (testnet tokens, brand-new deployments), prices are marked unavailable and the UI falls back to raw token amounts rather than showing a fake dollar value.

Yes – where the source subgraph exposes withdrawal events (most do), the Vestream stream detail view lists every historical claim with timestamp and amount. PinkSale is the exception: since there's no subgraph, we can only show the scheduled unlock plan, not historical withdrawals.

Free: $0, 3 wallets, 10 push alerts per month (resets on the 1st), no email alerts. Pro: $9.99/month or $74.99/year (saves 37%) for 10 wallets, unlimited push + email alerts, the web dashboard, the Discover page, and tax exports (Koinly / CoinTracker / TurboTax + year-end PDF + income statement). Tracking more than 10 wallets? Email [email protected].

A wallet is a distinct address you want scanned – EVM (0x…) or Solana (base58). If the same address has vestings on Sablier, Hedgey, UNCX and Streamflow, that still counts as one wallet – we auto-scan all 12+ protocols and all 9+ chains regardless of tier. The limit only bites when you want to track multiple different addresses (e.g. personal + team + investor wallets).

Yes. Web subscriptions cancel instantly from account settings and remain active until the end of the current billing period. In-app subscriptions cancel through the Apple/Google subscription management in your device settings. We don't do lock-in contracts, surprise renewals, or retention dark patterns.

No – never. Vestream is strictly read-only. We never request your private key or seed phrase, we don't ask you to connect a wallet, and we have no capability to initiate a transaction. Adding a wallet to your dashboard is typing its public address into a text field; the address is publicly visible on-chain anyway.

Only: the email you signed up with, the wallet addresses you choose to track, your notification preferences, and (if you're a paid subscriber) your RevenueCat customer ID for billing. We don't store KYC data, phone numbers, names, or any fields we don't have a concrete product reason to hold.

In a Postgres database hosted on Supabase (EU region by default). API secrets live in Vercel environment variables. Email delivery goes through Resend. Push delivery goes through Expo (for the mobile app) and Web Push (for PWAs). Payment data never touches our servers – Apple, Google, and RevenueCat handle card details directly.

Not currently. The MCP server (@vestream/mcp) is published to npm and its source is available there. The main web app is closed-source during early access, but we're committed to publishing the core vesting adapters as a standalone open-source library once the interfaces stabilise.

We use a single first-party session cookie for authentication (iron-session, HttpOnly, same-site) and nothing for third-party tracking. No Google Analytics, no Facebook Pixel, no retargeting trackers. The cookie banner you may see is a safety net for GDPR compliance – you can decline all optional cookies with no impact on functionality.

Yes – a public REST API at /api/v1/ with three primary endpoints: GET /api/v1/wallet/{address}/vestings returns every stream for a wallet; GET /api/v1/wallet/{address}/upcoming-unlocks returns scheduled unlocks within a configurable window; GET /api/v1/stream/{id} returns full detail for a single stream by composite ID. See /api-docs for the Swagger UI and live request builder.

Request access via the developer portal (/developer) or the contact form. API keys have the format vstr_live_{32 hex chars}, are shown once at creation time, and are stored as SHA-256 hashes – we can never recover a lost key, so copy it into your secret manager immediately. Use the Authorization: Bearer vstr_live_... header on every request.

@vestream/mcp is a Model Context Protocol server published to npm. It exposes three tools to AI agents – get_wallet_vestings, get_upcoming_unlocks, and get_stream – so Claude Desktop, Cursor, or any MCP-compatible client can query Vestream data natively without you writing glue code. See the AI Agents page at /ai for a quick-start config.

Free-tier API keys: 30 requests per minute burst, 150 per day. Pro: 5,000 per day. Enterprise: negotiated per contract, typically uncapped. All limits are enforced via Upstash Redis and return a standard 429 response with Retry-After header when exceeded. Rate-limit headers (X-RateLimit-Remaining, X-RateLimit-Reset) are on every response.

Not yet – the current API is pull-based. Webhook support (fire-on-unlock delivery) is on the Enterprise roadmap. If that's blocking your use case, tell us via the contact form and we'll prioritise it.

An iOS and Android app is in beta as of April 2026. It's a React Native / Expo companion to the web dashboard – same account, same wallets, same notification preferences, plus native push notifications (instead of web push) for reliable delivery when the app is backgrounded.

Native OS-level push notifications with richer previews, Face ID / Touch ID biometric re-lock when you background the app, and (roadmap) a lock-screen widget showing your next upcoming unlock. The mobile app is read-only and navigates to the same dashboard as web for settings and wallet management.

Same email OTP as web – enter your email, receive a 6-digit code, enter it. The mobile app uses an Authorization: Bearer token in the HTTP header (not a cookie) so sessions persist across app restarts without you having to re-verify.

Through your device's native subscription management – iOS Settings → Apple ID → Subscriptions, or Google Play → Subscriptions. This is required by Apple and Google for in-app purchases. Web subscriptions are managed in your Vestream account settings.

Email is your account identifier and changing it requires confirming ownership of both the old and new addresses. Contact support via the form and we'll walk you through it – takes a couple of minutes.

Contact support via the form and request deletion. All your data – wallets, notification preferences, any stored P&L data (if any) – is permanently removed from our database within 7 days. Subscriptions are cancelled as part of the same request.

Subscriptions go through Apple App Store (iOS) or Google Play (Android) at this stage – pay with whatever payment method you have on file with the platform store, including Apple Pay and Google Pay. No crypto payments currently – adding USDC checkout is on the roadmap but not committed.

Yes, within 14 days of the initial subscription purchase if you haven't used the paid features substantively. Contact support and we'll process it – no questions, no hoops. In-app purchase refunds go through Apple or Google per their policies.

Three common causes, in order of likelihood: (1) the wallet genuinely has no vesting streams on any of the 11+ supported protocols on any of the 9+ chains; (2) the streams exist on a protocol or chain we don't yet support; (3) the data source (subgraph or Solana RPC) is temporarily rate-limited or unreachable. Refresh in 60 seconds, and if you still see nothing, check the address on the protocol's own frontend to confirm streams exist.

First, check your spam folder – new sender domains often land there until you mark them safe. Second, confirm the email in Settings is correct and that the "Email alerts" toggle is on. Third, note that alerts only fire for unlocks in the future and at the lead time you configured; if the next unlock is 10 days out and you set "1 hour before", you won't hear anything for 9 days and 23 hours.

That state appears when the TVL bar is loading token prices from DexScreener, or when the price cache is briefly stale during a cold deploy. It clears within 10-30 seconds. If it persists more than a minute, refresh – our CDN layer may be holding a stale version from before the last deploy.

Contact support via the form and we'll help verify your identity (via wallet signature or other means) and recover account access. For obvious reasons we can't just send account details to whoever claims to be you in a chat – but we can always help legitimate account owners regain access.