Scribe Doc
  • Overview
  • Get Started
    • ?! FAQ
      • Liquidity & Yield Farming
      • Protocol Earnings
      • What is Impermanent Loss ?
      • Smart Contract Security and Features
  • Protocol
    • AMM
      • AMM V4 Features
        • V4 Add Liquidity (Concentrated)
          • Manual Mode (LP Only
    • Scribe Staked Position NFTs (spNFT)
      • Yield Farming and Rewards
      • Detailed Breakdown of spNFT Functionality
      • Use Cases and Strategies
    • xScribe Plugins
      • Rewards and Yield Boosters
      • Community Plugins
      • Integration and Usage
      • Benefits of Plugins
    • Launchpad
      • Key Features
      • Launch Process
      • Participation Guide
  • SCRIBE Tokenomics
    • SCRIBE Token
    • xSCRIBE Token
      • How to use xSCRIBE
      • Conversion - Redeeming
    • Distribution
    • Protocol Earnings
    • Deflationary Mechanics
  • Reference & Audits
    • Audits
    • Community & Social
  • Contracts
    • AMM V4
      • Factory
      • Non Fungible Position Manager
      • Base Plugin V1 Factory
      • Swap Router
      • Subgraph
Powered by GitBook
On this page
  • Allocations
  • Transfer
  1. SCRIBE Tokenomics
  2. xSCRIBE Token

How to use xSCRIBE

PreviousxSCRIBE TokenNextConversion - Redeeming

Last updated 10 months ago

xSCRIBE is illiquid and non-transferable, but can be used through , and in the future on approved (whitelisted) contracts providing additional usages.

Allocations

Users can freely allocate their available xSCRIBE to any plugin to take advantage of its benefits. While xSCRIBE is allocated and consequently deposited on the token contract, it can't be used for anything else.

Deallocating allocated xSCRIBE will withdraw the amount back into the owner's wallet.

A default 0.5% fee will be applied when deallocating xSCRIBE.

Transfer

xSCRIBE is by default non-transferable, except from/to whitelisted addresses. This is made so that essential interactions (like allocations and redeem with the token contract) and additional usages (for instance with partners specific implementations...) can still be leveraged.

plugins' allocations