-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
461d59a
commit befef5d
Showing
14 changed files
with
52 additions
and
7 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
# 📊 Tokenomics | ||
|
||
## Token Allocation <a href="#8de4" id="8de4"></a> | ||
|
||
The total token supply will be 10,000,000 EXA and will be distributed as follows: | ||
|
||
* **Community:** 4,500,000 EXA (45.00%) will be distributed to Exactly Protocol’s community to foster community engagement, awareness, and protocol adoption. | ||
* **Team, Advisors, and Investors:** 4,500,000 EXA (45.00%) will be distributed to Exactly’s employees, advisors, and investors. | ||
* **DAO Treasury:** The Exactly DAO Treasury will receive an immediate allocation of 1,000,000 EXA (10%) of the total supply. It grants the Treasury immediate access to necessary resources for its role within the ecosystem. | ||
|
||
<figure><img src="../../.gitbook/assets/image (1).png" alt="" width="563"><figcaption></figcaption></figure> | ||
|
||
## Token Distribution for the Community <a href="#2394" id="2394"></a> | ||
|
||
The total Community token supply will be distributed as follows: | ||
|
||
### **Airdrop for early users:** <a href="#71b6" id="71b6"></a> | ||
|
||
Since we launched the OP token rewards program in April, the community members already using the Protocol in OP Mainnet will receive an airdrop of 1% (100,000 EXA) of the total token supply, fostering community engagement, awareness, and protocol adoption. The criteria will be based on the proportion of already distributed OP rewards through our [Rewards Controller](https://docs.exact.ly/guides/protocol/rewardscontroller), measured on July 18, 2023, at 19:00 UTC. Users assigned OP rewards but didn’t claim them will also be eligible for the airdrop. | ||
|
||
Users can start claiming their tokens on July 25, 2023, at 14:00 UTC. We will implement a linear stream of 4 months for airdrop tokens, starting on the actual claiming date, ensuring a controlled and steady supply of EXA tokens. To facilitate token distribution, we have selected [Sablier](https://sablier.com/) as a platform that meets high security and robustness standards. All the processes will happen through the Exactly app in the new Governance section. | ||
|
||
### **EXA Incentives and Community Grants:** <a href="#f9d8" id="f9d8"></a> | ||
|
||
The protocol users will receive 5% (500,000 EXA) of the total token supply during 2023 through the current Rewards Controller Contract and other incentive mechanism. **The** [**EXA token rewards**](https://medium.com/@exactly\_protocol/exactly-rewards-update-introducing-exa-rewards-extending-op-rewards-program-6dd4a3dffe7a) **will start on July 24, 2023**. The remaining EXA tokens will be released over 36 months beginning January 1, 2024. | ||
|
||
The Exactly DAO will be also awarding **EXA token grants** to those builders who want to build on top of Exactly Protocol to foster the growth of the Exactly ecosystem. | ||
|
||
To ensure the optimal use of our available token supply, we have already introduced our [Rewards Controller Contract](https://docs.exact.ly/guides/protocol/rewardscontroller) as a distribution rule that adjusts rewards based on the percentage of the target loan volume achieved within the Exactly Protocol, using tokens allocated for community rewards. | ||
|
||
## Token distribution for Team Members, Advisors, and Investors <a href="#6f74" id="6f74"></a> | ||
|
||
We have implemented a linear lock-up period of 36 months, starting on January 1, 2024. | ||
|
||
You can see all the EXA tokens will be distributed in the following graphic: | ||
|
||
<figure><img src="../../.gitbook/assets/image (2).png" alt="" width="563"><figcaption></figcaption></figure> | ||
|
||
|
||
|
||
\ | ||
\ |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters