Closed 0x-General closed 10 months ago
Hi @0x-General, could you please help to find out actual request and expected response payloads?
I used https://thorswap.github.io/SwapKit/ to generate a send
or swap
requests with BNB chain, here's what I got:
cosmos_signAmino
Send (standard transfer) request: https://gist.github.com/satoshiotomakan/ff31ee75455a4e8691ff38a4f7b2c498cosmos_signAmino
Swap (THORSwap) request: https://gist.github.com/satoshiotomakan/76a7f21c57e46bb2e6940a70d64b512fThese requests do not match the documentation:
request.signDoc.fee
- probably, it supposes to be optional?request.signDoc.msgs
do not have type
and value
fields.Can we expect cosmos_signDirect
request instead?
Could you please also advice, did you get this response from the TrustWallet Android app?
One note - https://thorswap.github.io/SwapKit/ generates an expected payload on cosmos_signAmino
for THORChain: https://gist.github.com/satoshiotomakan/e72631f61cbee10cc81dc0469e1e270e
Hi @0x-General, we adopted WalletCore API to be able to parse and handle BNB signing requests through WalletConnect 2.0. The new Android/iOS releases coming soon
Description When signing & broadcasting a send transaction for BNB through walletconnect, the BNB node responds with a message saying:
Looks like the signing process is incorrect. To Reproduce
Expected behavior The node should process the transaction with no error messages.
Additional context This is the message that is being broadcasted: