[Suggestion] Modified transaction format for multi-contract atomic operations

XertroVXertroV Member Posts: 10
The current tx format is:

[ nonce, receiving_address, value, [ data item 0, data item 1 ... data item n ], v, r, s ]

By changing this format to:

[ [ nonce, receiving_address, value, [ data item 0, data item 1 ... data item n ]], [ nonce, receiving_address, value, [ data item 0, data item 1 ... data item n ]], ..., v, r, s ]

we can have multiple transactions to multiple contracts in one atomic operation, since the entire bundle is signed; not each individual tx. It must be exclusively accepted or exclusively rejected.

The trivial case is `[v,r,s]` which should be counted as non-standard or ignored by choice.

Whether this finds a use or not, the small increment in the size of txs is a near negligible cost; it might even save space when people mind less about privacy.

You can still only send transactions from a single address.
Sign In or Register to comment.