-
Notifications
You must be signed in to change notification settings - Fork 42
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
zoneconcierge: replace chain ID with client ID for consumers #22
Conversation
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.
looks good!
Putting this PR on hold for now. Another way of resolving this issue is to enforce each chain ID to only have 1 IBC client in record. This is followed by ICS. Will need to investigate further and provide a concrete design |
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.
Great work!
Subsumes #22 --- Fixes babylonlabs-io/pm#12 This PR replaces the chain ID with the client ID for consumers in the BTC timestamping protocol. This is in line with [the IBC security model](https://tutorials.cosmos.network/academy/3-ibc/1-what-is-ibc.html) where each IBC light client corresponds to a chain, and with the BTC staking integration implementation. The PR includes: - renaming all chain ID to consumer ID, same as BTC staking integration does - using client ID to identify {epoch, finalised} chain info - changing all queries, fuzz tests, e2e tests, and doc accordingly TODO before merging the PR: - [x] wait until @gitferry verifies we can do software upgrade with empty DB and updated DB schema Plan after the PR: - Fixing compatiblity with BE/FE (need arch decisions here)
Fixes https://github.com/babylonlabs-io/pm/issues/12
This PR replaces the chain ID with the client ID for consumers in the BTC timestamping protocol. This is in line with the IBC security model where each IBC light client corresponds to a chain, and with the BTC staking integration implementation.
The PR includes:
TODO before merging the PR:
Plan after the PR: