Hedgey Community Docs
  • โœŒ๏ธThis is Hedgey.
  • Products
    • ๐Ÿช™Vesting Plans
      • Getting Started
        • โœ…Note for Issuers
        • ๐Ÿ‘ฉโ€๐Ÿ’ผFor Issuers
        • ๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘งโ€๐Ÿ‘ฆFor Token Vesting recipients
        • โœ”๏ธDelegating your tokens
    • ๐Ÿ’ฐToken Grants
      • Getting Started
      • ๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘งโ€๐Ÿ‘ฆFor Grant Recipients
      • ๐Ÿ‘จโ€๐Ÿ’ผFor Grant Issuers
    • ๐Ÿ›๏ธInvestor Lockups
      • Getting Started
        • โœ…Note for Issuers
        • ๐Ÿคตโ€โ™€๏ธFor Issuers
        • ๐Ÿ‘ฏFor Investors who have received locked token allocations via Hedgey
      • Special Features
        • Segmenting Plans
        • โœ”๏ธDelegating your tokens
      • Creating Investor Lockups using Fireblocks (+troubleshooting)
    • ๐Ÿ”Treasury Lockups
      • Getting Started
      • Creating Treasury Lockups
    • ๐Ÿช‚Token Claims
      • ๐Ÿ‡Getting started
        • Using token claims on Farcaster
        • ๐ŸŽFor Claims Issuers
        • ๐Ÿ•ต๏ธโ€โ™‚๏ธCreating a test claim to verify wallet addresses
        • ๐ŸŽ‰For Claims Recipients (unlocked & locked claims)
    • ๐Ÿ•—Time Locks
      • ๐Ÿ‡Getting started
        • โฐCreating Time Locks
  • ๐ŸงฐSupport docs
    • ๐Ÿ”ตGrants (Arbitrum STIP)
      • Getting Started
      • For STIP Grant Recipients
      • For Arbitrum Grant Issuers
    • ๐Ÿ”ตGrants (Arbitrum LTIPP)
      • Getting Started
      • For LTIPP Grant Recipients
      • For Arbitrum Grant Issuers
    • ๐ŸŸฃGrants (Polygon Village)
      • Getting Started
      • For Grant Recipients
      • For Polygon Village Grant Issuers
    • ๐Ÿ”ตLocking your team tokens and LP tokens on Hedgey using Hedgey Treasury Locks (for ShimmerSea)
      • Getting Started
      • Creating a Treasury Lockup
    • ๐ŸŸ (Celo Specific) Connecting with Celo Terminal
    • โœ…(Celo Specific) using Hedgey through Valora
    • ๐ŸคฉGovernance
      • โšกHedgey <> Snapshot strategy
    • ๐Ÿ‘ฝOn-Chain Governance
    • ๐Ÿ”บUsing Hedgey app with Fireblocks
    • โš’๏ธTroubleshooting
    • ๐Ÿ’ปAdding Hedgey Apps as "custom" Safe apps
    • ๐ŸชฑFor Wormhole investors who have received lockups on Hedgey
    • โค๏ธโ€๐Ÿ”ฅCreating Investor Lockups using FireBlocks (+troubleshooting)
    • ๐ŸกViewing your Puffer lockup
  • FOR DEVELOPERS
    • โŒšTechnical Documentation
      • ๐Ÿ’พToken Vesting
        • Smart Contract Details
        • Integration & Direct Contract Interactions
      • ๐Ÿ“ผToken Lockups
        • Smart Contract Details
        • Integration & Direct Contract Interactions
      • โ˜Ž๏ธDelegation Architecture
        • Delegator Architecture
        • Voting Vaults & On-Chain Delegation
        • ERC721Delegate
      • ๐ŸฅณToken Claims
        • Smart Contract Information
      • ๐Ÿ“€V1 Contracts
        • Hedgeys NFT
          • Technical Details
        • DAO <> DAO Swap
        • Error Codes
    • ๐ŸAudits
    • ๐Ÿ“ŽBug Bounty
    • Deployments
      • Token Vesting Plans
      • Voting Token Vesting Plans
      • Vesting + Lockup Plans
      • Token Lockup Plans
      • Voting Token Lockup Plans
      • Bound Token Lockup Plans
      • Bound Voting Token Lockup Plans
      • Batch Planner Contract
      • Token Claims (ClaimCampaigns)
      • V1 Streaming Contracts
      • V1 Stream Vesting Contracts
      • Hedgeys
  • Contact HEDGEY
    • Social Media
    • Press and Media kit
  • LEGAL
    • Protocol Disclaimer
    • Terms of Use
    • Hedgey Pro Terms of Use
Powered by GitBook
On this page
  1. FOR DEVELOPERS
  2. Technical Documentation

Token Lockups

This section covers smart contracts related to Investor Lockups and Treasury Lockups

Overview:

The Token Lockups Contracts allow on-chain teams to distribute tokens to their investors, advisors, and community with a time based unlock schedule, where tokens cannot be revoked or cancelled, but unlock over a preset immutable schedule. This tool is designed for distributing tokens to beneficiaries who are guaranteed the rights to the tokens, but with a predefined time based unlock schedule. The tool allows for the lockups to be transferable or not transferable, which is required to be defined when creating the token lockups initially. Transferable lockups allow beneficiaries to transfer the lockups to a custodian, cold storage, and potentially used in DeFi protocols such as lending / swapping, opening up a larger ecosystem and use case for the token lockups.

The contract has two primary users, the creator and the beneficiary. Once the creator has created the token lockup plan and issued it to the beneficiary, they are no longer involved and have no administration rights over the lockup plan. All of the lockup details are set and immutable at creation. The contract controls the rate at which tokens unlock to the beneficiary, but also allows the beneficiary to participate in governance via delegation, transfer the lockup plans, and even split a single lockup plan into multiple chunks - or recombine previously split chunks back into a single lockup plan. At its core the lockup plan contract acts as an escrow contract, holding the tokens that unlock and are available to be claimed by the beneficiary based on the unlocking rates set at inception. The escrow contract is built on top of the ERC721 standard, with additional features, whereby the beneficiary has an NFT issued to their wallet address that is the owner of the lockup plan. There are 4 versions of the lockup plans, 1. Transferable with on-chain governance enabled contract 2. Transferable without on-chain governance enabled (but optimized for snaphshot voting) 3. Non-transferable with on-chain governance enabled 4. Non-transferable without on-chain governance enabled Each contract type has a different use case, performing the job that is required for its users. For instance tokens with on-chain voting that are locked for investors would likely use the version 1, so that investors can transfer them to custodians or cold storage, or even sell on secondary markets and participate in governance. Whereas a DAO locking up their treasury tokens to transparently evidence the emissions schedule to the community would likely use version 4 - where the lockup is not transferable and cannot participate in governance.

Because the lockup plans are built without oracles and an NFT primative, additional use cases can be built on top, such as intermediate ownership of a splitter contract for pooled investments, or an intermediate DAO contract that anyone can execute a claim of the tokens to.

PreviousIntegration & Direct Contract InteractionsNextSmart Contract Details

Last updated 1 year ago

โŒš
๐Ÿ“ผ