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
{{ message }}
This repository has been archived by the owner on Nov 10, 2023. It is now read-only.
Approval transactions via WalletConnect are not proposing to and therefore not saving in the queue.
Only once transactions are submitted, does the Safe propose the transaction. When using WalletConnect, there is most likely no transaction hash and therefore no proposal occuring.
Steps to reproduce
With Safe A owning Safe B: create a transaction and approve the hash in Safe A, observing that the transaction does not appear in the queue of Safe B.
Description
Approval transactions via WalletConnect are not proposing to and therefore not saving in the queue.
Only once transactions are submitted, does the Safe propose the transaction. When using WalletConnect, there is most likely no transaction hash and therefore no proposal occuring.
Steps to reproduce
With Safe A owning Safe B: create a transaction and approve the hash in Safe A, observing that the transaction does not appear in the queue of Safe B.
Expected result
Transaction appears in the queue of Safe B.
Obtained result
Transaction does not appear in the queue.
Links
The text was updated successfully, but these errors were encountered: