WalletConnect + Multix issue: getting error while trying to do cross-chain transfer from Polkadot to Hydration

[muddlebee]

Getting error while trying to do cross-chain transfer from Polkadot to Hydration using multix+walletconnect

1. Connect your multix+walletconnect
2. Goto https://app.hydration.net/cross-chain
3. Click on Transfer, then the error appears as below

[muddlebee]

but the option to Sign is appearing in Multix

[muddlebee]

and for better context

• I do have sufficient balance and min 20 DOT to do a multisig txn
• and no other pending txns are present

[Tbaut]

Thank you for the issue, this is fine, the TX will be submitted by Multix!
I need to find out with the hydration team to see how to make the experience better. If you submit the Tx with Multix, and it's signed by other signatories, then it'll be all good.

[muddlebee]

I was doing cross-chain transfer with 0.1 DOT which is below the threshold I guess. worked with more amount.. a more meaningful error in Hydradx will be handy..

Although the error message still appears after a succesful cross-chain transfer,..

[Tbaut]

I don't think Hydration has any way to know about the error at this stage. It's really any tx that results in this error screen IMHO although it's actually successfully passed to Multix.

[muddlebee]

@Tbaut so I had to re-connect walletConnect sessions two times for multisig account

• connect once for cross chain transfer of Polkadot to Hydration
• disconnect and connect once again for Hydration swaps

can we somehow make this experience better? I find it little painful to use multisigs currently haha :D Lovely app multix btw ❤️

for the average retail user, it feels like a struggle to setup cross-chain multisig and understand the flow in hydration @jak-pan if we can add a section in docs it will be great :)

[jak-pan]

@Tbaut so I had to re-connect walletConnect sessions two times for multisig account

• connect once for cross chain transfer of Polkadot to Hydration
• disconnect and connect once again for Hydration swaps

can we somehow make this experience better? I find it little painful to use multisigs currently haha :D Lovely app multix btw ❤️

for the average retail user, it feels like a struggle to setup cross-chain multisig and understand the flow in hydration @jak-pan if we can add a section in docs it will be great :)

This is specific issue with wallet connect. You connect to two separate chains and we'll need to check if it's supported in the new version https://reown.com/blog/walletconnect-is-now-reown

[jak-pan]

I don't think Hydration has any way to know about the error at this stage. It's really any tx that results in this error screen IMHO although it's actually successfully passed to Multix.

Thank you for the issue, this is fine, the TX will be submitted by Multix! I need to find out with the hydration team to see how to make the experience better. If you submit the Tx with Multix, and it's signed by other signatories, then it'll be all good.

Do you have any susggestions here?

[Tbaut]

The only think I'm thinking of is telling the WC maintainers about our use case and hoping they let us implement a flag or some way to explain that the app shouldn't expect any answer. Or maybe that the Dapp could identify the wallet, and if it's a multisig wallet (e.g from a shared list or something) then react differently.