Closed
Conversation
Contributor
|
closing this out in favor of seidb project we're releasing |
masih
pushed a commit
that referenced
this pull request
Sep 29, 2025
## Describe your changes and provide context This PR adds a max voting power ratio check for each token delegation. This check will only apply when the bonded voting power > certain threshold (MaxVotingPowerEnforcementThreshold in the params). Both the threshold and max ratio are adjustable as params' fields. ## Testing performed to validate your change Unit tests Co-authored-by: Cyson <cyson@Cysons-MBP.attlocal.net>
masih
pushed a commit
that referenced
this pull request
Sep 29, 2025
masih
pushed a commit
that referenced
this pull request
Sep 29, 2025
masih
pushed a commit
that referenced
this pull request
Sep 30, 2025
## Describe your changes and provide context This PR adds a max voting power ratio check for each token delegation. This check will only apply when the bonded voting power > certain threshold (MaxVotingPowerEnforcementThreshold in the params). Both the threshold and max ratio are adjustable as params' fields. ## Testing performed to validate your change Unit tests Co-authored-by: Cyson <cyson@Cysons-MBP.attlocal.net>
masih
pushed a commit
that referenced
this pull request
Sep 30, 2025
masih
pushed a commit
that referenced
this pull request
Sep 30, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I think that if each validator on the testnet applies this version of tm-db, block times will be reduced further.
Little information about that build of tm-db:
It is much faster. We currently use it on our osmosis validator, our Juno validator and our evmos validator so it is quite fair to say that it is tested, but because it is a giant PR, it has not been merged into tm-db and can't really blame them for that. The majority of the work comes from Notional and Terra.
In addition to that, this is what we used to host our RPCs. The feedback that we get from RPC users is that ours perform extremely well and I think that this is why. So that's about another 100 nodes that use this successfully.
Likely of particular interest, is the fact that this made it possible for a number of evmos validators and evmos rpc providers to actually stay in sync up to the tip of the chain.