-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Description
Component
Cast
Describe the feature you would like
For cast send, cast sign and cast mktx (any others?) we should support a batch mode where you can actually construct 1 or more transactions, each with their own value (optional), input (optional) and destination address. I'm not entirely sure what good UX would be here.
For e.g. Ethereum/Optimism or other chains without native batching capability, this would just result in multiple transactions. For networks with native batching support, such as Tempo, this should result in 1 transaction.
Some care needs to be taken to ensure you can't construct "bogus" batches, e.g. transactions with the same nonce. It might be preferable to simply manage the nonce for the user in this case, e.g. if I am on nonce 3 and I send a batch of 3 transactions, they would have nonce 4, 5, 6 respectively. For Tempo this would just result in a transaction with nonce 4 (since it has native batching).
Additional context
There is some documentation on call batching in Tempo here.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status