-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #15 from jup-ag/jupuary-vote-1
Create 27912
- Loading branch information
Showing
1 changed file
with
11 additions
and
0 deletions.
There are no files selected for viewing
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,11 @@ | ||
This vote is for checking if the community is comfortable with 2 more Jupuaries of 700M JUP each. | ||
|
||
Because it is crucial that the whole community is unified, the team will be seeking a 70% yes vote, and will spare no effort to get there. | ||
|
||
If the vote does not pass, we will take your feedback, iterate on the proposal, and ask for a new vote. | ||
|
||
Note: For this vote, you will be asked to leave your feedback after casting your vote. | ||
|
||
The aim of Jupuary is to accelerate the growth of the community, massively decentralize the protocol, and through the entire process unify the entire community under a common vision – that Jupiter has to be one of the key winners, Jupiverse has to be a cultural force, and JUP has to become one of the main tokens in the cryptoverse. | ||
|
||
If the vote passes, the team will gain the certainty to plan and execute on the next 2 Jupuaries together with the community. |