Hi everyone! Recently, we hosted a different Chain Chatter session where we discussed the token LEO, Inleo, and LeoDex from a unique perspective, aiming to explain them to those who are just getting to know us or have never interacted with our documentation before. While we've made significant strides, it's always crucial to maintain a strong foundation.
In this clip:
- The maximum supply is 50 million, expected to be reached in approximately 32 years
- Block rewards decrease every year
- There are different versions of the Leo token native to Hive on other blockchains like Ethereum, BSC, Polygon, and Arbitrum
- We delve into the System Income Rewards Pool and what happens after reaching maximum supply
- Token distribution
The token Leo lies at the center of the economy of the Inleo project and all that we build. It has a maximum supply of 50 million, which decreases every year by a fixed percentage and is expected to reach that maximum in approximately 32 years.
We have multiple listings focused on establishing a presence on decentralized exchanges (DEXs). Thus, we have the native token on Hive, a blockchain with no fees and fast transactions. Additionally, we offer wLEO on Ethereum, pLEO on Polygon, bLEO on BSC, and most recently, LEO on Arbitrum.
Currently, rewards come from inflation, but in the future, after we reach the cap, a mechanism we created called System Income will handle rewards. Presently, it feeds into liquidity pools like the LEO/CACAO pool on Maya, but will gradually replace block rewards.
These rewards are allocated to three different entities: content creators, who, as long as they publish through Inleo, are eligible to receive LEO rewards; curators, users who hold LEO in stake and use it to upvote content creators, thereby allocating part of the inflation according to their stake; and investors, facilitated through the Geyser, which allocates rewards to investors in the wLEO/ETH pool, soon to be moved to the LEO/CACAO pool.
So, these are the fundamentals of the LEO token. We delve deeper into the topic in our video, and you can always visit the documentation to learn more.