GenLayer Chain Integration

GenLayer Chain integration

GenLayer Chain is an EVM-compatible Arbitrum Orbit L2 that settles to Ethereum. GEN is its native gas token. It hosts ordinary Solidity contracts and the consensus contracts that coordinate Intelligent Contract execution. GenVM is a separate execution environment operated by nodes; it is not an EVM precompile or an Ethereum rollup execution engine.

What lives on GenLayer Chain

The chain provides ordering, availability, and an authoritative state machine for consensus. Its contracts record:

  • Intelligent Contract transactions and per-contract queues;
  • activator, leader, and committee assignments;
  • proposal, commit, reveal, decision, and appeal state;
  • validator staking, fees, and penalties; and
  • Ghost contracts that connect EVM accounts to Intelligent Contracts.

Because consensus actions are chain transactions, validators do not need a separate peer-to-peer network to agree on an Intelligent Contract result. Chain time and state determine whether a phase is open or a participant is idle.

What lives in GenVM

Intelligent Contract code and state execute in GenVM. Nodes reconstruct the accepted Intelligent Contract state by following GenLayer Chain events and replaying the corresponding state transitions. The consensus contracts store commitments and lifecycle data; they do not execute Python contract logic.

Ghost contracts bridge the environments

Every Intelligent Contract has a Ghost contract on GenLayer Chain at the same address. A Ghost:

  • receives EVM transactions addressed to the Intelligent Contract;
  • holds its native GEN balance on the EVM side;
  • forwards Intelligent Contract calls to the consensus system; and
  • delivers on-acceptance and on-finalization messages to EVM recipients.

The shared address gives wallets and EVM contracts one destination even though execution and balances span two environments. See accounts and addresses and messages.

Settlement and protocol finality are different

GenLayer Chain settles to Ethereum the way Arbitrum Orbit chains do. Its sequencer orders transactions. Its state is asserted on its parent chain without a validity proof: an assertion can be disputed during the chain's challenge period and is confirmed only after that period ends. A message from GenLayer Chain to Ethereum, such as a GEN withdrawal or an inflation request, can be executed through the canonical Outbox contract only after the assertion that contains it is confirmed. A sequencer receipt or an L2 event alone does not authorize an action on Ethereum.

On Testnet Bradbury, the parent chain is Ethereum Sepolia and the chain runs in AnyTrust mode: a data availability committee stores transaction data, and the parent chain records the committee's certificates. See Networks for each network's endpoints.

Separately, an Intelligent Contract transaction reaches protocol finality only after its consensus decision and appeal window complete. Applications must use the Intelligent Contract transaction status—not only the enclosing EVM transaction receipt—to determine whether an outcome is final.