You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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?
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
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
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
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: