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: 3 additions & 3 deletions .github/scripts/sanitize-config.sh
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,9 @@ echo "Sanitizing config file: $CONFIG_FILE"
# Use yq to:
# Replace RPC URLs / provider with TODO placeholders
yq -i '
.rollup.genlayerchainrpcurl = "TODO: Set your GenLayer Chain ZKSync HTTP RPC URL here" |
.rollup.genlayerchainwebsocketurl = "TODO: Set your GenLayer Chain ZKSync WebSocket RPC URL here" |
.rollup.provider = "TODO: Set your GenLayer Chain ZKSync provider"
.rollup.genlayerchainrpcurl = "TODO: Set your GenLayer Chain HTTP RPC URL here" |
.rollup.genlayerchainwebsocketurl = "TODO: Set your GenLayer Chain WebSocket RPC URL here" |
.rollup.provider = "TODO: Set your GenLayer Chain RPC provider"
' "$CONFIG_FILE"

echo "Config sanitization completed"
6 changes: 1 addition & 5 deletions content/api-references/genlayer-node/content.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,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 @@ -24,10 +24,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 `zksync_`.

## Usage Examples

### cURL
Expand Down
6 changes: 3 additions & 3 deletions content/validators/config.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# rollup configuration
rollup:
genlayerchainrpcurl: "TODO: Set your GenLayer Chain ZKSync HTTP RPC URL here" # GenLayer Chain RPC URL
genlayerchainwebsocketurl: "TODO: Set your GenLayer Chain ZKSync WebSocket RPC URL here" # GenLayer Chain WebSocket URL
provider: "TODO: Set your GenLayer Chain ZKSync provider" # Rollup operator name; surfaces as the "provider" label on RPC-driven metrics. Set explicitly per deployment.
genlayerchainrpcurl: "TODO: Set your GenLayer Chain HTTP RPC URL here" # GenLayer Chain RPC URL
genlayerchainwebsocketurl: "TODO: Set your GenLayer Chain WebSocket RPC URL here" # GenLayer Chain WebSocket URL
provider: "TODO: Set your GenLayer Chain RPC provider" # Rollup operator name; surfaces as the "provider" label on RPC-driven metrics. Set explicitly per deployment.
# consensus contracts configuration
consensus:
# Testnet - Phase 5
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: 1 addition & 5 deletions pages/api-references/genlayer-node.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1084,7 +1084,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 @@ -1094,10 +1094,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 `zksync_`.

## Usage Examples

### cURL
Expand Down
8 changes: 6 additions & 2 deletions pages/developers/networks.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,11 @@ 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 L2 (zkSync Elastic Chain) that handles standard Ethereum operations (`eth_*` methods). The GenLayer RPC also passes through all `eth_*` and `zks_*` 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 L2—an Arbitrum Orbit chain that settles to Ethereum and uses GEN as its native gas token—that handles standard Ethereum operations (`eth_*` methods). The GenLayer RPC also passes through all `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.

<Callout type="info">
GenLayer Chain runs on Arbitrum Orbit from consensus v0.6. Testnet Asimov and Bradbury keep the endpoints and chain ID listed below until they upgrade to v0.6; this page will list the new endpoints and contract addresses when they move.
</Callout>

For the full RPC reference, see [GenLayer Node API](/api-references/genlayer-node).

Expand Down Expand Up @@ -104,7 +108,7 @@ Local development with full control. Requires [GenLayer Studio](/developers/inte

## GenLayer Chain (L2)

The underlying zkSync Elastic Chain that GenLayer runs on. You typically don't need to interact with this directly — the GenLayer RPC passes through all `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 chain that GenLayer runs on. From consensus v0.6 it is an Arbitrum Orbit chain; the endpoint below is the pre-v0.6 testnet chain that Asimov and Bradbury use until they upgrade. 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 all `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