Hello,
I’m working on a dApp used to make payments, and some of our users are using Fireblocks.
When making a payment, they connect to their Fireblocks account via WalletConnect (we do not have any API key).
They’ve been facing issues when making payments on Solana.
All Solana transactions sent from our dApp to Fireblocks via WalletConnect are considered as SOLANA_MESSAGE instead of TRANSFER.
However, if the signing process takes more than a few minutes, which often happens, the connection between the dApp and Fireblock will close.
Then, they will be able to complete the signing process, but once the message is signed, nothing happens with it (as the dApp x Fireblocks connection is closed) and the transaction is never broadcasted on-chain.
I was able to replicate with my own Fireblock account:
I made a SOL transfer from my Fireblock workspace directly. It is marked as TRANSFER, associated txId: d6ca59d0-00ef-4dbb-b49f-bd4a488059a7
I made a SOL transfer from the dApp using Fireblocks via WalletConnect, it is marked as SOLANA_MESSAGE, associated txId 67c7f62b-043d-4f23-813e-5c91c38cd835
Here is the code that we use to send the transaction:
As you can see, we’re using the latestBlockHeight strategy. Should we switch to the nonce strategy to make this work ?
If that’s the case, how can we retrieve the inputs to use for the nonce strategy ?
If you can help me with this, it would be much appreciated.
Thanks,
Léo