Exchange & Wallet Integration

Exchange & Wallet Integrator Guide

This guide is for teams onboarding GenLayer into existing infrastructure — exchanges listing GEN, wallets adding the network, and indexers or custodians tracking balances and transfers. It orients you to the chain model, the endpoints and formats you'll integrate against, and the finality considerations that matter for crediting deposits.

⚠️

This page points at the canonical sources for concrete values rather than duplicating them. Network IDs, RPC endpoints, and contract addresses change per network and over time. Always read the live values from the Networks page and the validator Setup Guide before wiring anything up, and re-verify after network upgrades.

Chain model

GenLayer presents as two layers, and which one you integrate against depends on what you're doing:

  • GenLayer node RPC handles Intelligent Contract operations (gen_*) and forwards supported Ethereum (eth_*) calls to the chain. Use a Phase 2-compatible node for Intelligent Contract operations on Bradbury.
  • GenLayer Chain (L2) is the EVM-compatible Arbitrum Orbit chain that holds account balances and processes native GEN transfers. Connect to the chain RPC to index those transfers.

Bradbury Phase 2 settles to Ethereum Sepolia and uses AnyTrust for data availability. An AnyTrust certificate attests to batch data availability. Withdrawal eligibility depends on confirmation of the rollup assertion on the parent chain.

Use the GenLayer Node API to check which eth_* methods the node forwards. The optional zks_* compatibility proxy defaults to off on Bradbury Phase 2. Use standard Ethereum methods for Orbit integrations.


Endpoints, chain IDs, and currency

Read the exact values from the Networks page — do not hardcode them from this guide. For quick orientation, GenLayer exposes distinct environments, each with its own chain ID and RPC:

  • Testnet Bradbury Phase 2 — Networks lists the chain RPC, chain ID and explorer. The chain RPC serves EVM requests. Intelligent Contract methods require a GenLayer node RPC.
  • Studionet (hosted dev) and Localnet (local dev) — separate chain IDs, useful for staging your integration before pointing at a testnet.
  • GenLayer Chain (L2) — the underlying chain you'll index for balances/transfers; its RPC, chain ID, currency (GEN, 18 decimals), and chain explorer are in the GenLayer Chain (L2) section, which also provides an "add to wallet" control that emits the correct hex chain ID and native-currency metadata.

WebSocket access. Bradbury’s chain WebSocket requires a Conduit RPC key. Follow the configuration instructions on Networks before enabling subscriptions.

⚠️

Verify the deployment before crediting deposits. Bradbury Phase 2 reuses chain ID 4221. Check the block-zero hash and AddressManager against Networks when onboarding or switching RPC providers.


Addresses

GenLayer uses Ethereum-style accounts: addresses are 0x-prefixed hexadecimal strings, and the account model has Externally Owned Accounts (controlled by private keys) and Contract Accounts (Intelligent Contracts). Standard Ethereum address handling — hex parsing, checksumming, key management — applies. See Accounts and Addressing for the account model.

Same address across both layers. An Intelligent Contract's GEN balance is held by its "ghost contract" on the chain layer at the same address, so a given address refers to the same account whether you view it via the GenLayer RPC or directly on the GenLayer Chain. This simplifies balance tracking — you index one address space.


The GEN token

GEN is the native token of the GenLayer Chain (analogous to ETH on Ethereum), not an ERC-20 on that chain. Balances are denominated in wei (1 GEN = 10¹⁸ wei), and you read a balance with standard eth_getBalance against the chain RPC.

⚠️

On the Ethereum parent chain, GEN is an ERC-20. Track that token’s events on L1 and native GEN balances on L2. Verify the L1 token and bridge addresses against the deployment’s official information. See Bridging GEN.


Deposit detection

For crediting user deposits of native GEN on the GenLayer Chain, the pattern mirrors any EVM chain:

  1. Assign and monitor deposit addresses in the standard 0x hex format. For direct native transfers, identify the customer by the destination address.
  2. Follow new blocks via the chain RPC (HTTP polling eth_blockNumber / eth_getBlockByNumber, or WebSocket subscriptions if available for your network).
  3. Verify each deposit. For direct native transfers, match the recipient and value and check that the receipt succeeded in the canonical block. If you also accept transfers made by contracts, use a trace-capable provider to identify successful internal value transfers. eth_getBalance gives the current balance, not a history of deposits.
  4. Wait for finality before crediting (see below) — don't credit on first inclusion.

Full-block decoders must support Nitro system transactions, including type 0x6a. If you only need hashes, request eth_getBlockByNumber with its second argument set to false. Fetch the relevant transaction and its receipt individually to verify the recipient, value and success before crediting it.


Finality guidance

Choose the crediting threshold for each operation and record which signal the indexer requires.

  • Sequencer inclusion. A successful L2 receipt records execution. Indexers can record a pending deposit at this point and track the containing block.
  • Ethereum settlement. For a policy that requires a confirmed L2 state, wait for confirmation of the rollup assertion covering the transfer after the challenge period. Posting a batch or an AnyTrust certificate is an earlier event.
  • Intelligent Contract finality. For a credit that depends on an Intelligent Contract outcome, check the GenLayer transaction status. The Finality Window allows appeals before the result becomes final.
⚠️

Confirmation and challenge periods are deployment-specific. Use the parent-chain assertion status when your policy requires settlement. A fixed count of L2 blocks or elapsed minutes cannot establish that status.

For a canonical withdrawal, show the L2 submission, the wait for assertion confirmation and the successful L1 Outbox claim as separate stages. See Bridging GEN.


Integration checklist

  • Pull chain IDs, RPC (HTTP + WS), currency, and explorer URLs from the Networks page for each environment you support.
  • Verify the Bradbury Phase 2 genesis hash and AddressManager alongside the chain ID.
  • Verify the L1 token and canonical bridge for each deployment. For Bradbury Phase 2, use the bridge and Sepolia GEN links.
  • Track native GEN via eth_getBalance and native transfers (not ERC-20 logs) on the GenLayer Chain.
  • Specify whether each credit requires sequencer inclusion, a confirmed assertion or a finalized Intelligent Contract result.
  • Check the supported eth_* methods and test full-block decoding against a block containing a Nitro system transaction.
  • Re-validate all endpoints and addresses after every network upgrade.

Related resources