Liquifi
Liquifi vesting uses linear or custom schedules alongside separate lockups
Liquifi vesting uses linear or custom schedules to represent the dates and percentages in a token grant. Regular intervals suit a linear schedule; specified percentages at particular dates fit a custom schedule. Lockups can postpone access after tokens vest, so compare both calendars before publishing. The platform now operates as Coinbase Token Manager. Coinbase announced the transition on February 2, 2026, with February 28, 2026 as the effective date.
Which vesting schedule matches your grant?
A linear schedule fits regular vesting intervals; a custom schedule fits specified percentages that vest on particular dates. Choose from the executed grant terms, including any independent lockup provisions. For linear vesting, the interval and occurrence date both matter. Monthly events can fall at the start or end of a month, or follow the grant's start day. Custom vesting records percentages against defined dates or periods. An uneven allocation needs its actual percentages preserved, even when some dates repeat regularly.
A cliff has both a duration and a percentage. Matching its date alone won't establish the correct initial vesting amount.
Draft grants and the publication boundary
Draft grants provide a review point before publication finalizes their terms. Keep the grants in draft while checking that either creation route reproduces the agreement's amounts and dates.
Individual entry and CSV import
Create one draft in the app
The in-app route starts with a stakeholder and grant details. Apply a saved template or enter a custom schedule, then create the draft. Its amount, dates, and schedule provide the first comparison against the agreement.
Validate a CSV of grants
CSV imports require stakeholder profiles and saved schedule templates before grant import. Each row supplies the grant quantity, start date, and relevant template ID. If validation finds errors, correct and re-upload the CSV. Once validation succeeds, review the constructed grants before confirming the import. The imported grants typically appear as drafts.
| Parameter | Supported value or form | Expected schedule | Mismatch to catch |
|---|---|---|---|
| Vesting type | Linear or custom | Regular intervals or specified dates and percentages | Equal intervals replacing irregular terms |
| Vesting cliff | Optional duration and percentage | First vesting event matches both inputs | Correct cliff date with an incorrect amount |
| Vesting length | Agreed total duration, including the cliff | Final vesting date matches the agreement | Cliff duration counted twice |
| Vesting frequency | Agreed recurrence after the cliff | Recurring vesting events follow the intended interval | Events recurring at the wrong frequency |
| Vesting occurrence date | Month start, month end, or grant-start day | Events fall on the intended calendar dates | Correct month with the wrong event day |
| Lockup type | Linear or custom | Unlock events follow the separate release terms | Vested tokens treated as unlocked tokens |
Read these settings from the saved template or the draft's custom schedule. Either route matches when the resulting grant reproduces the intended stakeholder, quantity, dates, and rules. A successful CSV upload alone doesn't establish that match. Before publishing a grant in a custody-based or smart contract account, confirm that its recipient has a registered wallet and, for custody-based grants, any required custodian setup is complete. Publishing finalizes the grant and may require a wallet or multisig transaction when the account uses on-chain contracts. Leave the grant unpublished while any required correction remains.
Vested tokens during an active lockup
Vesting and lockups describe separate conditions on the same grant, so a correct vested balance doesn't establish that tokens are ready for delivery. Vested tokens that remain locked aren't claimable. Linear lockups release tokens gradually. Custom lockups use specified dates and percentages and can release an allocation all at once. The relevant lockup duration, cliff, and unlock frequency must match the agreement independently of the vesting settings.
Compare the first vesting event with the first permitted release. Different dates can reflect the agreement's terms.
Schedule records across account types
An account's distribution mode determines whether its schedule records support tracking alone or connect to token payouts and claims.
In a tracking-only account, vesting dates support reporting and reconciliation. The operations team executes transfers outside Token Manager. A published grant can therefore describe the correct schedule without initiating a token transfer.
Custody-based accounts connect grant records to the issuer's configured custody source. Payout readiness also needs integration permissions, any required recipient allowlisting, and sufficient tokens. Registering a recipient's wallet doesn't remove those requirements.
Smart contract accounts use an on-chain escrow. Their onboarding flow requires a published grant before account publication creates that escrow, followed by funding. Token delivery then requires a completed payout or claim through the configured arrangement. A schedule review and a transfer confirmation establish different things.
Why can vested and unlocked tokens remain unavailable?
Vested and unlocked tokens may need an administrator payout if direct claims are disabled. An inactive grant or an underfunded source can also prevent delivery.
An external-wallet claim needs the wallet registered to the grant and the correct distribution network. Email-only login generally provides view access. An issuer-configured, platform-generated wallet can support a different claim route, so email access alone doesn't identify the account's distribution mode.
A direct claim can also require native tokens for gas. Recipients whose custodial wallets can't connect to the application may need an issuer payout or an appropriately configured non-custodial wallet. Grant administrators control releases and funding; Token Manager support can't release an issuer's tokens on its behalf.
Scheduled quantities and net token delivery
Tax withholding can explain a smaller token delivery even when the schedule matches the agreement. For an event with configured withholding, Token Manager applies the rate to the claimable tokens and retains the withheld portion in the source wallet. The intended payout is the net token amount. Some custody APIs may reject the payout if withholding leaves a net amount of zero. Compare quantities for the same event, keeping the claimable amount separate from the deduction. The entire grant balance can include amounts outside that individual payout.
Reusable templates for matching grant terms
Reusable templates suit grants that share their vesting and lockup terms. Templates can contain vesting only, lockup only, or both schedules. They also support custom dates and percentages, so using a template doesn't force a linear structure. Each CSV row needs the template ID that represents its intended rules.
Where a grant has different terms, an administrator can select a separate matching template or configure that individual grant's schedule directly. A custom schedule inside a reusable template suits repeated dated allocations; individual configuration suits terms that don't match an existing template.
What to know about Liquifi vesting
Does the grant date have to equal the vesting start date?
The grant date usually records the document's signature date, while the vesting start date anchors the schedule. Use the executed grant terms to determine each date. Matching dates in a particular grant don't make the fields interchangeable, especially when comparing imported records with the signed agreement.
Are token unlocks always aligned with the grant start date?
Linear lockups can align with the grant start date or follow calendar-based intervals. The lockup settings select that alignment. Custom lockups map release percentages to specified dates or periods. Compare the unlock calendar with the vesting calendar without assuming that their event dates coincide.
Which date format should a vesting CSV use?
A vesting CSV must use the date format specified by the grant import template. MM/DD/YY is an example format, not a universal requirement for every import.
Is a four-year vesting schedule with a one-year cliff mandatory?
The grant agreement determines the schedule; a four-year term with a one-year cliff is one template example. That example vests 25% at 12 months within a 48-month total duration. Other grants can use different durations, cliff percentages, and custom dates that reflect their executed terms.
Does monthly vesting establish a fixed monthly cash payment?
Monthly vesting sets token events, while cash conversion uses a separately quoted exchange rate and any applicable provider fees. Cash withdrawal requires an organization-enabled third-party integration. The provider, bank, and region affect transfer timing after conversion, so a vesting date doesn't establish a bank deposit date.
Can a recipient's custodian hold the full allocation during a lockup?
A recipient's custodian can hold the full allocation under a technical lockup when the recipient requires custody and the issuer isn't using a custodian itself. The recipient's custodian must apply the technical lockup before the issuer transfers the full allocation. Tokens then release under the applied lockup schedule.
Why does Ledger report 'Cannot estimate gas' for an unlocked grant?
A Ledger 'Cannot estimate gas' error typically indicates a grant configuration or source-funding problem. Ask the administrator to confirm that the grant is claimable and that escrow or custody funding covers the claim. This differs from 'Transaction needs gas', which indicates an insufficient native-token balance for transaction fees.
Who approves and executes a Safe claim for vested tokens?
An enabled Safe claim for vested and unlocked tokens needs the owner confirmations required by that Safe's configured threshold, followed by execution. Keep both Token Manager and Safe browser sessions open throughout signing and execution. The executing signer may need gas in their signer wallet, rather than the Safe itself.