Developer reference

Build with
clear boundaries.

Explore L7X's public read APIs, network identity and current capabilities. Start with observed state before building a wallet or application.

Explore the read API ↓Check network status ↗

01 / Network identity

A new home. The same network identity.

Native network

layer7:mainnet

L7C is a peer L1 asset on L7X. Network identity, wallet addresses and the current epoch are preserved by the website move.

EVM compatibility identity

717 · 0x2cd

The endpoint exposes identity discovery. EVM contract calls, Ethereum transaction execution and native cross-chain swaps are not implemented.

Receipt sequence

Centralized sequencer

PostgreSQL records committed receipts. Height is a receipt sequence, rather than evidence of validator consensus or circulating supply.

02 / Public JSON-RPC

Discover. Read. Verify the scope.

Use rpc.l7x.network for GET identity discovery. JSON-RPC requests are accepted with POST at both / and /rpc.

curl https://rpc.l7x.network/rpc \
  --header 'Content-Type: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Expected identity: 0x2cd. This response does not confirm EVM execution support.

Selected implemented read methods
Method	Purpose
`eth_chainId`	EVM identity, hexadecimal Chain ID 717.
`net_version`	EVM identity, decimal network ID.
`web3_clientVersion`	Runtime version identification.
`l7_status`	Service and ledger read readiness.
`l7_getHead`	Committed receipt sequence head.
`l7_getTransactionByHash`	Receipt lookup; pass the hash as the first parameter.
`l7_getEcosystem`	Architecture catalog and implementation capabilities.

These examples read public data. Service write methods require separate server authorization and are outside this guide. Never place a service credential in a browser.

03 / HTTP read API

Start with the public record.

These routes are served by the existing runtime. The links below use the public RPC host. Handle HTTP failures and unavailable fields explicitly; a missing response is not an empty ledger.

Public HTTP reads
Request	What it reports
`GET /health`Open ↗	Service and ledger read readiness; PostgreSQL and Redis observations.
`GET /seq`Open ↗	Current committed receipt sequence head.
`GET /txs?limit=20`Open ↗	Recent committed receipts.
`GET /tx/:hash`	One receipt by its hash; replace :hash with a receipt hash.
`GET /v1/explorer/seals`Open ↗	Explorer search and pagination read API.
`GET /v1/ecosystem`Open ↗	Peer L1s, application layers, rail catalog and implementation capabilities.
`GET /v1/genesis/readiness`Open ↗	Native issuance gates and locked-genesis phase.
`GET /v1/hlp/readiness`Open ↗	HLP implementation gates; catalog membership does not enable settlement.
`GET /v1/hlp/observations`Open ↗	Cached provider observations, source timestamps and explicit unavailable states.

04 / Wallet continuity

Your wallet keeps its secure origin.

L7X Wallet continues at l7c.ai/wallet/v2 so encrypted browser wallets and installed Latch capsule approvals keep working. Old RPC aliases remain compatible. There is no automatic cross-domain vault migration.

Genesis still requires its dedicated owner approval and execution checks. HLP-4 catalogs 21 rails with 0 live settlement rails; provider observations do not activate them.