SIMD-0185: Vote Account v4 #185
Conversation
jstarry
force-pushed
the
vote-account-v4
branch
from
3fc627d
to
9d8dedb
Compare
| `authorized_voters` field that correspond to epochs less than the current epoch, | ||
| only purge entries less than the previous epoch (current epoch - 1). This will | ||
| mean that the `authorized_voters` field can now hold up to 4 entries for the | ||
| epochs in the range `[current_epoch - 1, current_epoch + 2]`. Keeping the |
There was a problem hiding this comment.
is there a reason we need to store current_epoch + 2?
There was a problem hiding this comment.
Yeah that's the current design and I think it kinda makes sense because otherwise you could set a new authorized voter at the end of an epoch and immediately start using it in the next block in the new epoch and leaders would need an up to date view on any new authorized voters for each fork crossing the epoch boundary
|
I'm sorry, why is |
Up for debate still, but I put it there for now since it's easier to update the vote account all in one go. If that field remains unused by the protocol it can be used for something else in the future. |
|
Is this about a new instruction to pay the leader who landed a successful transaction? |
|
I updated the proposal to use basis points for commission values and to remove any special handling for block tips for now. |
No description provided.