-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release v0.9.0 #2
Merged
Merged
Conversation
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
* Add update changelog script * Add CHANGELOG.md
Link to a broken user guide document is fixed. it was https://docs.babylonchain.io/docs/user-guides and now is https://docs.babylonchain.io/docs/user-guides/overview
a small spelling error has been fixed
…ing BTCHeaderHashBytes into hex
…TCCheckpointInfoResponse` (#493) chore: update proto of BtcCheckpointsInfo to return response
… keys (#494) * chore: modified EpochSubmissions query to return client friendly response * chore: removed unused pagination * chore: moved to structure that combines txs keys from same submission * fix: removed unused pagination tag * chore: moved from toResponse to NewSubsmissionKey * chore: update error msg * fix: lint removed unused import * chore: add log err msg
Co-authored-by: KonradStaniec <konrad.staniec@gmail.com>
* chore: split btc delegation response structure from query return * chore: add slashing properties to BTCDelegationResponse * fix: add verification for nil properties * chore: btc del resp finality provider (#511) * chore: update FinalityProviderDelegations to return BTCDelegatorDelegationsResponse which has delegation status * chore: reduce code diff * chore: add StakingOutputIdx to BTC del response and fix e2e ParseRespsBTCDelToBTCDel
* chore: add voting power to finality provider * fix: check of equal between finality provider and query response
* chore: add voting power to finality provider * chore: modified query FinalityProvider to return FinalityProviderResponse * fix: check of equal between finality provider and query response
* Tighten checks in CheckTransactions function * wrap errors
* Enforce that keys are unique in scripts
* chore: set signer addr as finality provider * chore: proto gen fp signer changes * chore: update to use fp addr as signer * fix: unit test check * fix: lint, removed unused import * chore: remove unused PoP * chore: removed unused func * chore: add test for valid basic * chore: update description of PoP * chore: update to use fp addr instead of deriving from bbn SK * chore: update order of addr in finality provider * chore: update readme about btcstaking protos * chore: add send msg with signer to use in testings
* Add command to print module sizes
* Add docs to public facing functions
* feat: add 08-wasm clients support Signed-off-by: aeryz <abdullaheryz@protonmail.com> * chore: bump ibc-go to v8.3.0 Signed-off-by: aeryz <abdullaheryz@protonmail.com> --------- Signed-off-by: aeryz <abdullaheryz@protonmail.com>
* refactor: moving keepers to a new struct (#697) * upgrade: framework for writing software upgrade migration function (#703) * fix: execute `PreBlocker` for upgrade module (#707) * docstring for vanilla upgrade
Disable flaky test
* feat: Add finality provider signing info (#614) * feat(jailing): Identify inactivity upon EndBlocker (#681) * feat(Inactivity): Add LivenessDelay to finality params and logic for reverting inactive flag (#689)
… events, and metrics (#714)
* Improve extracting data from op_return + add tests * remove unused constant
…` genesis state (#720)
Rename BabylonChain to BabylonLabs --------- Co-authored-by: KonradStaniec <konrad.staniec@gmail.com>
RafilxTenfen
approved these changes
Jul 29, 2024
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.
💯
gitferry
approved these changes
Jul 30, 2024
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.
No description provided.