Lucid
  • USING LUCID
    • Welcome to Lucid
    • Homepage
    • Explore Page
    • Organisation Summary Page
    • Sidebar Navigation
  • Organisation Creation Page
  • Creating an Organisation
    • 1. Setup Organisation Details
    • 2. Module Selection
    • 3. Module Configuration
    • 4. Safe and Protocol Upgrades Configuration
    • 5. Governor Configuration
    • 6. Veto and Multi-Bridge Configuration
    • 7. Token Configuration
    • 8. Asset Transfer Portals Configuration
    • 9. Review and Deploy Organisation
    • 10. Lucid Post-Deployment Integration
  • Editing an Organisation
  • Modules and integrations
    • Multi-Bridge
      • Multi-Bridge Asset Transfers
      • Multi-Bridge Message and Asset Transfers
      • Resend Transaction
    • Bridge Portals
    • Vested Emission Offerings (VEOs)
      • VEO Purchase Flow
      • VEO Creation Flow
      • VEO Removal Flow
      • Claiming Vested Tokens
    • Wizard | Protocol Upgrades
  • Developer Reference
    • VEOs
      • Vesting Options
      • Price Models
      • Debt Buffer
      • Deposit Interval
    • Message Bridging
      • Sending a Message
      • Message Execution
      • Admin Functions
    • Asset Bridging
      • Bridging Assets
      • Admin Functions
    • Adapters
      • Axelar Adapter
      • CCIP Adapter
      • Connext Adapter
      • Hyperlane Adapter
      • LayerZero Adapter
      • Polymer Adapter
      • Wormhole Adapter
    • Deployed Contracts
      • Multibridge Contracts
      • VEO Contracts
  • API Reference
  • RESOURCES
    • About
    • Fees
      • Lucid Pricing and Fee Structure
      • Fee Estimates for Bridges
    • Frequently Asked Questions
    • Key Terms and Explanations
    • Contact
Powered by GitBook
On this page
  1. Developer Reference
  2. VEOs

Vesting Options

When configuring a VEO, you’ll be asked to choose a Vesting Type. There are four options:

Fixed Expiry

  • The tokens purchased will unlock on a specific date & time.

  • All users receive their vested tokens on the same end date, regardless of when they purchased.

  • Ideal when the protocol wants to align all token unlocks to a specific timeline for strategic or liquidity reasons.

Fixed Term

  • The vesting period begins individually for each buyer at the moment of their purchase.

  • The unlock date varies per user based on when they bought the VEO.

  • Best when the goal is to create rolling vesting timelines.

Linear Fixed Expiry

In this model, tokens vest continuously (every second) starting from the time of purchase by the user and continue until a fixed expiry date set by the project. All users who receive tokens under this schedule follow the same timeline, regardless of when their individual allocation is made.

  • The expiry date is universal for all participants.

  • If a user joins later, they still vest only until the fixed expiry date, resulting in a shorter vesting window. Even though the vesting period is shorter, more tokens vest during this period compared to someone who bought the same amount of VEOs at an earlier date.

  • Vesting speed adjusts based on when the user joins, to ensure full vesting by the expiry date.

This model is ideal for scenarios where the project wants to align all recipients to a shared end date.

Linear Fixed Term

In this model, tokens vest continuously (every second) over a fixed duration (term) that starts when each individual user purchases. A vesting schedule is created when the user purchases the bond.

  • Each user has a personalized vesting timeline starting from their allocation date.

  • The vesting period lasts the same amount of time for everyone (e.g., 6 months), regardless of when they join.

  • Useful when recipients are onboarded at different times, ensuring each gets a consistent vesting experience.

PreviousVEOsNextPrice Models

Last updated 6 days ago