You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All validators should be continually voting on either the last transaction or the last vote (which is also a transaction) at a rate of VOTE_TIMEOUT_MS. But if no new transaction occurs after VOTE_TIMEOUT_MS, the validator will stop voting until the next transaction is seen. Instead after VOTE_TIMEOUT_MS it should vote on whatever the last transaction seen is, and if it's the same transaction then it can just vote on it again.
* Use u128 for all the math but store in u64
* tests
* missing changes
* bulds
* specific conversion failure
* fix tests
* use large numbers
* Rebase and fix merge issue from new tests
Co-authored-by: Jon Cinque <[email protected]>
All validators should be continually voting on either the last transaction or the last vote (which is also a transaction) at a rate of VOTE_TIMEOUT_MS. But if no new transaction occurs after VOTE_TIMEOUT_MS, the validator will stop voting until the next transaction is seen. Instead after VOTE_TIMEOUT_MS it should vote on whatever the last transaction seen is, and if it's the same transaction then it can just vote on it again.
ref: https://github.com/solana-labs/solana/blob/master/src/replicate_stage.rs#L65
The text was updated successfully, but these errors were encountered: