This repository has been archived by the owner on Apr 15, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 16
feat: gossiping the latest valset in P2P layer in case they get pruned #560
Merged
Merged
Changes from 1 commit
Commits
Show all changes
28 commits
Select commit
Hold shift + click to select a range
9270c89
feat: gossiping the latest valset in P2P layer in case they get pruned
rach-id 96642c3
Update p2p/dht.go
rach-id 7f5f74f
Update p2p/dht.go
rach-id bc15575
Update p2p/dht.go
rach-id 479cab4
Update p2p/dht.go
rach-id 620b0bb
Update p2p/dht.go
rach-id 7b0f5fb
Update p2p/dht.go
rach-id 2a0d5e5
Update p2p/errors.go
rach-id 25fdfe4
Update p2p/keys.go
rach-id 697e0c2
Update types/latest_valset.go
rach-id 21e32ab
Update p2p/validators.go
rach-id 16b712f
Update p2p/validators_test.go
rach-id a5b2e50
Update p2p/validators_test.go
rach-id 09e6954
Update p2p/validators_test.go
rach-id e6b61d2
Update p2p/validators.go
rach-id d69f14c
Update p2p/validators.go
rach-id 8124d1c
Update p2p/validators.go
rach-id 42e1f02
Update p2p/validators.go
rach-id e13e23a
Update p2p/validators.go
rach-id 24469ea
Update p2p/validators.go
rach-id cc536e3
Update p2p/validators.go
rach-id 9b5baf8
Update p2p/validators.go
rach-id 5e726f0
fix: nil pointer
rach-id 545ccee
chore: type2 rename
rach-id 4df2e5a
Update types/latest_valset_test.go
rach-id 755ff25
fix: introduce LatestValset type to fix serialization
rach-id d4e6c41
feat: authenticate the valset to the Blobstream contract
rach-id e5a05a5
feat: add log message for deployer
rach-id File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the standard thing is naming this
qgbtypes
instead of types2There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
545ccee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
definitely not blocking, just for future reference,
celestiatypes
is better, but imo we should be specific with our imports to improve readability. for instance, what happens if we need to import"github.com/celestiaorg/celestia-app/x/blob/types"
or"github.com/celestiaorg/celestia-core/types"
as well? personally I'm not a fan of naming everything types, but the sdk and tendermint don't agree lolThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
concerning this, what do you think of making it a rule in CI? I looked for existing tools that can do this but found none, so maybe we can do a simple bash script that takes all the imports in the project, filter those we want to have the same name across all repos, then check whether the right name is used or not.
I don't think it's worth it tbh, it would just make it harder to commit code, but if there is a good reason for it, I'm in
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah I'm 100% down for adding CI to look at import names. For packages with types I think we could define a linter that is generic enough to be useful. Not sure about other package names that frequently require renaming
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#563