Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/evm/developing/fees.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,7 @@ Etherlink EVM<!--TEVM--> calculates the inclusion fee with this equation:
inclusion_fee = 0.000004 XTZ * (150 + tx.data.size() + tx.access_list.size())
```

For EIP-7702 transactions, there is an additional term: the size of the authorization list.
For EIP-7702 transactions, there is an additional term: the size of the authorization list (125 bytes per authorization).

## Gas limit

Expand Down
2 changes: 1 addition & 1 deletion docs/evm/get-started/network-information.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -228,7 +228,7 @@ These precompiled contracts are specific to Etherlink EVM{/* TEVM */}:
<td><InlineCopy code="0xff00000000000000000000000000000000000002" href="https://shadownet.explorer.etherlink.com/address/0xff00000000000000000000000000000000000002" abbreviate="5,4"></InlineCopy></td>
</tr>
<tr>
<td><Link to="/evm/nac-usage">Native Atomic Calls</Link></td>
<td><Link to="/evm/nac-usage">Native Atomic Composability (NAC)</Link></td>
<td><InlineCopy code="0xff00000000000000000000000000000000000007" href="https://explorer.etherlink.com/address/0xff00000000000000000000000000000000000007" abbreviate="5,4"></InlineCopy></td>
<td><InlineCopy code="0xff00000000000000000000000000000000000007" href="https://shadownet.explorer.etherlink.com/address/0xff00000000000000000000000000000000000007" abbreviate="5,4"></InlineCopy></td>
</tr>
Expand Down
2 changes: 1 addition & 1 deletion docs/michelson/bridging.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,4 +9,4 @@ This page is under construction, the bridging website is being worked out.
Come back soon!
:::

In the meantime, you can [bridge tokens to the EVM interface](/evm/bridging/) and control them via [Native Atomic Calls](/michelson/nac-usage).
In the meantime, you can [bridge tokens to the EVM interface](/evm/bridging/) and control them via [Native Atomic Composability (NAC)](/michelson/nac-usage).
2 changes: 1 addition & 1 deletion docs/overview/accounts-and-aliases.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ evm_alias = keccak256(utf8(tz_address_base58check))[0:20]

When an EVM account interacts with the Michelson runtime for the first time, a Michelson alias is created as a **KT1 smart contract**. This contract automatically forwards any tez it receives back to the native EVM account via the gateway.

The KT1 alias address is computed by applying **BLAKE2b with a 20-byte output** to the the UTF-8 bytes of the lowercase hex string including the `0x` prefix, then encoding the result as a KT1 contract hash:
The KT1 alias address is computed by applying **BLAKE2b with a 20-byte output** to the UTF-8 bytes of the lowercase hex string including the `0x` prefix, then encoding the result as a KT1 contract hash:

```
kt1_alias = KT1(blake2b_160(utf8("0x" + lowercase_hex(evm_address))))
Expand Down
29 changes: 14 additions & 15 deletions docs/overview/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ title: Architecture
## Seamless integration

To enable the seamless integration of the two ecosystems (EVM and Michelson) in a single blockchain, Etherlink<!--TX--> provides **Native Atomic Composability** (sometimes shortened as NAC): smart contracts in one interface can call contracts in the other within a single atomic transaction.
Thanks to the atomic composition combined with the use of the same native token, Etherlink<!--TX--> can be seen as **unified execution layer**, constituting a single economical space.
Thanks to the atomic composition combined with the use of the same native token, Etherlink<!--TX--> can be seen as **a unified execution layer**, constituting a single economic space.

Each interface is implemented by a dedicated runtime exposing a standard RPC endpoint.

Expand All @@ -24,22 +24,21 @@ When an EVM contract calls a Michelson contract on Etherlink<!--TX-->, both exec

```mermaid
graph TB
subgraph tools["Developer Tools :"]
eth["Ethereum tools :<br/>(MetaMask,<br/>Hardhat,<br/>Foundry...)<br/><br/>"]
tez["Tezos tools :<br/>(Temple,<br/>Taquito,<br/>tzkt...)<br/><br/>"]
end
subgraph chain["Etherlink chain :"]
evm["EVM runtime :<br/>Ethereum<br/>JSON-RPC<br/><br/>"]
mic["Michelson runtime :<br/>Tezos<br/>JSON-RPC<br/><br/>"]
evm <-->|"cross-runtime , <br/>atomic calls<br/><br/>"| mic
subgraph tools["Developer tools"]
eth["Ethereum tools<br/>(MetaMask,<br/>Hardhat,<br/>Foundry...)"]
tez["Tezos tools<br/>(Temple,<br/>Taquito,<br/>TzKT...)"]
end
subgraph chain["Etherlink chain"]
evm["EVM runtime<br/>Ethereum JSON-RPC"]
mic["Michelson runtime<br/>Tezos RPC"]
evm <-->|"cross-runtime<br/>atomic calls"| mic
end

l1["Tezos Layer1 :<br/>(Smart<br/>Rollup)<br/><br/>"]
l1["Tezos Layer 1"]

eth --> evm
tez --> mic
evm --> l1
mic --> l1
chain -->|"anchored as a Smart Rollup"| l1
```

This is fundamentally different from **L1↔L2 bridging** (moving assets between Tezos L1 and Etherlink<!--TX-->) or **cross-chain bridging** (connecting two independent chains through a third-party relayer).
Expand All @@ -50,8 +49,8 @@ In both bridging cases, the two sides are separate ledgers that must be reconcil
| Chains / layers involved | 2 | 3+ | 1 |
| Number of transactions | 2+ | 4+ | 1 |
| Atomic (all-or-nothing) | No | No | Yes — reverts entirely |
| Latency | Minutes to hours | Minutes to hours | Same block (~500 ms) |
| Asset representation | Wrapped tokens | Doubly-wrapped tokens | Native tokens |
| Latency | Minutes (deposits) to days (withdrawals) | Minutes to hours | Same block (~500 ms) |
| Asset representation | Native tez; wrapped FA tokens | Doubly-wrapped tokens | Native tokens |
| Trust assumption | Bridge operator | Multiple bridge operators | None — same kernel |

### NAC call sequence
Expand All @@ -75,7 +74,7 @@ sequenceDiagram
GW-->>EVM: outcome
EVM-->>U: transaction receipt

Note over EVM,M: One atomic block — all or nothing
Note over EVM,M: One atomic transaction — all or nothing
```

Because the two runtimes share the same ledger, there are no wrapped tokens to mint or burn, no bridge relayer to trust, and no risk of one side completing while the other fails.
Expand Down
9 changes: 6 additions & 3 deletions docs/progress/upgrades.md
Original file line number Diff line number Diff line change
Expand Up @@ -173,10 +173,13 @@ For more information, see [Announcing Etherlink 6.6: a security hardening kernel

## Etherlink 7.0 (Ganesha)

The Etherlink 7.0 upgrade went live on 13 August 2026 through the slow kernel governance process and introduced a series of new features preparing for the launch of Tezos X.
In particular, it added the new Michelson interface allowing to run Michelson smart contracts, and Native Atomic Calls for seamlessly combining EVM and Michelson contracts.
The Etherlink 7.0 upgrade went live on 20 August 2026 through the fast kernel governance process and brought the largest expansion of Etherlink's scope since launch.
In particular, it added the new Michelson interface, which runs Michelson smart contracts and brings the Tezos account model to Etherlink, and Native Atomic Composability (NAC) for seamlessly combining EVM and Michelson contracts.

For more information, see [Announcing Ganesha: A 7th Upgrade Proposal for Etherlink Mainnet](https://medium.com/@etherlink/announcing-ganesha-a-7th-upgrade-proposal-for-etherlink-mainnet-ae0a3af93aba).
Etherlink 7.0 was initially proposed through the slow kernel governance process on 2 August 2026.
After a security vulnerability was found in that kernel during continued testing, bakers were asked to reject the proposal — Etherlink Mainnet was never exposed to the vulnerability — and a patched kernel was resubmitted through the fast kernel governance process on 19 August 2026.

For more information, see [Announcing Ganesha: A 7th Upgrade Proposal for Etherlink Mainnet](https://medium.com/@etherlink/announcing-ganesha-a-7th-upgrade-proposal-for-etherlink-mainnet-ae0a3af93aba) and [Etherlink 7.0 (Ganesha): resubmission via Fast governance](https://forum.tezosagora.org/t/etherlink-7-0-ganesha-resubmission-via-fast-governance-on-wednesday-august-19th/7159).

## Changelog

Expand Down
2 changes: 1 addition & 1 deletion docs/testing/testnet.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -42,5 +42,5 @@ Examples of using test networks are on other pages in this documentation.

## Etherlink{/* TX */} Previewnet

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strictly speaking it's called Tezos X Previewnet and i don't think there is a need to “downcast” it to Etherlink Previewnet? or at least no decision was made about that

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong PR


The [Previewnet test network](/testing/previewnet) is a temporary testnet made available before the addition of the Michelson interface to Etherlink{/* TX */}, for developers trying to test Native Atomic Calls before Etherlink upgrade 7.
The [Previewnet test network](/testing/previewnet) is a long-running test network that runs the upgrade-7 feature set (the Michelson interface and Native Atomic Composability) ahead of the other Etherlink{/* TX */} networks.
Previewnet is still available for some time.
Loading