LogoLogo
HomeLaunch app
  • About Ekubo
    • 👋Introduction
    • 🔑Features
  • User Guides
    • 🌊Add liquidity
    • 🔄Swap
    • ⌛Dollar-cost average orders
    • 🏩Governance
      • EKUBO token
    • Incentives
      • 🌻Starknet DeFi Spring
  • Integration Guides
    • 🔌Extensions
      • Oracle
    • 🔄Swapping
    • 💸"Till" pattern
    • 📚Reference
      • Core Interfaces
      • Contract addresses
      • Reading pool price
      • Error Codes
      • Ekubo API
      • Audits
      • Key concepts
      • Math 1-pager
      • Frequently Asked Questions (FAQ)
  • Links
    • Home
    • Launch app
    • Discord
    • Twitter
    • Telegram
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. User Guides
  2. Governance

EKUBO token

Information about the EKUBO token

PreviousGovernanceNextIncentives

Last updated 1 month ago

Was this helpful?

The EKUBO token is an bridged to , developed for the purpose of decentralizing ownership of Ekubo Protocol.

Initial distribution

The total supply of the EKUBO token is 10 million (10,000,000). The total supply was split into 3 equal parts of 3,333,333 tokens. The 3 categories of distribution for the EKUBO token generation event were:

  • Airdrop: 1/3rd of the total supply was distributed to users via airdrop

  • Team: 1/3rd of the total supply is held by the company Ekubo, Inc.

  • Sale: 1/3rd of the total supply was sold by the DAO for ETH, USDC and STRK via Ekubo's DCA order feature

Airdrop

Each user's allocation of EKUBO was calculated based on their share of total points on the leaderboard, with a few adjustments: we exponentiated each user's points (i.e. p^x) based on their role in the ecosystem, and accounts that earned less than 1,000 points were excluded. As a result, users who used fewer accounts received slightly more EKUBO tokens from the airdrop.

  • Moderators had a boost of 1.01

  • Active translators received a boost of 1.001

  • Everyone else received a boost of 1.0001

The airdrop contract is deployed at the address 0x04bfacd0fcf70f444815de9150008fd12b5fb6721562707e502ce71ccb327d88 (, ). It uses the open source airdrop contract found . There is no deadline to claim the airdrop.

An airdrop can be claimed by using a block explorer to submit a transaction using data found in this spreadsheet:

Claiming your airdrop

We have removed the ability to claim from the interface. Below is a guide to claiming the airdrop using the Voyager block explorer:

1

Download the airdrop data CSV file

This CSV contains a list of all the accounts and allocation amounts that were included in the airdrop. Each row corrresponds to a single address's claim in the airdrop.

2

Find your address in the CSV file

Extract the .csv from the .zip file , and then open the file in any text editor like Notepad or Sublime. Search for the line containing your address in the file. If you cannot find it, make sure to remove any leading zeroes from your address. E.g. if your address is 0x0000abcd, search for 0xabcd. If you still cannot find your address, you did not receive an airdrop.

Do not use Excel or Numbers to open the spreadsheet. They will round the numbers in the columns causing you to get "Invalid proof" when you try to submit your transaction.

3

Copy the row into Voyager block explorer

4

Click transact to claim!

When you click transact, the transaction should simulate successfully, and if you are transacting from the claimee address you should see an EKUBO balance increase from the simulation.

Sale

Approximately 3,269,920 EKUBO was sold for 343.675 ETH, 1,204,770 USDC, and 1,549,920 STRK.

Team

Governance contracts

Disclaimer

The EKUBO token serves only to decentralize the ownership role of the on-chain instance of the core Ekubo Protocol.

Ekubo, Inc., is not in any way obligated to provide service, maintenance, or development for Ekubo Protocol and related tools or services except as explicitly agreed via governance proposal.

The governance infrastructure is necessary security infrastructure: it protects users of Ekubo Protocol from malicious upgrades by requiring a decentralized and interested majority of stakeholders to come to consensus on the validity and safety of the changes.

The columns in the CSV are claimee, id, amount and proof from left to right. For the row containing your address, copy each column value into the . Remove the quotes and curly braces from the proof column data. Then connect your wallet and it should look something like this.

The DCA orders executed over 2 months, starting 5/24/24, 2:48 AM UTC and ending 7/23/24, 7:09 PM. The proceeds of the DCA order were owned by the , a.k.a. the DAO.

The following pools were used: , , and .

The company Ekubo, Inc., a service provider to the DAO, holds one-third of the total supply. There is no vesting schedule for these tokens. The team has come to an agreement with the DAO to hold these tokens indefinitely via to fund the company's provision of services.

The governance contract addresses can be found .

You can learn more about how the governance contracts work .

🏩
block explorer
Governor
EKUBO/ETH 5%
EKUBO/STRK 5%
EKUBO/USDC 5%
governance proposal
here
L1 Ethereum token
Starknet
Starkscan
Voyager
here
36MB
airdrop_data.csv.zip
archive
A CSV containing the entirety of the merkle tree for the EKUBO airdrop
here