|
| 1 | +import { Callout } from 'nextra/components'; |
| 2 | + |
1 | 3 | # Divergence from Ethereum |
2 | 4 |
|
3 | 5 | While Sei features full EVM compatibility, there are some distinctions between |
4 | | -Sei's EVM and Ethereum itself. |
5 | | - |
6 | | -## EVM Differences |
7 | | - |
8 | | -Unlike Ethereum mainnet which is on Cancun for its execution layer, Sei uses the |
9 | | -Shanghai version of EVM. This means that features like blob transactions are not |
10 | | -supported on Sei. |
| 6 | +Sei's EVM and Ethereum itself: |
| 7 | + |
| 8 | +| | Sei | Ethereum Mainnet | |
| 9 | +| --------------------- | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | |
| 10 | +| Gas per Second | ~ 25 MegaGas/s | ~ 3 MegaGas/s | |
| 11 | +| TPS | ~ 12,500 | ~ 11 | |
| 12 | +| Block time | 400 ms | 12 s | |
| 13 | +| Finality | Instant | Various commitment levels (i.e., safe, latest, justified, finalized) | |
| 14 | +| EVM Version | Shanghai | Cancun | |
| 15 | +| Gas Limit | 10 M | 36 M | |
| 16 | +| Byte Size Limit | 21 MB | No byte-denominated limits | |
| 17 | +| Execution environment | EVM and CosmWasm | EVM | |
| 18 | +| Address space | Dual ECDSA-derived addresses; sei-native Bech32 (sei…) + EVM-compatible address (0x…) | ECDSA-derived address (0x…) | |
| 19 | + |
| 20 | +- Sei uses the [Shanghai](https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/shanghai.md) version of EVM. This means features rolled out on Ethereum mainnet via the [Cancun](https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/cancun.md) upgrade (i.e., EIP-4844 or blob transactions) are not supported on Sei |
| 21 | +- Sei’s gas limit is 10M as opposed to Ethereum’s 30M. Sei also has a byte size limit of 21MB. |
| 22 | +- Sei has instant finality. This means the various commitment levels typical for Ethereum (i.e., safe, latest, justified) do not apply on Sei. |
| 23 | + |
| 24 | +- **Sei is a dual-execution environment (EVM and CosmWasm).** This means: |
| 25 | + - Non-EVM transactions can update EVM-accessible state. |
| 26 | + - For example, an account’s SEI balance can be affected by both Cosmos (bank send, wasm execute) transactions as well as EVM send transactions |
| 27 | + - Sei assets can not only exist as EVM (i.e., ERC20/721/1155), but also as CW (i.e., CW20, CW721) or as native (Sei, IBC, Tokenfactory). |
| 28 | + - User accounts on Sei have [two addresses](https://www.docs.sei.io/learn/account-structure) derived from the same public key (sei-native Bech32 and EVM-compatible 0x…) |
| 29 | + |
| 30 | +<Callout type="info">💡 Interoperability between EVM and CosmWasm is governed and navigated via [precompiles](./precompiles/example-usage) and [pointer contracts](./pointers/standard)</Callout> |
11 | 31 |
|
12 | 32 | ## Opcode Differences |
13 | 33 |
|
@@ -58,14 +78,6 @@ subspace: evm |
58 | 78 | value: '"0.007500000000000000"' |
59 | 79 | ``` |
60 | 80 |
|
61 | | -## Block Limit |
62 | | - |
63 | | -Sei has a gas limit of 10M on `pacific-1`, compared to |
64 | | -Ethereum’s 30M. |
65 | | - |
66 | | -In addition, Sei also has a byte size limit of 21MB, whereas Ethereum doesn’t |
67 | | -have byte-denominated limits. |
68 | | - |
69 | 81 | ## Non-EVM Transactions |
70 | 82 |
|
71 | 83 | On Sei there exists non-EVM transactions which may update states accessible by |
|
0 commit comments