Skip to content
Open
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
6 changes: 2 additions & 4 deletions content/api-references/genlayer-node/content.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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:**

Expand All @@ -36,9 +36,7 @@ The GenLayer Node also supports Ethereum-compatible methods that are proxied to

## 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.
The node can forward `zks_*` methods to an upstream that supports the [zkSync JSON-RPC API](https://docs.zksync.io/zksync-protocol/api/zks-rpc). Set `node.rpc.endpoints.zksync.enabled` to `true` to enable forwarding for a compatible upstream. Keep the default value of `false` on Bradbury Phase 2, which runs on Arbitrum Orbit.

## Usage Examples

Expand Down
4 changes: 2 additions & 2 deletions pages/FAQ.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand Down Expand Up @@ -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>
Expand Down
6 changes: 2 additions & 4 deletions pages/api-references/genlayer-node.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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:**

Expand All @@ -1659,9 +1659,7 @@ The GenLayer Node also supports Ethereum-compatible methods that are proxied to

## 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.
The node can forward `zks_*` methods to an upstream that supports the [zkSync JSON-RPC API](https://docs.zksync.io/zksync-protocol/api/zks-rpc). Set `node.rpc.endpoints.zksync.enabled` to `true` to enable forwarding for a compatible upstream. Keep the default value of `false` on Bradbury Phase 2, which runs on Arbitrum Orbit.

## Usage Examples

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Fee-charging writes carry an explicit policy for consensus time units, execution
### Consensus Layer
The consensus layer implements GenLayer's Optimistic Democracy mechanism to ensure reliable and secure execution of transactions using a validator-driven commit-reveal scheme. It also handles appeals and transaction finality to maintain integrity and fairness.

It is built on ZK-stack rollups to provide scalability and cost-efficiency, secure state updates, and anchoring to Ethereum's security model.
The consensus contracts run on [GenLayer Chain](/understand-genlayer-protocol/core-concepts/rollup-integration), an Arbitrum Orbit L2 that settles to Ethereum and uses GEN as its native gas token.

### Execution Environment
The execution environment (the GenVM) is the engine that executes Intelligent Contracts. It supports both deterministic and non-deterministic operations, enabling AI integration and web data access.
Expand Down
4 changes: 2 additions & 2 deletions pages/developers/networks.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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).

Expand Down Expand Up @@ -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 |
|:--|:--|
Expand Down
Loading
Loading