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
With the upcoming release of IBC 3.0, the Interchain Accounts module will make its debut into the IBC world. This module allows to create an IBC connection between on-chain accounts of different chains. Even though such link could then be used to perform any operation between the two chains (eg. signing a message on one chain and broadcasting it to the second one), there are some limitations to what it should be done. Quoting Charly from Interchain Gmbh:
i would just also want to point out that due to the current architecture for ica (1 channel per account, bc we need ordered channels for execution and dont yet support partially ordered channels) we would like to encourage chain to chain usecases, rather than exposing to end users. this is to avoid a huge overhead for relayers. obviously the design does support many use cases, but i think we need to avoid overloading the current relayer infrastructure with a huge number of channels for now.
Inside Desmos we could leverage this linkage in order to provide users another way of creating a chain link to their profile: instead of manually generating a proof signing a message with the private key associated to the external chain account and then uploading it to Desmos using a MsgLinkChain transaction, we allow the user to create an interchain account between their Desmos account and their external chain account, and then use such interchain account to obtain the proof to be used to create the chain link.
Aside from simplifying the whole process (we should then rely only on IBC transactions), we would also make it a lot easier for future projects to link their account to a Desmos profile: they just have to implement the ICA module and we would take care of everything else.
The text was updated successfully, but these errors were encountered:
Hi @RiccardoM@bragaz , It reminds me that I had created a roughly ppt which shows the verification process to create a chain link between the two chains separately when I confirmed the chain link process with @bragaz in Campfire in 2021 March. It seems something similar with your opinion, so I just put it here.
With the upcoming release of IBC 3.0, the Interchain Accounts module will make its debut into the IBC world. This module allows to create an IBC connection between on-chain accounts of different chains. Even though such link could then be used to perform any operation between the two chains (eg. signing a message on one chain and broadcasting it to the second one), there are some limitations to what it should be done. Quoting Charly from Interchain Gmbh:
Inside Desmos we could leverage this linkage in order to provide users another way of creating a chain link to their profile: instead of manually generating a proof signing a message with the private key associated to the external chain account and then uploading it to Desmos using a
MsgLinkChain
transaction, we allow the user to create an interchain account between their Desmos account and their external chain account, and then use such interchain account to obtain the proof to be used to create the chain link.Aside from simplifying the whole process (we should then rely only on IBC transactions), we would also make it a lot easier for future projects to link their account to a Desmos profile: they just have to implement the ICA module and we would take care of everything else.
The text was updated successfully, but these errors were encountered: