Skip to content

Commit

Permalink
GITBOOK-553: change request with no subject merged in GitBook
Browse files Browse the repository at this point in the history
  • Loading branch information
jorgelinae authored and gitbook-bot committed May 9, 2024
1 parent 0d924f2 commit 1728200
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions governance/exactly-token-exa/escrowedexa-esexa.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,12 @@ Elements for the esEXA to EXA conversion process:
* Burning Mechanism: Holders will burn their esEXA tokens to initiate the vesting period and convert them into EXA tokens through [Sablier](https://sablier.com/).
* EXA Reserve: Holders must provide a “reserve” in EXA proportionally to the esEXA they want to vest. This proportion is represented in the EscrowedEXA contract as \`reserveRatio\`, the “reserve” EXA tokens to start the vesting process. The reserve percentage is 25% and can be changed through governance.

### Steps

* Step 1: Claim your esEXA Rewards 
* Step 2: Initiate the vesting of your esEXA. You must deposit 25% of the total esEXA you want to vest as an EXA reserve. 
* You can get EXA if you don’t have the required reserve amount: https://app.exact.ly/get-exa

Users can cancel the vesting at their discretion, triggering the withdrawal of all vested EXA tokens from Sablier and the associated reserve. Any unvested tokens are returned to the EscrowedEXA contract, where the corresponding esEXA tokens are minted and returned to the user.

This mechanism guarantees that the exclusive path for the users to retrieve reserved EXA tokens from the EscrowedEXA contract is by adhering to the stipulated vesting schedule.
Expand Down

0 comments on commit 1728200

Please sign in to comment.