-
Notifications
You must be signed in to change notification settings - Fork 628
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
Test rollkit app ibc connection to cosmos sdk app with tm wasm clients (step 2) #5854
Comments
@damiannolan we have tested the ibc connection between rollup chain(gm) and cosmos app chain(paloma) by taking avail and celestia as data availability layers. The ibc transfers got succeeded. But here I have a doubt like, If we do |
Hey @chandiniv1, thanks for the question! Indeed, you are correct - rollkit blocks will be executed by a single centralised sequencer and requires a more complex architecture in order to verify correctness of ibc packets. This issue is essentially a stepping stone as part of the greater body of work feeding into this. Verification of updates to rollkit clients will need an additional step in order to prove blocks are posted to DA. This is where a concept known as conditional clients was introduced. We will also be looking into fraud proof windows etc as part of ongoing work. There is more context available on conditional clients and architecture for rollkit/celestia in these issues:
|
finished |
Will update step docs to this repo for playground for test setup: https://github.com/chatton/gm-demo/tree/master |
Summary
Requires #5853
NOTE: we can also swap out the ibc-go-simd app chain for something like celestia testnet, as was done for step 1 of integration work already.
For Admin Use
The text was updated successfully, but these errors were encountered: