LogoLogo
  • Blend v2 Documentation
  • ๐Ÿ“„Blend Whitepaper
  • ๐ŸงชMedia Kit
  • ๐Ÿš€Deployments
  • ๐Ÿ•ต๏ธโ€โ™‚๏ธAudits & Bug Bounties
  • ๐Ÿง‘โ€๐ŸญGithub
  • v1 Docs
  • ๐Ÿ‘ฅUsers
    • General/FAQ
    • Choosing Pools
    • Lending-Borrowing
      • Lending
      • Borrowing
      • Liquidations
    • Backstopping
    • BLND Token
    • Auctions
  • Emissions
  • ๐ŸŒŠPool Creators
    • General
    • Tutorial: Setting Up a Pool
    • Adding Assets
      • Risk Parameters
      • Interest Rates
      • Emissions
    • Pool Management
    • Selecting an Oracle
    • Setting Backstop Take Rate
    • Setting Max Positions
    • Backstop Bootstrapping
    • Required Infrastructure
  • ๐Ÿ“šTech Docs
    • General
    • Core Contracts
      • Emitter
        • Backstop Management
        • Blend Distribution
      • Backstop
        • Deposit Management
        • Drawing and Donating
        • Emission Distribution
      • Pool Factory
        • Lending Pool Deployment
      • Lending Pool
        • Fund Management
        • Liquidation Management
        • Emission Management
        • Interest Management
        • Pool Management
        • Bad Debt Management
        • Protocol Tokens
    • Guides
      • Deploying a Pool
    • Integrations
      • Integrate with a Blend Pool
      • Fee Vault
    • Potential Improvements
Powered by GitBook
On this page
  • Normal Emissions
  • Drop Emissions
Export as PDF
  1. Tech Docs
  2. Core Contracts
  3. Emitter

Blend Distribution

The Emitter contract is the admin of the Blend token and is responsible for minting and emitting Blend to the current backstop.

Normal Emissions

Regular emissions are carried out via the distribute() emitter function. This function mints an amount of Blend equal to the number of seconds that have passed since the last distribution time and sends it to the backstop contract. The Backstop contract handles further distribution logic.

Drop Emissions

Blend emissions are also carried out via "Drops". Drops are fixed 50 million token emissions that can be executed after every backstop swap. Drops are carried out by the Emitter contract'sdrop() function which uses a drop_recipient list stored in the Backstop contract to determine what addressed Blend should be minted to.

Each Backstop contract address can only call drop() once. If the backstop contract address is swapped then swapped back the original backstop still will not be able to call drop again.

The listed Backstop contract must call drop()` so Backstop contracts must always have a method of doing so

Drops are intended to incentivize further open-source development of the protocol - as a backstop swap represents the release of a new protocol version.

PreviousBackstop ManagementNextBackstop

Last updated 2 months ago

๐Ÿ“š