Update EIP-5792: multi-chain wallet_sendCalls #8771
Conversation
|
✅ All reviewers have approved. |
pedrouid
changed the title
github-actions
bot
added
c-update
| * MUST send the calls on the same chain identified by the request's `chainId` property | ||
| * MUST send the calls in the order specified in the request | ||
| * MUST send the calls on the same chain identified by the call's `chainId` property | ||
| * MUST NOT await for any calls to be finalized to complete the batch |
There was a problem hiding this comment.
can you explain why you think we should enforce this? I'd expect this to be up to the wallet, until we have the other capability we talked about which would enforce waiting for calls to be mined across chains.
There was a problem hiding this comment.
My understanding is that we would enforce the behavior to always be "parallel" by default
So the new capability would be "sequential" if available
But my take is that either way it should be deterministic by the spec rather than wallet-dependent
There was a problem hiding this comment.
Hmm just seeing this. I do feel like generally order matters to devs, but trying to sequence multi chain calls is probably too difficult. Too hard to know when the output of one will land on the other chain, if I am, say, funding my account on chain A from chain B
Changes proposed:
chainIdfrom top-level to call-levelatomicBatchregarding multi-chain