-
Notifications
You must be signed in to change notification settings - Fork 5
There is no agreement in the community regarding the RPC method for batched transactions #1
Comments
I've put a doc for I'd appreciate your feedback before sharing it with other projects |
@DmitryBespalov, I've replied to your comments in the doc, just dropping a mention here because HackMD didn't send me any notifications about comments |
I would appreciate your feedback on the second round of wallet_batchTransaction RPC proposal, this time it is EOA "compatible", and the transaction types are exactly the same as in eth_sendTransaction. https://hackmd.io/HFHohGDbRSGgUFI2rk22bA?view EDIT: Argent team said they'd be happy to support this too. |
Richard Moore (author of ethers.js) shared his feedback: https://notes.ethereum.org/J0_Qs3dfQtGVmVTcb-rqUg |
What is the problem?
Batch transactions are becoming more popular as more dapps start supporting them. We believe that smart contracts wallets that can organically support batch transactions will be more adopted with time. But currently, different smart contract wallets don't have a shared standard for batching transactions. For example, we implemented the "gs_multi_send" RPC method, but Argent uses the "wc_multicall" method.
Why is it relevant?
If we support one or several batching RPC methods, we need to work on a shared vision across the community.
How can we track the problem?
We need to ensure that the most adopted smart contract wallets with batching functionality support the same RPC method.
Links
Reference discussion: safe-global/safe-apps-sdk#245
The text was updated successfully, but these errors were encountered: