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
The only thing the safe-apps-provider lacks is the support for the OG gs_multi_send method for batching transactions. Supporting this method has some complexity because under the hood, the safe-apps-provider stores a fake transaction that includes the recipient address, data, etc. Since the transactions passed to the gs_multi_send method will be encoded and sent to the multisend contract, we need somehow to get the encoded data and the address of the multisend contract.
I see two options to achieve this:
Replicate the encoding/address retrieval logic from our interfaces in the safe-apps-provider
Change the txs.send return type to return the whole safe transaction object
I lean towards 2)
The text was updated successfully, but these errors were encountered:
We are migrating the wallet-connect safe app to the safe-apps-provider:
safe-global/safe-react-apps#537
The only thing the
safe-apps-provider
lacks is the support for the OGgs_multi_send
method for batching transactions. Supporting this method has some complexity because under the hood, thesafe-apps-provider
stores a fake transaction that includes the recipient address, data, etc. Since the transactions passed to thegs_multi_send
method will be encoded and sent to the multisend contract, we need somehow to get the encoded data and the address of the multisend contract.I see two options to achieve this:
safe-apps-provider
txs.send
return type to return the whole safe transaction objectI lean towards 2)
The text was updated successfully, but these errors were encountered: