Run Your Token Operations
Schedules, grants, claim portals and staking — how each one works, and the API behind all of them.
Getting started
Dovim keeps one ledger for every token your project owes: vesting schedules, off-chain grants, airdrop claims and staking pools. Each workspace belongs to a project; each project has one token on Solana.
- Open the app and connect the wallet that administers your treasury. You'll sign a one-time message to prove ownership — it costs nothing and sends no transaction.
- Import your cap table as CSV (
wallet, amount, name, group) or start from a template in Allocations. - Review the unlock curve for each group, then sign the funding transaction from your multisig.
Onchain vesting
A schedule is a start date, a cliff, a total length and a release step (every block, monthly or quarterly). Each schedule is deployed as its own program holding exactly the tokens it owes; nothing is pooled across recipients.
| Template | Cliff | Then | Typical use |
|---|---|---|---|
| Cliff + linear | 12 months, 25% released | Monthly for 36 months | Team, early investors |
| Short cliff + linear | 6 months, 25% released | Monthly for 18 months | Later rounds |
| Step | None | 8 quarterly tranches | Advisors |
| Linear | None | Every block for 24 months | Ecosystem, foundation |
Revocable or fixed. You choose per allocation. Revoking returns the unvested part to the treasury; vested tokens always stay claimable by the recipient. About two-thirds of onchain vesting streams in one large public dataset can be cancelled by the sender — investors increasingly ask which kind they hold, so the recipient's schedule page states it plainly.
Grants & tax
Off-chain grants stay in your own custody until they release. At each release Dovim records the fair value, applies the withholding rate you configured for the recipient's country, and pays the net amount to their wallet. You choose net settlement, cash settlement or full delivery per grant.
Withholding rates are your configuration, not tax advice. Confirm them with your counsel; Dovim keeps the records and the statements your auditors will ask for.
Claim portals
A claim portal is a page on your own domain where recipients check eligibility and claim. You upload a list or a snapshot, then set the rules:
- Sybil clusters — wallets that share a funding source are grouped and can be excluded together. Filters trade false positives for false negatives; review the excluded list before publishing.
- Wallet age — exclude wallets first seen shortly before the snapshot.
- Activity score and a per-wallet cap.
- Vested claims — release part of the allocation at claim and vest the rest.
Claims can be sponsored, so recipients pay no network fee. Unclaimed tokens return to the pool you name when the window closes. See Claim campaigns and the recipient view at Claim page.
Staking
Pools have a lock period, a reward rate funded from an incentives budget, an optional cap and an early-exit penalty. Recipients can move from a claim straight into a pool in one signature, and unvested tokens can sit in a pool without breaking their schedule if you allow it.
API
Every action in the app is available over a REST API. Authenticate with a workspace key in the x-dovim-key header.
curl -X POST $API_URL/v1/allocations \
-H 'Content-Type: application/json' \
-H 'x-dovim-key: dovim_live_key' \
-d '{ "tokenId": "your_token_id", "cursor": "cursor", "limit": 100 }'List endpoints are cursor-paginated (limit up to 500). Writes return an operation ID; the matching program instruction is queued for your multisig to sign.
Webhooks
Subscribe to allocation.created, tranche.released, claim.confirmed, allocation.revoked and campaign.closed. Each delivery is signed with your endpoint secret; retries back off for 24 hours.
{
"type": "claim.confirmed",
"campaignId": "cmp_s1",
"wallet": "<recipient address>",
"amount": "12480.00",
"tx": "<transaction id>",
"confirmedAt": "2026-11-20T14:02:11Z"
}SDK
Put the claim flow inside your own app with @dovim-protocol/sdk.
import { Dovim } from "@dovim-protocol/sdk";
const ops = new Dovim({ apiKey: process.env.DOVIM_KEY });
const check = await ops.claims.eligibility({ campaignId: "cmp_s1", wallet });
if (check.eligible) {
const tx = await ops.claims.build({ campaignId: "cmp_s1", wallet });
// sign and send with the user's Solana wallet
}Security model
- No single-signer admin. Funding, revocation and sweep functions require your multisig; Dovim never holds an admin key.
- Time-locked sweeps. Returning unclaimed tokens waits out a delay recipients can see.
- Funded means locked. Once a schedule is funded its terms can't be edited — only revoked, if it was created revocable.
- Decoded signing. Every request shows signers what the transaction does in plain words before they approve it.
- Open source. Every program is published with its source and verified on Solscan.
Audits reduce risk; they don't remove it. Report a vulnerability through the security contact on the about page.
FAQ
Do schedules depend on Dovim staying online?
No. Schedules live on Solana, not in our database. If the app were unavailable, recipients could still claim from the program directly.
Can I migrate existing vesting contracts?
Yes. We read the existing schedules, mirror them in the ledger, and move tokens only when your multisig signs the migration.
What does it cost?
Self-serve schedules are free apart from network fees. Sponsored claims start at $1.20 per claim and fall to $0.10 above 50,000; grants and withholding are $990 a month for up to 50 grantees. Pay in $DOVIM for 20% off.