Developer Hub

AERE is a live EVM Layer 1. If you can deploy Solidity to Ethereum, you can deploy to AERE, same tools, same workflow, faster blocks. Everything you need to go from idea to mainnet is below.

Chain ID
2800
RPC
https://rpc.aere.network
WebSocket
wss://wss.aere.network
Native token
AERE
EVM ruleset
Pectra + Fusaka
Consensus
QBFT · 0.62 s blocks (0.5 s target)
EVM ruleset: AERE runs Pectra + Fusaka (both activated 2026-05-31), the Prague and Osaka rule sets of Ethereum mainnet, though not full parity: the EIP-4788 beacon-roots system contract has no code on chain 2800. Deploy any Solidity / Vyper code that runs on Ethereum, plus use native EIP-7702 (EOA → smart-account delegation), EIP-2537 (BLS12-381 precompiles), EIP-2935 (historical block hashes), EIP-1153 (transient storage), EIP-5656 (MCOPY), EIP-6780 (SELFDESTRUCT change), and RIP-7951 secp256r1 precompile at 0x100 for native Face ID / Touch ID / Windows Hello / YubiKey signature verification, natively.
Gasless UX, deployed and not funded: AERE ships a 5-contract paymaster stack (deployed 2026-05-31). The design: pay gas in a whitelisted ERC-20 (AereTokenPaymaster), a daily free-tx quota for AERE stakers (AereStakeQuotaPaymaster, stake-for-free-tx UX on EVM), or first-time sponsorship (AereOnboardingPaymaster). These three Foundation paymasters hold no deposit today (measured 2026-10-15), so they sponsor nothing until funded. What works today: a dApp deploys its own paymaster through the permissionless AereAppPaymasterFactory in one call and funds it to sponsor its own users, and Aere Cloud subscribers get their users' gas sponsored through the Foundation relay, metered to their account.
Cross-chain messaging: AereMessenger is a Hyperlane Mailbox-compatible cross-chain message bus with an ECDSA multisig Interchain Security Module, configured today with a single Foundation signer and a threshold of one (read threshold() and validators(0) on the contract), so a message is as trustworthy as that one key until more signers are enrolled. Apps call dispatch(destDomain, recipient, body) to send arbitrary payloads to any registered chain. AereIGP handles outbound gas fees. Built to be drop-in compatible with the public Hyperlane validator network once AERE is added to the Hyperlane registry, same contracts, same signature scheme, same Warp Route token-bridge pattern. For typed token bridging, deploy an AereWarpRoute per asset (collateral on the source chain, synthetic on AERE).
Intent-based cross-chain UX, not yet usable, and the V1 addresses are deprecated. The design is an Across-v3-compatible SpokePool where a user signs an intent ("I want X on Aere Network, charge me Y from any chain") and a solver delivers, plus an ERC-7683 IOriginSettler so UniswapX, Across, CoW Protocol, 1inch Fusion and any other intent aggregator can route orders through one uniform interface, with permissionless solver participation. What is actually on chain, measured 2026-08-01: the V1 pair AereSpokePool 0xCAB1DBA5… and AereERC7683 0x67Fb9830… is marked deprecated and flawed in our own registry, because the settlement path could release locked principal without properly verifying the delivered output leg. Do not integrate against them. Both hold a zero balance. The corrected pair, AereSpokePoolV2Corrected 0xbEF9BF0D… and AereERC7683V2Corrected 0x8eC4e7F0…, is deployed and deliberately inert: no remote spoke is enrolled, so no intent route is open on either version. Build against V2 when the route opens, and never against V1.
Pyth-compatible pull oracle: AerePyth implements Pyth Network's IPyth interface, apps written against the canonical Pyth SDK work unchanged on AERE. Publisher-signed pull updates: callers include a recent attestation as calldata; the contract verifies threshold signatures and serves the price within the same transaction. AereOracleAdapter exposes a unified quote(symbol) interface that routes Pyth → legacy AereOracle fallback, so existing dApps keep one address and one signature while the underlying source migrates. When AERE is added to the public Pyth network, the same contracts accept Guardian-set signatures without redeploy. No publisher feed is live on chain 2800 yet (no price update in the 300,000 blocks before 2026-10-15), so there is no price to read today.
Verifiable randomness (drand): use AereRandomnessBeaconV2 (0xaDC45101D408E88d3268e2262CD53F3A4eC92cfD). It consumes the drand Quicknet chain (3-second period, threshold-BLS-signed by the League of Entropy) and checks every submitted signature against the Quicknet public key on chain with the EIP-2537 precompiles, so a forged round is refused. A dApp fetches the signature for a round (free at api.drand.sh) and submits it with submitRound(round, signature), paying its own gas. Measured on 2026-10-15 with a simulated call: a real signature accepted, a forged one refused with "BLS verification failed". Do not use the first version, AereRandomnessBeacon 0x25b6317e…D8213C, or the reference consumer AereDrandConsumer built on it: that version accepts any signature, so whoever submits a round chooses its randomness.
Validator-reward burn (live, currently burning ~0 because validator reward is 0): AereCoinbaseSplitter atomically routes validator coinbase rewards: 37.5% to AereFeeBurnVault (permanent destruction, no withdraw, no admin), 62.5% back to the validator. This burned share is a Foundation-set cut of validator block rewards, currently 37.5% and hard-capped at 50%, routed to a sealed vault whose destination can never change; it is now measurable in real time via splitter.totalBurned() and the vault's on-chain balance. Each validator runs a small forwarder daemon that sweeps coinbase into the splitter periodically. As gas volume grows (consumer apps, dApps, paymasters, intent bridging), the burn would steadily remove AERE from a fixed, no-emission supply. Until validator coinbase revenue is non-zero, that reduction stays at today’s measured 0.1374 AERE, and Aere is not deflationary today.
Developers get paid: AereFeeMonetizationV2 is built to pay you AERE for the transactions that touch your registered contract. Call register(contractAddr, payoutAddr) for a contract you control, receive an ERC-721 NFT representing its fee stream, and collect a 20% share of the gas fees credited to it. Credits are made by a Foundation distributor from validator fees; no distributor runs today and the contract holds no AERE (measured 2026-10-15), so it pays nothing yet. The NFT is transferable, sell your fee stream on AereNFTMarketplace, fractionalise it, collateralise it. The design: developers paid for the work their code does, from the gas their contracts generate, and a 5% treasury share, with no grants application, no token launch and no user surcharge. It becomes real when the distributor runs.
Touch ID / Face ID wallets: AERE chain 2800 has native passkey wallet support via the Fusaka RIP-7951 secp256r1 precompile. AerePasskeyAccountFactoryV2Fixed deploys CREATE2 smart accounts whose only signer is a WebAuthn passkey (Touch ID, Face ID, Windows Hello, YubiKey, EU Digital Identity Wallet); applications reach it through Aere Cloud's gas sponsorship. The first factory (0xfB0e…0739) is deprecated: it can create accounts that no key controls, so do not use it. On-chain WebAuthn verification through the precompile costs a small fraction of a pure-Solidity P-256 verifier. How the passkey wallet works →
Native zk-proof verification: AERE chain 2800 deploys the canonical SP1VerifierGateway (Succinct Labs v6.x Groth16 + Plonk) and RiscZeroVerifierRouter (RISC Zero zkVM). Verify any SP1 or RISC Zero proof on the native BN254 precompiles. Wrap with AereProofRegistry for permissionless program registration + permanent on-chain attestation. Future SP1 v7+ / RISC Zero v2+ versions plug in via addRoute with zero dApp migration. Live proof feed →
MEV-resistant batch DEX: AereSettlement is a batch-auction settlement contract, users sign EIP-712 orders off-chain (no gas), an authorised solver collects open orders, finds a uniform clearing price per token pair, and submits the batch atomically. The entire batch executes in one transaction, so no one can sandwich it: a single uniform price applies to every order in the batch. Coincidence-of-wants matching between orders pays zero AMM fee. AereVaultRelayer proxies token allowances; AereSolverRegistry manages the solver set. No solver runs on mainnet today (no settlement in the 300,000 blocks before 2026-10-15), so signed orders do not settle yet; Phase 2 adds permissionless bonded solver entry.
AERE mainnet is live. The genesis was re-executed on 2026-05-07 establishing a 2.8 billion AERE supply. System contracts, including the staking module, governance DAO, NFT registry, oracle, and identity attestation system, are deployed; where one is not in use yet, this page says so (the price oracle AereOracleV2 has no fresh reporters; the old reporter stack was stopped on 2026-08-23). You are building on a running chain, not a testnet.

Learn → Build → Launch

1
Step one
Learn the chain
Read the documentation to understand the network architecture, system contracts, and development environment setup. Add AERE to MetaMask using Chain ID 2800 and RPC https://rpc.aere.network. There is no public sale and no exchange listing, and until AERE is listed the Foundation does not give out mainnet AERE (the mainnet faucet was closed on 2026-10-15). Build and test on the public testnet, chain 28001: the same node software, and test tokens with no value from its faucet.
2
Step two
Build your project
Deploy contracts using Hardhat or Foundry pointed at the AERE RPC. Use the AERE SDK for front-end integration or chain-specific helpers. Consult the RPC & API reference for the JSON-RPC method list, indexer API endpoints, and WebSocket event subscriptions. Read the state window section before you write anything that reads state at a historical block: the public endpoints keep world state for 512 blocks, and beyond that state reads are refused with -32000 World state unavailable, and eth_call with -32603 Internal error (until 2026-09-10 eth_getTransactionCount answered a false 0x0 there, and another provider still can; corrected 2026-10-27: this sentence said it still does, and gave -32000 for eth_call too). Verify deployed contracts on the block explorer.
3
Step three
Launch and grow
Deploy to mainnet. Gas on mainnet is paid in AERE, which is not sold or given out before listing; for a production integration, an Aere Cloud plan sponsors your users' gas through the Foundation relay, metered to your account. Apply for a developer grant if your project contributes to the ecosystem, no equity, no token claw-backs. The AERE source is open on git.aere.network/aere-network (aere-contracts, sdk-js, aere-docs, aere-research, aere-node), publish your own source to build credibility with the community. The Foundation is available via the repository issue tracker for integration support.

Resources

📖
Documentation
Network architecture, system contract reference, deployment guides, and tutorials.
☁
Aere Cloud
Keyed RPC endpoints, managed nodes and the live post-quantum verification API, priced in USD: while AERE is not listed, paid plans are invoiced in USDC or EUR and activated on chain by a subscription contract that never custodies funds.
⚡
RPC & API Reference
Full JSON-RPC method list, indexer REST API, WebSocket subscriptions, the 512-block state window (beyond it state reads are refused; until 2026-09-10 one call returned a false zero; corrected 2026-10-28).
🛠
AERE SDK
JavaScript / TypeScript SDK for connecting to AERE, reading chain state, and signing transactions.
🚰
Faucet
The mainnet faucet is closed since 2026-10-15: until AERE is listed, no mainnet AERE is given out. Test tokens come from the testnet faucet below.
🧪
Testnet
Chain 28001: the same node software as mainnet with hybrid post-quantum consensus (a Falcon-512 checkpoint under the hash of every 32nd block) and its enforcement switched on, 10 tAERE per address per 24 hours from the testnet faucet, no real value. Live since 2026-09-02.
💸
x402 on the testnet
An x402 v2 facilitator for chain 28001 (GET /supported, POST /verify, POST /settle) settling the "exact" scheme through EIP-3009 on a test dollar (tUSD, free faucet, no value). A real payment is run through it every 6 hours and the result is public. Mainnet needs a real EIP-3009 asset first; none is live yet.
🐳
Local devnet
docker run --rm -p 8545:8545 git.aere.network/aere-network/devnet:latest runs a one-validator local chain (id 28002) with 500 ms blocks, ten funded Hardhat accounts, and DEBUG and TRACE open. Published 2026-09-02, built from the binary the mainnet validators ran that day (they run newer builds now; pulled anonymously on 2026-10-15); the public read node rpc2 also answers read-only trace calls.
💰
Developer Grants
$1k, $100k in funding for dApps, infrastructure, tooling, and content. Public and milestone-based.
🔍
Block Explorer ↗
Search transactions, blocks, addresses, and token transfers on AERE mainnet.
📦
Source on Git ↗
Public repositories at git.aere.network/aere-network: aere-contracts (Solidity), aere-research (vectors, formal models, benchmarks), aere-docs (specifications), sdk-js (TypeScript client).
📡
Oracle Network
AereOracleV2, a multi-reporter median that needs three fresh reporters: none publishes today (the old reporter stack was stopped on 2026-08-23), so getPrice reverts with InsufficientQuorum. Do not integrate against it until its feeds are live.

Solutions on the network

⇄
Payments
Settlement rails for businesses moving money, final in one block on the validators (about 0.62 seconds).
⚖
Institutions and real-world assets
Issuance, custody and reporting on a public chain with fixed supply.
⚙
AI agents and x402
Machine payments over HTTP with on-chain identity; the facilitator runs on the public testnet today.
∞
DeFi
AMM, order book and batch settlement with deterministic finality.
☷
Infrastructure and tooling
Nodes, indexing, light clients and the builder surface.
◉
Run a validator
The validator package, and how the set grows beyond the Foundation.

Key facts for your configuration

Hardhat / Foundry network config

// hardhat.config.js
networks: {
  aere: {
    url: "https://rpc.aere.network",
    chainId: 2800,
    accounts: [process.env.PRIVATE_KEY]
  }
}

ethers.js / viem connection

// ethers v6
import { JsonRpcProvider } from "ethers";
const provider = new JsonRpcProvider(
  "https://rpc.aere.network"
);

// viem
import { createPublicClient, http } from "viem";
const aere = { id: 2800, name: "AERE Network",
  nativeCurrency: { name:"AERE",symbol:"AERE",decimals:18},
  rpcUrls: { default: { http:
    ["https://rpc.aere.network"] } } };

MetaMask, add network manually

Network nameAERE Network
RPC URLhttps://rpc.aere.network
Chain ID2800
Currency symbolAERE
Explorer URLhttps://explorer.aere.network

Need help?

Open an issue on aere-contracts for technical questions, bug reports, or integration requests. The source code for all system contracts is public, reading the contract is often faster than waiting for a forum response. For grant applications and larger partnership discussions, use the grants repository.