kirilaa · Oct 12, 2026 · Oct 12, 2026 · Oct 12, 2026 · Oct 12, 2026 · Oct 12, 2026
diff --git a/content/api-references/genlayer-node/content.mdx b/content/api-references/genlayer-node/content.mdx
@@ -24,7 +24,7 @@ ${debugMethods.join('\n\n')}
 
 ## Ethereum Compatibility
 
-The GenLayer Node also supports Ethereum-compatible methods that are proxied to the underlying infrastructure. These methods follow the standard [Ethereum JSON-RPC specification](https://ethereum.org/en/developers/docs/apis/json-rpc/) and are prefixed with `eth_`.
+The GenLayer Node also supports Ethereum-compatible methods that are proxied to the underlying GenLayer Chain, an Arbitrum Orbit chain. These methods follow the standard [Ethereum JSON-RPC specification](https://ethereum.org/en/developers/docs/apis/json-rpc/) and are prefixed with `eth_`.
 
 **Examples of supported Ethereum methods:**
 
@@ -34,12 +34,6 @@ The GenLayer Node also supports Ethereum-compatible methods that are proxied to
 - `eth_call`
 - And other standard Ethereum JSON-RPC methods
 
-## zkSync Compatibility
-
-[zkSync-compatible](https://docs.zksync.io/zksync-protocol/api/zks-rpc) methods are also supported and proxied to the underlying infrastructure. These methods are prefixed with `zks_`.
-
-The default `config.yaml` turns the `zksync` group off (`node.rpc.endpoints.zksync.enabled: false`). Set it to `true` to forward `zks_*` calls.
-
 ## Usage Examples
 
 ### cURL

diff --git a/pages/FAQ.mdx b/pages/FAQ.mdx
@@ -8,7 +8,7 @@ description: "Frequently asked questions about GenLayer: Intelligent Contracts,
 <details>
   <summary>What is GenLayer?</summary>
 
-  GenLayer is the **adjudication layer for the agentic economy**. It uses decentralized AI-validator consensus to resolve contracts that require judgment, not just code. It's built as an L2 on zkSync Elastic Chain, anchoring to Ethereum's security. Contracts on GenLayer — called **Intelligent Contracts** — can interpret language, process images, fetch live web data, and reach consensus on contested or subjective outcomes. See [What is GenLayer](/understand-genlayer-protocol/what-is-genlayer).
+  GenLayer is the **adjudication layer for the agentic economy**. It uses decentralized AI-validator consensus to resolve contracts that require judgment, not just code. It runs on GenLayer Chain, an Arbitrum Orbit L2 that settles to Ethereum and uses GEN as its native gas token. Contracts on GenLayer — called **Intelligent Contracts** — can interpret language, process images, fetch live web data, and reach consensus on contested or subjective outcomes. See [What is GenLayer](/understand-genlayer-protocol/what-is-genlayer).
 </details>
 
 <details>
@@ -99,7 +99,7 @@ description: "Frequently asked questions about GenLayer: Intelligent Contracts,
   - Token holders delegate stake to validators, incentivizing honest behavior
   - Multiple validators independently verify each transaction
   - Appeals provide a failsafe — dishonest validators get slashed
-  - The system anchors to Ethereum via zkSync for finality
+  - GenLayer Chain is an Arbitrum Orbit rollup that settles to Ethereum
 </details>
 
 <details>

diff --git a/pages/api-references/genlayer-node.mdx b/pages/api-references/genlayer-node.mdx
@@ -1647,7 +1647,7 @@ Retrieves the full execution trace for a transaction, including the return data,
 
 ## Ethereum Compatibility
 
-The GenLayer Node also supports Ethereum-compatible methods that are proxied to the underlying infrastructure. These methods follow the standard [Ethereum JSON-RPC specification](https://ethereum.org/en/developers/docs/apis/json-rpc/) and are prefixed with `eth_`.
+The GenLayer Node also supports Ethereum-compatible methods that are proxied to the underlying GenLayer Chain, an Arbitrum Orbit chain. These methods follow the standard [Ethereum JSON-RPC specification](https://ethereum.org/en/developers/docs/apis/json-rpc/) and are prefixed with `eth_`.
 
 **Examples of supported Ethereum methods:**
 
@@ -1657,12 +1657,6 @@ The GenLayer Node also supports Ethereum-compatible methods that are proxied to
 - `eth_call`
 - And other standard Ethereum JSON-RPC methods
 
-## zkSync Compatibility
-
-[zkSync-compatible](https://docs.zksync.io/zksync-protocol/api/zks-rpc) methods are also supported and proxied to the underlying infrastructure. These methods are prefixed with `zks_`.
-
-The default `config.yaml` turns the `zksync` group off (`node.rpc.endpoints.zksync.enabled: false`). Set it to `true` to forward `zks_*` calls.
-
 ## Usage Examples
 
 ### cURL

diff --git a/pages/developers/networks.mdx b/pages/developers/networks.mdx
@@ -7,7 +7,7 @@ import AddToWallet from '../../components/AddToWallet'
 
 # Networks
 
-GenLayer operates as two layers: the **GenLayer RPC** handles intelligent contract operations (`gen_*` methods), while the **GenLayer Chain** is the underlying Arbitrum Orbit L2 that handles standard Ethereum operations (`eth_*` methods). The GenLayer RPC also passes through supported `eth_*` calls to the underlying chain, so you can use either endpoint for standard wallet operations.
+GenLayer operates as two layers: the **GenLayer RPC** handles intelligent contract operations (`gen_*` methods), while the **GenLayer Chain** is the underlying Arbitrum Orbit L2—settling to Ethereum, with GEN as its native gas token—that handles standard Ethereum operations (`eth_*` methods). The GenLayer RPC also passes through supported `eth_*` calls to the underlying chain, so you can use either endpoint for standard wallet operations. See [GenLayer Chain integration](/understand-genlayer-protocol/core-concepts/rollup-integration) for how the chain, bridge, and settlement work.
 
 For the full RPC reference, see [GenLayer Node API](/api-references/genlayer-node).
 
@@ -94,7 +94,7 @@ Local development with full control. Requires [GenLayer Studio](/developers/inte
 
 ## GenLayer Chain (L2)
 
-The underlying Arbitrum Orbit L2 for Bradbury Phase 2. You typically don't need to interact with this directly — the GenLayer RPC passes through supported `eth_*` calls. But if you need direct L2 access (e.g., token transfers, contract debugging at the EVM level), you can add this chain to your wallet.
+The underlying Arbitrum Orbit L2 for Bradbury Phase 2. GEN is its native currency, so balances and gas are in GEN. You typically don't need to interact with this directly — the GenLayer RPC passes through supported `eth_*` calls. But if you need direct L2 access (e.g., token transfers, contract debugging at the EVM level), you can add this chain to your wallet.
 
 | Setting | Value |
 |:--|:--|