align docs with new changes

astroport-fi · Sep 4, 2024 · f0d91c4 · f0d91c4
1 parent 0cc4346
commit f0d91c4
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 2 deletions.
diff --git a/assets/emissions_controller_general.png b/assets/emissions_controller_general.png
diff --git a/contracts/emissions_controller/README.md b/contracts/emissions_controller/README.md
@@ -19,7 +19,8 @@ If the pool is located on the Hub contract also checks, this LP token correspond
 ## Voting
 
 Users are required to have vxASTRO to cast their votes.
-They can vote for up to five whitelisted pools at once every 10 days.
+They can vote for whitelisted pools at once every epoch.
+Vote changes are not allowed after votes are cast.
 After voting, they can't change their votes until the cooldown period ends.
 Executable message accepts an array of tuples with LP token and vote weight.
 Vote weight is a number between 0 and 1. Total vote weight can't exceed 1.

diff --git a/contracts/emissions_controller_outpost/README.md b/contracts/emissions_controller_outpost/README.md
@@ -3,7 +3,8 @@
 The Emissions Controller Outpost is a lightweight satellite for the main Emissions Controller located on the Hub.
 For the vxASTRO staker perspective, this contract has the same API as the main Emissions Controller.
 However, Outpost can't perform fine-grained sanity checks for voted LP tokens.
-Same restrictions as on the Hub are applied, like voting every 10 days for up to 5 pools at once.
+Users can vote up to five pools only once per epoch.
+Once votes are cast they can't be changed until the next epoch.
 The contract composes a special internal IBC message to the Hub with the user's vote.
 If sanity checks passed on the Hub, the vote is accepted.
 In case of IBC failure or timeouts, the user can try to vote again.