Closed tomtau closed 2 years ago
(opened this issue to sync up / in order not to duplicate efforts :))
Beautiful! (On the ibc-rs side, no one is working on ICS 006, so we should be good. In contrast, we may update the protos, but it's not going to be very soon e.g., within 1-2 weeks; but there shouldn't be conflicts there anyway.)
In contrast, we may update the protos, but it's not going to be very soon e.g., within 1-2 weeks; but there shouldn't be conflicts there anyway
Thanks for the heads-up. I'll keep rebasing my branch with the latest master to keep everything updated.
Is the Crypto.com team planning on building a solo machine relayer/orchestrator in Rust?
Is the Crypto.com team planning on building a solo machine relayer/orchestrator in Rust?
what do you mean by "relayer/orchestrator"? Do you mean a solo machine that would open two connections against two different networks and do synchronous ops between the networks (e.g. transfer-in/transfer-out ICS20)?
Is the Crypto.com team planning on building a solo machine relayer/orchestrator in Rust?
Is there any reason for the normal relayer not to work with solo machines?
I think of it something that generate and process IBC packets for an IBC solo machine.
The normal relayer would need new functions to injest and deliver packets that aren't based on Tendermint rpc.
The normal relayer would need new functions to injest and deliver packets that aren't based on Tendermint rpc.
By tendermint RPC, do you mean these GRPC endpoints? https://github.com/cosmos/ibc-go/blob/97f8985e485ea067d187a0813ca880d771b56abc/proto/ibc/core/channel/v1/tx.proto#L12
The normal relayer would need new functions to injest and deliver packets that aren't based on Tendermint rpc.
By tendermint RPC, do you mean these GRPC endpoints? https://github.com/cosmos/ibc-go/blob/97f8985e485ea067d187a0813ca880d771b56abc/proto/ibc/core/channel/v1/tx.proto#L12
AFAIK, Tendermint JSON-RPC, as the relayer uses it for the light client: https://github.com/cosmos/relayer/blob/v0.8.2/relayer/tm-light-client.go ?
I think of it something that generate and process IBC packets for an IBC solo machine.
@devashishdxt is working on CLI that will leverage the client from https://github.com/informalsystems/ibc-rs/compare/master...devashishdxt:solo-machine i.e. AFAIK do what you described, but internal/embedded -- so far no plan for some external interface to the solo machine, but it may evolve out of it.
Is crypto.com also planning to create a solo machine instance that uses the solo machine client? We haven't seen one in the wild yet, would like to give this effort visibility if so.
Is crypto.com also planning to create a solo machine instance that uses the solo machine client? We haven't seen one in the wild yet, would like to give this effort visibility if so.
I'm doing a POC here: https://github.com/devashishdxt/ibc-solo-machine
@hxrts one thing to note is that due to IBC spec and implementation bugs, a solo machine can currently only connect to networks that have applied https://github.com/cosmos/ibc-go/pull/123
Noted, thanks @tomtau. Also @brapse @fedekunze are interested in connecting with you regarding this effort.
Not clear if this issue is still relevant. Optimistically closing.
Had a look at https://github.com/devashishdxt/ibc-solo-machine and I don't see much activity. Please let us know otherwise, esp. if any changes should be upstreamed into the Hermes relayer. Thank you.
Crate
proto (potentially relayer etc.)
Summary
Currently, the IBC solo machine client isn't supported.
Problem Definition
https://github.com/cosmos/ics/blob/master/spec/ics-006-solo-machine-client/README.md
Proposal
@devashishdxt has been working on this
https://github.com/informalsystems/ibc-rs/compare/master...devashishdxt:solo-machine
so this will be upstreamed when ready.
For Admin Use