A place for talking about the Ethereum Virtual Machine on Farcaster.

nonce is an EVM based transaction is used to prevent replay attacks.

but can i send 3 different transactions at once from the same address, but all have different nonce values?

think that nonce is being kept track of offchain.

ai x hardware skunk-works with @waitin4agi_ (twitter); 

prev: cofounded a hw x iot company @noctolabs;

IC in BTC, ETH and SOL ecosystem (systems)

i want to basically escape the sequential nature of EVM txns.

And no don’t tell me UserOps+Bundler is the solution, it works for a set of txns. that come one after another.

I am specifically talking about different txns. at once.

You need meta txs with unordered nonce support

You can never escape the sequential nature of transactions. A total ordering is fundamental

Ethereum & Optimism, cofounder Optimism. Opinions are my own

The nonce is required for replay protection. It must be unique otherwise you can play transactions more than once

permit2 uses unordered nonces

Right, so it has to be unique irrespective of the txn. being broadcasted. 

Thanks for sharing, will check this!

The nonce is required for replay protection. It must be unique otherwise you can play transactions more than once

permit2 uses unordered nonces
https://github.com/Uniswap/permit2/blob/main/src/SignatureTransfer.sol#L150

Okay, a question 1 level deeper.

- Is the nonce required to be unique to a transaction or irrespective of the transaction?

- What is this unordered nonce that you speak of any live example or spec?