-## Withdrawing tokens from Etherlink to layer 1
+## Withdrawing tokens from Etherlink EVM to layer 1
-The process of bridging FA-compatible tokens from Etherlink to layer 1 (also known as withdrawing tokens) follows these general steps:
+The process of bridging FA-compatible tokens from Etherlink EVM to layer 1 (also known as withdrawing tokens) follows these general steps:
-1. The user calls the FA bridging precompiled contract on Etherlink and includes this information:
+1. The user calls the FA bridging precompiled contract on Etherlink EVM and includes this information:
- The address of the ERC-20 proxy contract that manages the tokens
- The user's layer 1 address or the address of a contract to send the tokens to
@@ -78,7 +78,7 @@ The process of bridging FA-compatible tokens from Etherlink to layer 1 (also kno
1. The proxy contract sends the information about the withdrawal to the helper contract by putting it in a transaction in the Smart Rollup outbox.
This transaction includes the target layer 1 address.
- This outbox message becomes part of Etherlink's commitment to its state.
+ This outbox message becomes part of Etherlink's commitment to its state.
1. When the commitment that contains the transaction is cemented on layer 1, anyone can run the transaction by running the Octez client `execute outbox message` command.
@@ -90,6 +90,6 @@ This transaction includes the target layer 1 address.
1. The helper contract sends the tokens to the target layer 1 address.
-This diagram is an overview of the process of bridging tokens from Etherlink to layer 1:
+This diagram is an overview of the process of bridging tokens from Etherlink EVM to layer 1:
diff --git a/docs/bridging/bridging-fa-transactions.md b/docs/evm/bridging/bridging-fa-transactions.md
similarity index 75%
rename from docs/bridging/bridging-fa-transactions.md
rename to docs/evm/bridging/bridging-fa-transactions.md
index 1bbac265..bb892bac 100644
--- a/docs/bridging/bridging-fa-transactions.md
+++ b/docs/evm/bridging/bridging-fa-transactions.md
@@ -6,15 +6,15 @@ dependencies:
Because the contracts that control bridging FA tokens follow the [TZIP-029](https://gitlab.com/baking-bad/tzip/-/blob/wip/029-etherlink-token-bridge/drafts/current/draft-etherlink-token-bridge/etherlink-token-bridge.md) standard, the transactions to bridge tokens are the same for any token.
-## Depositing FA tokens from layer 1 to Etherlink
+## Depositing FA tokens from layer 1 to Etherlink EVM
-It takes a few transactions to bridge a token from layer 1 to Etherlink:
+It takes a few transactions to bridge a token from layer 1 to Etherlink EVM:
- A transaction to give the token bridge helper contract access to the tokens
- A transaction to initiate the deposit
-- A transaction to claim the tokens on Etherlink
+- A transaction to claim the tokens on Etherlink EVM
-Follow these steps to deposit FA-compliant tokens from layer 1 to Etherlink:
+Follow these steps to deposit FA-compliant tokens from layer 1 to Etherlink EVM:
1. Give the token bridge helper contract access to the tokens, depending on the type of token:
@@ -44,7 +44,7 @@ Follow these steps to deposit FA-compliant tokens from layer 1 to Etherlink:
--burn-cap 0.1
```
-1. Call the token bridge helper's `deposit` entrypoint and pass the address of the Etherlink Smart Rollup and the address of the Etherlink account to send the tokens to, as in this example:
+1. Call the token bridge helper's `deposit` entrypoint and pass the address of the Etherlink Smart Rollup and the address of the Etherlink EVM account to send the tokens to, as in this example:
```bash
octez-client --wait none transfer 0 from my_wallet \
@@ -55,15 +55,15 @@ Follow these steps to deposit FA-compliant tokens from layer 1 to Etherlink:
```
The token bridge helper contract sends the tokens to the ticketer contract, which issues a ticket that represents the tokens.
- The token bridge helper contract sends that ticket to Etherlink.
+ The token bridge helper contract sends that ticket to Etherlink EVM.
-1. When the deposit is in an Etherlink block, call the FA bridging precompiled contract contract's `claim` function to cause the ERC-20 proxy contract to mint the tokens.
+1. When the deposit is in an Etherlink EVM block, call the FA bridging precompiled contract contract's `claim` function to cause the ERC-20 proxy contract to mint the tokens.
The address of the precompiled contract is `0xff00000000000000000000000000000000000002` and to call the function you can use the ABI `claim(uint256 depositId)`, where `depositId` matches the `depositId` that was emitted in a previous event for this transfer by the precompile (`QueuedDeposit(uint256 depositId, address recipient, uint256 amount, uint256 timelock, uint256 depositCount)`).
As a reference, here is an [example of the sequencer injecting a deposit](https://explorer.etherlink.com/tx/0x5a06fe64e880d6d1f53c243477cd5656204712f1543b607340996ad246158669) and here is an [example of the corresponding claim transaction](https://explorer.etherlink.com/tx/0xe017665cd7bfdef375a863114ac9f7ed2538da4d8584b0f1e0aa71ce96342aee).
- The precompiled contract sends information about the deposit to the ERC-20 proxy contract, which mints the tokens and sends them to the Etherlink account.
+ The precompiled contract sends information about the deposit to the ERC-20 proxy contract, which mints the tokens and sends them to the Etherlink EVM account.
:::note
@@ -72,20 +72,20 @@ Follow these steps to deposit FA-compliant tokens from layer 1 to Etherlink:
:::
-To see the tokens in your Etherlink wallet, look up the ERC-20 proxy contract in a block explorer or use its address to manually add the tokens to your wallet.
-Because the Etherlink tokens are compatible with the ERC-20 standard, EVM-compatible wallets should be able to display them.
+To see the tokens in your Etherlink EVM wallet, look up the ERC-20 proxy contract in a block explorer or use its address to manually add the tokens to your wallet.
+Because the Etherlink EVM tokens are compatible with the ERC-20 standard, EVM-compatible wallets should be able to display them.
-## Withdrawing FA tokens from Etherlink to layer 1
+## Withdrawing FA tokens from Etherlink EVM to layer 1
-It takes two transactions to withdraw an FA token back to Etherlink: one to initiate the withdrawal and another to run the outbox transaction on Tezos layer 1.
-As described in [Bridging FA tokens](/bridging/bridging-fa), you must wait two weeks to run the outbox transaction due to the Smart Rollup refutation period.
+It takes two transactions to withdraw an FA token back to layer 1: one to initiate the withdrawal and another to run the outbox transaction on Tezos layer 1.
+As described in [Bridging FA tokens](/evm/bridging/bridging-fa), you must wait two weeks to run the outbox transaction due to the Smart Rollup refutation period.
Normally, an automated system run by Optimistic Labs runs these outbox transactions as soon as the refutation period is over, which sends the withdrawn tez to the layer 1 account.
However, pending outbox transactions expire after a period equal to the refutation period.
Therefore, if the system that runs these outbox transactions is down for two weeks after the refutation period ends, the transactions may be lost.
Neither of these transactions are easy to do by yourself.
-Initiating the withdrawal requires sending complex information about the ticket and contracts to the FA2 withdrawal precompile on Etherlink.
-Running the outbox transaction requires you to know the level of the Etherlink commitment that contains it in order to get its proof and commitment, and there is no easy way to get that information without using an indexer to check each level for the transaction.
+Initiating the withdrawal requires sending complex information about the ticket and contracts to the FA2 withdrawal precompile on Etherlink EVM.
+Running the outbox transaction requires you to know the level of the Etherlink commitment that contains it in order to get its proof and commitment, and there is no easy way to get that information without using an indexer to check each level for the transaction.
The command-line tool at https://github.com/baking-bad/etherlink-bridge provides commands that can help with the withdrawal transactions.
diff --git a/docs/bridging/bridging-fa.md b/docs/evm/bridging/bridging-fa.md
similarity index 57%
rename from docs/bridging/bridging-fa.md
rename to docs/evm/bridging/bridging-fa.md
index 1704aeba..bd7338d7 100644
--- a/docs/bridging/bridging-fa.md
+++ b/docs/evm/bridging/bridging-fa.md
@@ -1,45 +1,45 @@
---
-title: Bridging FA tokens between Tezos layer 1 and Etherlink
+title: Bridging FA tokens between Tezos layer 1 and Etherlink EVM # tevm
sidebar_label: Bridging FA tokens
---
import CementingDelayNote from '@site/docs/conrefs/cementing-delay.md';
-You can bridge FA standards-compliant tokens in and out of Etherlink by deploying contracts that move the tokens.
-Then you can create dApps that use these contracts to move tokens or send a request to the Etherlink team to add your tokens to the bridge at https://bridge.etherlink.com/tezos.
+You can bridge FA standards-compliant tokens in and out of Etherlink EVM by deploying contracts that move the tokens.
+Then you can create dApps that use these contracts to move tokens or send a request to the Etherlink team to add your tokens to the bridge at https://bridge.etherlink.com/tezos.
The Tezos FA standards are token standards like the Ethereum ERC-20, ERC-721, and ERC-1155 standards.
For more information about the FA standards, see [Token standards](https://docs.tezos.com/architecture/tokens#token-standards) on docs.tezos.com.
Two bridging operations are available:
-- Bridging tokens from Tezos layer 1 to Etherlink is referred to as _depositing_ tokens.
-Depositing an FA token locks it in a contract on layer 1 and mints an equivalent ERC-20 token on Etherlink.
-- Bridging tokens from Etherlink to Tezos layer 1 is referred to as _withdrawing_ tokens.
-Withdrawing an FA token burns the ERC-20 token on Etherlink and unlocks the equivalent token on Tezos layer 1.
+- Bridging tokens from Tezos layer 1 to Etherlink EVM is referred to as _depositing_ tokens.
+Depositing an FA token locks it in a contract on layer 1 and mints an equivalent ERC-20 token on Etherlink EVM.
+- Bridging tokens from Etherlink EVM to Tezos layer 1 is referred to as _withdrawing_ tokens.
+Withdrawing an FA token burns the ERC-20 token on Etherlink EVM and unlocks the equivalent token on Tezos layer 1.
-Like the bridge that transfers XTZ tokens (see [Bridging XTZ between Tezos layer 1 and Etherlink](/bridging/bridging-tezos)), the FA bridge is permissionless, meaning that anyone can use it without restrictions or the intervention of a third party.
-It is also trustless, meaning that it relies on automated, transparent, and audited smart contracts installed on Etherlink and Tezos.
+Like the bridge that transfers XTZ tokens (see [Bridging XTZ between Tezos layer 1 and Etherlink EVM](/evm/bridging/bridging-tezos)), the FA bridge is permissionless, meaning that anyone can use it without restrictions or the intervention of a third party.
+It is also trustless, meaning that it relies on automated, transparent, and audited smart contracts installed on Etherlink EVM and Tezos.
-The explorer at https://bridge.explorer.etherlink.com shows bridging transactions between Tezos Mainnet and Etherlink Mainnet.
+The explorer at https://bridge.explorer.etherlink.com shows bridging transactions between Tezos Mainnet and Etherlink Mainnet.
@@ -32,13 +32,13 @@ These bridges are permissionless; anyone can use them without restrictions or th
Tezos bridge
- Bridges XTZ and approved FA tokens from Tezos layer 1 to Etherlink and back
+ Bridges XTZ and approved FA tokens from Tezos layer 1 to Etherlink EVM{/* TEVM */} and back
Mainnet
Shadownet Testnet
EVM bridge
- Bridges assets from EVM chains to wrapped assets on Etherlink and back
+ Bridges assets from EVM chains to wrapped assets on Etherlink EVM{/* TEVM */} and back
Mainnet
Shadownet Testnet
diff --git a/docs/evm/developing/compatibility.md b/docs/evm/developing/compatibility.md
new file mode 100644
index 00000000..e012ff40
--- /dev/null
+++ b/docs/evm/developing/compatibility.md
@@ -0,0 +1,27 @@
+---
+title: Compatibility with Ethereum
+---
+
+# Compatibility with Ethereum
+
+The EVM Interface targets compatibility with the Ethereum ecosystem:
+
+- Supports the **Ethereum JSON-RPC** standard
+- Supports standard EVM opcodes and precompiles
+- Compatible with tooling such as MetaMask, ethers.js, viem, Hardhat, and Foundry
+
+## Differences between Etherlink EVM and Ethereum
+
+While Etherlink EVM is intended to be fully EVM-compatible, it differs in some ways:
+
+- As described in [Ethereum endpoint support](/evm/developing/endpoint-support), Etherlink EVM does not support all EVM RPC endpoints.
+
+- Etherlink EVM calculates gas fees differently; see [Fee structure](/evm/developing/fees).
+
+- Etherlink EVM computes the state world hash with a different function than Ethereum uses.
+Therefore it is not compatible with EVM "light clients" that compute states in the way that Ethereum does, with the `Keccak-256` hash function.
+Therefore, Etherlink EVM is not compatible with EVM light-client implementations that use this hash function, such as Geth's light client and OpenEthereum.
+
+- Etherlink EVM computes block hashes in a custom way, not including every header field.
+Therefore, you cannot compute Etherlink EVM block hashes with tools such as Geth.
+
diff --git a/docs/building-on-etherlink/deploying-contracts.md b/docs/evm/developing/deploying-contracts.md
similarity index 75%
rename from docs/building-on-etherlink/deploying-contracts.md
rename to docs/evm/developing/deploying-contracts.md
index 054c683c..2d17ebe7 100644
--- a/docs/building-on-etherlink/deploying-contracts.md
+++ b/docs/evm/developing/deploying-contracts.md
@@ -6,38 +6,38 @@ dependencies:
import PublicRpcRateLimitNote from '@site/docs/conrefs/rate-limit.md';
-As an EVM-compatible chain, Etherlink runs Solidity contracts.
+As an EVM-compatible chain, Etherlink EVM runs Solidity contracts.
You can deploy Solidity smart contracts in any way that you would deploy them to an EVM-compatible chain.
:::note
-Etherlink supports Solidity versions up to and including 0.8.24.
+Etherlink EVM supports Solidity versions up to and including 0.8.24.
:::
-You can use any of the toolkits in [Development toolkits](/building-on-etherlink/development-toolkits) to deploy to Etherlink, as well as standard tools such as the [Remix Ethereum IDE](https://remix.ethereum.org/).
+You can use any of the toolkits in [Development toolkits](/evm/developing/development-toolkits) to deploy to Etherlink EVM, as well as standard tools such as the [Remix Ethereum IDE](https://remix.ethereum.org/).
-To call the contract after you deploy it, see [Sending transactions](/building-on-etherlink/transactions).
+To call the contract after you deploy it, see [Sending transactions](/evm/developing/transactions).
## Deploying with Remix
-The Remix online IDE lets you code, compile, and deploy contracts to EVM chains, including Etherlink
+The Remix online IDE lets you code, compile, and deploy contracts to EVM chains, including Etherlink EVM
-1. Connect your wallet to Etherlink Shadownet Testnet as described in [Using your wallet](/get-started/using-your-wallet).
+1. Connect your wallet to Etherlink Shadownet Testnet as described in [Using your wallet](/evm/get-started/using-your-wallet).
-1. Get some Etherlink tokens as described in [Getting Testnet tokens](/get-started/getting-testnet-tokens).
+1. Get some Etherlink EVM tokens as described in [Getting Testnet tokens](/evm/get-started/getting-testnet-tokens).
1. Open the Remix IDE at https://remix.ethereum.org.
1. In the **contracts** section of the IDE, create a contract.
-For example, you can create a contract named `4_HelloEtherlink.sol` and use this contract from the [Solidity by Example](https://solidity-by-example.org/hello-world/):
+For example, you can create a contract named `4_HelloTezosEVM.sol` and use this contract from the [Solidity by Example](https://solidity-by-example.org/hello-world/):
```solidity
// SPDX-License-Identifier: MIT
// compiler version must be greater than or equal to 0.8.24 and less than 0.9.0
pragma solidity ^0.8.24;
- contract HelloEtherlink {
- string public greet = "Hello Etherlink!";
+ contract HelloTezosEVM {
+ string public greet = "Hello Etherlink EVM!";
}
```
@@ -67,7 +67,7 @@ If you used the example contract above, you can call the `greet` entrypoint and
-Now the contract is deployed on Etherlink.
+Now the contract is deployed on Etherlink EVM.
You can look it up on the [Shadownet block explorer](https://shadownet.explorer.etherlink.com/).
## Deploying with ethers.js
diff --git a/docs/building-on-etherlink/development-toolkits.md b/docs/evm/developing/development-toolkits.md
similarity index 84%
rename from docs/building-on-etherlink/development-toolkits.md
rename to docs/evm/developing/development-toolkits.md
index 5f2c8451..a88f799d 100644
--- a/docs/building-on-etherlink/development-toolkits.md
+++ b/docs/evm/developing/development-toolkits.md
@@ -6,14 +6,14 @@ dependencies:
## 👷 Hardhat
-[Hardhat](https://hardhat.org/) is an Ethereum development environment for professionals. It facilitates performing frequent tasks, such as running tests, automatically checking code for mistakes or interacting with a smart contract. To get started, check out the [Hardhat documentation](https://hardhat.org/docs) or the [Etherlink tutorial](/tutorials/predictionMarket).
+[Hardhat](https://hardhat.org/) is an Ethereum development environment for professionals. It facilitates performing frequent tasks, such as running tests, automatically checking code for mistakes or interacting with a smart contract. To get started, check out the [Hardhat documentation](https://hardhat.org/docs) or the [prediction market tutorial](/tutorials/predictionMarket).
-### Using Hardhat with Etherlink
+### Using Hardhat with Etherlink EVM
-Hardhat works seamlessly with Etherlink.
-You can follow the documentation at https://hardhat.org/docs and insert values for Etherlink.
+Hardhat works seamlessly with Etherlink EVM.
+You can follow the documentation at https://hardhat.org/docs and insert values for Etherlink EVM.
-Here is an example `hardhat.config.js` file for Etherlink Mainnet and Shadownet Testnet:
+Here is an example `hardhat.config.js` file for Etherlink Mainnet and Shadownet Testnet:
```javascript
module.exports = {
@@ -74,7 +74,7 @@ Hardhat offers great guides for [deploying](https://hardhat.org/hardhat-runner/d
For the most up to date information on how to deploy and verify a smart contract, check out the [guide](https://book.getfoundry.sh/forge/deploying) provided by the Foundry team!
-As a summary, you can run the following command for Etherlink:
+As a summary, you can run the following command for Etherlink EVM:
```bash
forge create --rpc-url "https://node.mainnet.etherlink.com" \
@@ -84,4 +84,4 @@ forge create --rpc-url "https://node.mainnet.etherlink.com" \
src/YOUR_CONTRACT.sol:YOUR_CONTRACT --legacy
```
-To use Etherlink Shadownet Testnet, substitute the RPC URL `https://node.shadownet.etherlink.com` for the Mainnet URL.
+To use Etherlink Shadownet Testnet, substitute the RPC URL `https://node.shadownet.etherlink.com` for the Mainnet URL.
diff --git a/docs/building-on-etherlink/endpoint-support.md b/docs/evm/developing/endpoint-support.md
similarity index 87%
rename from docs/building-on-etherlink/endpoint-support.md
rename to docs/evm/developing/endpoint-support.md
index 50d76b65..75f48c76 100644
--- a/docs/building-on-etherlink/endpoint-support.md
+++ b/docs/evm/developing/endpoint-support.md
@@ -3,8 +3,8 @@ title: Ethereum endpoint support
hide_table_of_contents: true
---
-Etherlink nodes use [Geth](https://geth.ethereum.org/) to provide access to both standard Ethereum RPC endpoints and Geth-specific RPC endpoints.
-These tables list these endpoints and whether Etherlink supports them:
+EVM nodes use [Geth](https://geth.ethereum.org/) to provide access to both standard Ethereum RPC endpoints and Geth-specific RPC endpoints.
+These tables list these endpoints and whether Etherlink EVM supports them:
## Standard Ethereum endpoints
@@ -137,7 +137,7 @@ For information about these endpoints, see [JSON-RPC API](https://ethereum.org/e
`eth_accounts`
Yes
- This endpoint always returns an empty list because the Etherlink EVM node does not manage any addresses
+ This endpoint always returns an empty list because the EVM node does not manage any addresses
`eth_blobBaseFee`
@@ -152,7 +152,7 @@ For information about these endpoints, see [JSON-RPC API](https://ethereum.org/e
`eth_call`
Yes
- Etherlink nodes use the standard Ethereum version of the `eth_call` endpoint instead of the Geth version; see [Sending transactions](/building-on-etherlink/transactions)
+ EVM nodes use the standard Ethereum version of the `eth_call` endpoint instead of the Geth version; see [Sending transactions](/evm/developing/transactions)
`eth_chainId`
@@ -172,7 +172,7 @@ For information about these endpoints, see [JSON-RPC API](https://ethereum.org/e
`eth_estimateGas`
Yes
- See [Sending transactions](/building-on-etherlink/transactions)
+ See [Sending transactions](/evm/developing/transactions)
`eth_feeHistory`
@@ -197,7 +197,7 @@ For information about these endpoints, see [JSON-RPC API](https://ethereum.org/e
`eth_getBlockByNumber`
Yes
- Note that Etherlink uses a nonstandard way of computing block hashes, so you cannot use the header information from the `eth_getBlockByNumber` endpoint to compute the block hash.
+ Note that Etherlink EVM uses a nonstandard way of computing block hashes, so you cannot use the header information from the `eth_getBlockByNumber` endpoint to compute the block hash.
`eth_getBlockReceipts`
@@ -232,7 +232,7 @@ For information about these endpoints, see [JSON-RPC API](https://ethereum.org/e
`eth_getLogs`
Yes
- See [Getting event logs](/building-on-etherlink/transactions#getting-event-logs)
+ See [Getting event logs](/evm/developing/transactions#getting-event-logs)
`eth_getProof`
@@ -327,7 +327,7 @@ For information about these endpoints, see [JSON-RPC API](https://ethereum.org/e
`eth_sendRawTransaction`
Yes
- See [Sending transactions](/building-on-etherlink/transactions)
+ See [Sending transactions](/evm/developing/transactions)
`eth_sendTransaction`
@@ -347,7 +347,7 @@ For information about these endpoints, see [JSON-RPC API](https://ethereum.org/e
`eth_subscribe`
Experimental
- See Getting updates with WebSockets
+ See Getting updates with WebSockets
`eth_syncing`
@@ -389,7 +389,7 @@ For information about these endpoints, see [JSON-RPC API](https://ethereum.org/e
## Geth-specific endpoints
-This table shows the Geth endpoints that Etherlink nodes support.
+This table shows the Geth endpoints that EVM nodes support.
All other Geth endpoints are not supported.
For information about these endpoints, see the Geth documentation at https://geth.ethereum.org/docs.
@@ -415,7 +415,7 @@ For information about these endpoints, see the Geth documentation at https://get
`eth_call`
No
- Etherlink nodes use the standard Ethereum version of the `eth_call` endpoint instead of the Geth version; see [Sending transactions](/building-on-etherlink/transactions)
+ EVM nodes use the standard Ethereum version of the `eth_call` endpoint instead of the Geth version; see [Sending transactions](/evm/developing/transactions)
`txpool_content`
@@ -427,7 +427,7 @@ For information about these endpoints, see the Geth documentation at https://get
## ethers.js SDK methods
-The Etherlink EVM node supports these [ethers.js](https://docs.ethers.org/v6/) methods:
+The EVM node supports these [ethers.js](https://docs.ethers.org/v6/) methods:
@@ -466,7 +466,7 @@ The Etherlink EVM node supports these [ethers.js](https://docs.ethers.org/v6/) m
-For examples of using these ethers.js methods, see [Using ethers.js](/building-on-etherlink/information).
+For examples of using these ethers.js methods, see [Using ethers.js](/evm/developing/information).
## Additional information
@@ -488,7 +488,7 @@ For examples of using these ethers.js methods, see [Using ethers.js](/building-o
Fee Structure
- **Post London** (Fee market is not implemented yet, but the rollup supports EIP-1559 transaction types); see Fee structure
+ **Post London** (Fee market is not implemented yet, but the rollup supports EIP-1559 transaction types); see Fee structure
-
@@ -100,7 +99,7 @@ The wallet sends a new transaction with the increased fee.
Rabby wallet shows a spinning indicator with a number to indicate pending transactions.
In this picture, one transaction is shown as pending because it did not include enough transaction fees.
-Etherlink has dropped the transaction but the wallet has not updated its status yet:
+Etherlink has dropped the transaction but the wallet has not updated its status yet:
@@ -122,18 +121,18 @@ The wallet sends a new transaction with the increased fee.
## Checking gas prices
-As described in [Estimating fees](/building-on-etherlink/estimating-fees), the _gas price_ is the cost per unit of computation required by a transaction.
+As described in [Estimating fees](/evm/developing/estimating-fees), the _gas price_ is the cost per unit of computation required by a transaction.
The fee for a transaction depends on the gas price.
-The Etherlink gas price (and therefore the fee for a given transaction) varies based on the activity on the chain.
+The Etherlink EVM gas price (and therefore the fee for a given transaction) varies based on the activity on the chain.
The default gas price is 1 gwei, or 0.000000001 XTZ, but at times of high activity it can go higher.
-Here are some ways to get Etherlink's gas price:
+Here are some ways to get Etherlink EVM's gas price:
-- For an average of Etherlink gas prices, go to the [Gas tracker](https://explorer.etherlink.com/gas-tracker) page on the Etherlink block explorer.
+- For an average of Etherlink EVM gas prices, go to the [Gas tracker](https://explorer.etherlink.com/gas-tracker) page on the Etherlink EVM block explorer.
- For the actual gas price of the previous block, go to https://explorer.etherlink.com/blocks, click the most recent block, and check the `Base fee per gas` field.
-- Developers can use the standard EVM `eth_gasPrice` endpoint, as described in [Estimating fees](/building-on-etherlink/estimating-fees).
+- Developers can use the standard EVM `eth_gasPrice` endpoint, as described in [Estimating fees](/evm/developing/estimating-fees).
The actual cost of a transaction depends on the gas price and the complexity of the transaction.
Wallets show the estimated cost for a transaction before you approve the transaction.
diff --git a/docs/get-started/using-your-wallet.mdx b/docs/evm/get-started/using-your-wallet.mdx
similarity index 63%
rename from docs/get-started/using-your-wallet.mdx
rename to docs/evm/get-started/using-your-wallet.mdx
index d77cf94a..36469d52 100644
--- a/docs/get-started/using-your-wallet.mdx
+++ b/docs/evm/get-started/using-your-wallet.mdx
@@ -16,7 +16,7 @@ You can connect any wallet that supports custom EVM networks, including:
- [Temple wallet](https://www.templewallet.com)
- [Trust Wallet](https://trustwallet.com/)
-You can use these buttons to connect your wallet to Etherlink:
+You can use these buttons to connect your wallet to Etherlink EVM{/* TEVM */}:
diff --git a/docs/tools/exchanges.md b/docs/evm/tools/exchanges.md
similarity index 76%
rename from docs/tools/exchanges.md
rename to docs/evm/tools/exchanges.md
index 4d178b7c..262d3e1a 100644
--- a/docs/tools/exchanges.md
+++ b/docs/evm/tools/exchanges.md
@@ -22,7 +22,7 @@ These decentralized exchanges allow users and dApps to trade XTZ with other cryp
:::note
-On exchanges, be sure that you are getting Etherlink XTZ and not Tezos layer 1 XTZ or wrapped XTZ (WXTZ) on another platform.
-If you have XTZ on a different platform, you can bridge it to Etherlink XTZ as described in [Bridging](/bridging)
+On exchanges, be sure that you are getting Etherlink EVM XTZ and not Tezos layer 1 XTZ or wrapped XTZ (WXTZ) on another platform.
+If you have XTZ on a different platform, you can bridge it to Etherlink EVM XTZ as described in [Bridging](/evm/bridging/)
:::
diff --git a/docs/tools/game-development.md b/docs/evm/tools/game-development.md
similarity index 71%
rename from docs/tools/game-development.md
rename to docs/evm/tools/game-development.md
index 5fa4312f..4875cadd 100644
--- a/docs/tools/game-development.md
+++ b/docs/evm/tools/game-development.md
@@ -4,19 +4,19 @@ title: Game development
## Tezos Unity SDK
-The [Tezos Unity SDK](https://docs.tezos.com/unity) provides tools that lets you access Etherlink in games and other Unity applications.
+The [Tezos Unity SDK](https://docs.tezos.com/unity) provides tools that lets you access Etherlink EVM in games and other Unity applications.
You can use the SDK to:
- Use a player's account as their account for a game and their wallet as their way of logging in to the game
- Accept payments from players in XTZ
-- Use Etherlink to create game assets, store player inventories, and transfer assets between players
+- Use Etherlink EVM to create game assets, store player inventories, and transfer assets between players
- Verify that users own specific game assets and allow them to transfer them to other players
- Use smart contracts as backend logic for games
The SDK supports wallets that connect via the WalletConnect protocol, including MetaMask.
-It can call Etherlink contracts and initiate transfers of XTZ on Etherlink.
+It can call Etherlink EVM contracts and initiate transfers of XTZ on Etherlink EVM.
-Using Etherlink in a Unity application requires version 4.0.0 of the Tezos Unity SDK or later.
+Using Etherlink EVM in a Unity application requires version 4.0.0 of the Tezos Unity SDK or later.
For more information, see the documentation for the [Tezos Unity SDK](https://docs.tezos.com/unity).
## Sequence
@@ -24,7 +24,7 @@ For more information, see the documentation for the [Tezos Unity SDK](https://do
[Sequence](https://sequence.xyz) is a comprehensive web3 integration platform for game developers that simplifies blockchain implementation with plug-and-play tools.
Sequence offers:
-- Support for Etherlink Mainnet and Shadownet Testnet
+- Support for Etherlink Mainnet and Shadownet Testnet
- Full-stack development support across frontend, backend, and on-chain
- SDK integration for Unity, Unreal, and mobile
- Payment solutions with fiat-crypto onramps and NFT checkout
diff --git a/docs/tools/institutions.md b/docs/evm/tools/institutions.md
similarity index 99%
rename from docs/tools/institutions.md
rename to docs/evm/tools/institutions.md
index 14c3285c..9fa328b0 100644
--- a/docs/tools/institutions.md
+++ b/docs/evm/tools/institutions.md
@@ -11,4 +11,3 @@ title: Institutional tools
- On-chain payments
Find out more about these services [here](https://www.fireblocks.com/pricing/).
-
diff --git a/docs/tools/node-providers.md b/docs/evm/tools/node-providers.md
similarity index 86%
rename from docs/tools/node-providers.md
rename to docs/evm/tools/node-providers.md
index 9105e307..54248b0e 100644
--- a/docs/tools/node-providers.md
+++ b/docs/evm/tools/node-providers.md
@@ -4,7 +4,7 @@ title: Node providers
## Public RPC
-The public RPC nodes at `node.mainnet.etherlink.com` and `https://node.shadownet.etherlink.com` are intended for use within user wallets such as MetaMask and for dApps wanting to test out API access to Etherlink within the rate limits listed below.
+The public RPC nodes at `node.mainnet.etherlink.com` and `https://node.shadownet.etherlink.com` are intended for use within user wallets such as MetaMask and for dApps wanting to test out API access to Etherlink EVM within the rate limits listed below.
For higher limits you must [run your own node](/network/evm-nodes) or subscribe to an API plan offered by a commercial RPC node provider.
### Current restrictions
@@ -34,7 +34,7 @@ These restrictions are kept under frequent review and may be updated without not
## Commercial RPC Providers
-If you don't want to deploy and manage your own Etherlink RPC node, or if you require features or rate limits higher than the public nodes, these companies offer a wide range of free and paid plans:
+If you don't want to deploy and manage your own EVM node, or if you require features or rate limits higher than the public nodes, these companies offer a wide range of free and paid plans:
- Ankr: See https://www.ankr.com/web3-api/chains-list/etherlink/
- BlockPI: See https://blockpi.io/chain/etherlink
diff --git a/docs/evm/tools/onramps.md b/docs/evm/tools/onramps.md
new file mode 100644
index 00000000..5a5e707a
--- /dev/null
+++ b/docs/evm/tools/onramps.md
@@ -0,0 +1,16 @@
+---
+title: On-ramps/off-ramps
+---
+
+On-ramps and off-ramps convert fiat currency to Etherlink EVM tokens and back, which allows your users to use cryptocurrency on your site as seamlessly as they use fiat currency on traditional finance sites.
+On-ramps and off-ramps can integrate with your application to allow it to:
+
+- Use Etherlink EVM as a payment method and financial backend
+- Receive payments in Etherlink EVM without requiring users to buy cryptocurrency manually
+- Make it easier to bridge and swap cryptocurrency tokens
+
+Some on-ramps and off-ramps also allow users to conduct transactions with their wallets directly, without using a specific dApp.
+
+These on-ramps/off-ramps support Etherlink EVM:
+
+- [Transak](https://transak.com)
diff --git a/docs/tools/price-feeds.md b/docs/evm/tools/price-feeds.md
similarity index 90%
rename from docs/tools/price-feeds.md
rename to docs/evm/tools/price-feeds.md
index ebfcf321..65b47635 100644
--- a/docs/tools/price-feeds.md
+++ b/docs/evm/tools/price-feeds.md
@@ -6,7 +6,7 @@ dependencies:
## Pyth
-[Pyth](https://pyth.network/) offers 400+ pull-based price feeds for Etherlink.
+[Pyth](https://pyth.network/) offers 400+ pull-based price feeds for Etherlink EVM.
Learn more about integrating Pyth with their documentation on [How to Use Real-Time Price Data](https://docs.pyth.network/price-feeds/use-real-time-data).
This example contract accepts price update data from Pyth and uses it to provide the price of one XTZ in USD:
@@ -39,9 +39,9 @@ contract PythSimple {
}
```
-To deploy this contract you need the address of the Pyth on-chain application on Etherlink (`0x2880aB155794e7179c9eE2e38200202908C17B43` on Mainnet and Shadownet Testnet) and the ID of the XTZ/USD price feed (`0x0affd4b8ad136a21d79bc82450a325ee12ff55a235abc242666e423b8bcffd03` as listed on the Pyth [Price feed IDs](https://legacy.pyth.network/developers/price-feed-ids)).
+To deploy this contract you need the address of the Pyth on-chain application on Etherlink EVM (`0x2880aB155794e7179c9eE2e38200202908C17B43` on Mainnet and Shadownet Testnet) and the ID of the XTZ/USD price feed (`0x0affd4b8ad136a21d79bc82450a325ee12ff55a235abc242666e423b8bcffd03` as listed on the Pyth [Price feed IDs](https://legacy.pyth.network/developers/price-feed-ids)).
-Here is an example JavaScript application that uses the [`viem`](https://viem.sh/) SDK to call the contract on Etherlink:
+Here is an example JavaScript application that uses the [`viem`](https://viem.sh/) SDK to call the contract on Etherlink EVM:
```javascript
import { createWalletClient, http, getContract } from "viem";
@@ -132,7 +132,7 @@ Pyth also provides prices on Shadownet Testnet but the price does not change.
## RedStone
-[RedStone](https://redstone.finance/) offers push-based price feeds for Etherlink.
+[RedStone](https://redstone.finance/) offers push-based price feeds for Etherlink EVM.
Get started with their [docs](https://docs.redstone.finance/docs/introduction) to learn more.
The example in [`etherlinkcom/infra-instruments`](https://github.com/etherlinkcom/infra-instruments/tree/main) includes a contract that retrieves pricing data from RedStone for multiple assets.
@@ -187,17 +187,17 @@ contract RedStoneSimple {
To deploy this contract you need the address of the RedStone contract that provides the XTZ/USD price feed:
-- `0xe92c00BC72dD12e26E61212c04E8D93aa09624F2` on Etherlink Mainnet
-- `0xb9D0073aCb296719C26a8BF156e4b599174fe1d5` on Etherlink Shadownet Testnet
+- `0xe92c00BC72dD12e26E61212c04E8D93aa09624F2` on Etherlink Mainnet
+- `0xb9D0073aCb296719C26a8BF156e4b599174fe1d5` on Etherlink Shadownet Testnet
Similarly, you can get the price of the URANIUM token in USD with these addresses:
-- `0xb81131B6368b3F0a83af09dB4E39Ac23DA96C2Db` on Etherlink Mainnet
-- `0xED2B1ca5D7E246f615c2291De309643D41FeC97e` on Etherlink Shadownet Testnet
+- `0xb81131B6368b3F0a83af09dB4E39Ac23DA96C2Db` on Etherlink Mainnet
+- `0xED2B1ca5D7E246f615c2291De309643D41FeC97e` on Etherlink Shadownet Testnet
For more price feed information, see the [RedStone documentation](https://app.redstone.finance/app/feeds/?networks=127823,128123,42793&page=1&sortBy=feed&sortDesc=false&perPage=32).
-Here is an example JavaScript application that uses the [`viem`](https://viem.sh/) SDK to call the contract on Etherlink:
+Here is an example JavaScript application that uses the [`viem`](https://viem.sh/) SDK to call the contract on Etherlink EVM:
```javascript
import { createWalletClient, http, getContract } from "viem";
@@ -342,10 +342,10 @@ contract AcurastSimple {
```
-To deploy this contract you need the address of the Acelon proxy on Etherlink (`0x4Bf5C46Ee59a1110c2a242715f9c3b548A14ee02` on Mainnet).
-Acelon is not available on Etherlink testnets.
+To deploy this contract you need the address of the Acelon proxy on Etherlink EVM (`0x4Bf5C46Ee59a1110c2a242715f9c3b548A14ee02` on Mainnet).
+Acelon is not available on Etherlink testnets.
-Here is an example JavaScript application that uses the [`viem`](https://viem.sh/) SDK to get the price of stXTZ on Etherlink:
+Here is an example JavaScript application that uses the [`viem`](https://viem.sh/) SDK to get the price of stXTZ on Etherlink EVM:
```javascript
import { createWalletClient, http, getContract } from "viem";
@@ -437,4 +437,4 @@ callContract();
```
-You can also use the NPM package `@acelon/acelon-sdk` for the same purpose.
\ No newline at end of file
+You can also use the NPM package `@acelon/acelon-sdk` for the same purpose.
diff --git a/docs/tools/vrf.md b/docs/evm/tools/vrf.md
similarity index 63%
rename from docs/tools/vrf.md
rename to docs/evm/tools/vrf.md
index 732fdedc..7e47da66 100644
--- a/docs/tools/vrf.md
+++ b/docs/evm/tools/vrf.md
@@ -3,10 +3,12 @@ title: Verifiable random functions
---
:::note
-