Skip to content
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

Closed
3 of 6 tasks
damiannolan opened this issue Feb 15, 2024 · 4 comments
Closed
3 of 6 tasks
Assignees

Comments

@damiannolan
Copy link
Member

damiannolan commented Feb 15, 2024

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

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
@damiannolan damiannolan added this to the Rollkit integration milestone Feb 15, 2024
@damiannolan damiannolan moved this to Todo 🏃 in ibc-go Feb 15, 2024
@damiannolan damiannolan moved this from Todo 🏃 to In progress 👷 in ibc-go Feb 20, 2024
@chandiniv1
Copy link
Contributor

@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 ibc-transfer from cosmos app chain to rollup chain, It will be easy for the rollup chain to verify,that it will just look whether the block header is signed by 2/3 validators or not. But if we do ibc-transfers from rollup chain to cosmos-app chain, as currently rollkit is following pessimistic approach, it have neither fraud proofs nor validators (as only sequencer will execute blocks and post it), how does the cosmos app chain verifies the transaction?
Screenshot from 2024-02-23 11-24-56

@damiannolan
Copy link
Member Author

damiannolan commented Feb 23, 2024

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:

@damiannolan damiannolan changed the title Test rollkit app ibc connection to cosmos sdk app Test rollkit app ibc connection to cosmos sdk app (step 2) Feb 28, 2024
@damiannolan damiannolan changed the title Test rollkit app ibc connection to cosmos sdk app (step 2) Test rollkit app ibc connection to cosmos sdk app with tm wasm clients (step 2) Feb 28, 2024
@charleenfei
Copy link
Contributor

finished

@github-project-automation github-project-automation bot moved this from In progress 👷 to Done 🥳 in ibc-go Feb 29, 2024
@damiannolan
Copy link
Member Author

Will update step docs to this repo for playground for test setup: https://github.com/chatton/gm-demo/tree/master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

4 participants