how to make transactions execution work when using safe from our dapp? #2489
Unanswered
abhijeetbhagat
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
we have a dapp (app.enscribe.xyz) that allows users set ENS names for their smart contracts. we use rainbowkit to connect the dapp to wallets. our dapp works fine with wallets like metamask, coinbase but recently a user reported that they could not get safe wallet with multisig to work (they were connecting to safe via walletconnect in rainbowkit).
when we investigated the problem, we noticed that the dapp kicks off a transaction (lets say hash is 0xabc) & waits for it to complete as usual. on the safe wallet side, it starts a new multisig transaction (lets say hash is 0x123) as a result which we are able to sign & execute successfully. this is where the problem comes - since the transaction hash kicked off by our dapp (0xabc) is different from the one kicked off by safe (0x123), our dapp times out waiting for a confirmation for its own transaction (0xabc) eventually.
is this problem trivial to solve? if so, what is the fix?
EDIT: forgot to mention that when we check the logs of the safe transaction on etherscan, we do see our dapp transaction hash listed in the log like this (highlighted in orange):

Beta Was this translation helpful? Give feedback.
All reactions