- remember that optimistic rollups publish batches of txs in the calldata on ethereum, but it needs to wait for a dispute period to pass to ensure the sequencer is not publishing invalid txs before withdrawing.
- avm architecture: arbitrum is fully compatible with the evm, but it also has its vm called arbitrum virtual machine:
- execution flow and structure: arbitrum has an operating system and its core called arbos, which ensures the solitary existence, optimal performance and efficient analytics of smart contracts.
- dispute settlement speed: the avm has a custom protocol for dispute management, so that it can be acquired out on a standard vm.
- natives tuples: the avm uses tuples to define and references types in its merkle tree. the tuples can be referenced in looking up the merkle root of any tx on the evm merkle tree.
- optimistic rollup, with no mempool for bots to frontrun, but searchers can listen the queue through websockets and backrun, etc...
- currently has a centralized sequencer and whitelisted proof validation while having upgradable contracts
- faster tx processing: ethereum is operating under 15-20 tps, while the arbitrum network can process ~40 tps
- lower tx fees: in ethereum, a significant percentage of validators need to confirm the genuineness of a tx; arbitrum average fee is $~.2 compared to $6.5 (source: nansen)
ย
ย
MEV_on_Arbitrum
Folders and files
| Name | Name | Last commit date | ||
|---|---|---|---|---|
parent directory.. | ||||
ย | ย | |||
ย | ย | |||
ย | ย | |||