Short answer
The Aeredium testnet is publicly accessible at explorer.aeredium.io. It uses a Blockscout interface, the same explorer software used by hundreds of EVM networks including Optimism and Base. You can check blocks, transactions, addresses, and contract activity without any login, wallet, or special access.
The first TEE-BFT consensus block was committed on April 16, 2026, after resolving nine engineering problems across three codebases. A public benchmark followed, recording 1,436,820 TPS ingestion with a 0% failure rate across a three-node, intercontinental deployment. Methodology: production hardware, real TEE attestation, no simulation.
The June AMAs add an important distinction: the June 25 AMA described public testnet as running around 250,000 TPS end to end through smart contract execution and attestation, while separate AMA and blog sources describe higher ingestion or stagenet figures. Those are not the same metric and should not be collapsed into one headline claim.
What makes this testnet different from most is what's running underneath it. Read the full architecture overview for the complete picture. Aeredium's validators are not traditional PoS nodes. They're TEE enclaves distributed across AWS Nitro Enclaves (50%), Azure SEV-SNP (30%), and GCP Confidential Space (20%). Every block finalizing on that explorer was validated inside hardware-isolated environments with attestation proofs, not by human node operators. The current official site states 50 blocks/sec and 20ms block time. The July 9 AMA described variation around 30-50 blocks/sec and said explorer display can appear frozen before catching up. The stats widget above pulls directly from the live API so you're seeing the actual current state of the chain.
The benchmark: 1,436,820 TPS
AEREDIUM published a public benchmark following the first block milestone. The headline number is 1,436,820 transactions per second ingestion throughput. Here are the full results:
The methodology statement from the official announcement is explicit: production hardware, real TEE attestation, intercontinental distances, no simulation, no synthetic conditions, no local-only testing. Read the full announcement →
Three things to understand about how this number is produced. First, "ingestion throughput" measures how fast transactions enter and clear the processing pipeline, not the finality-confirmed TPS of a steady-state public network. Second, the benchmark was on a three-node network. Third, AMA comments distinguish public testnet, stagenet, and benchmark environments; do not collapse those numbers into one claim. The Group Model architecture is designed to scale linearly: each additional group of three validators adds roughly 1.4M TPS to theoretical capacity. Projected at 10 groups: ~14.3M TPS. No stated theoretical ceiling. Those are projections, not measured results at that scale.
For context against other networks, the comparison the official announcement publishes: Bitcoin processes 7 TPS, Ethereum 15–30, Solana 2,000–4,000 actual throughput, Visa peak capacity 65,000. The 1,436,820 figure is ingestion throughput under test conditions, while the other figures represent different measurement standards and operating conditions. The directional difference in scale is still substantial.
The explorer: what it is and how to use it
Go to explorer.aeredium.io right now. What you'll see is the standard Blockscout interface: a dashboard showing recent blocks and transactions, a search bar where you can look up addresses or transaction hashes, and navigation to blocks, transactions, tokens, and contracts.
Blockscout is open-source, widely used, and familiar to any Ethereum developer. Aeredium chose it because the chain is fully EVM-compatible. Solidity smart contracts, MetaMask, Hardhat, and standard ECDSA transaction signatures all work natively. The explorer reflects that EVM compatibility while the underlying consensus runs inside multi-cloud TEE infrastructure.
The API is also public. Two endpoints worth bookmarking:
The stats endpoint returns total transactions, total addresses, average block time, and gas statistics. The blocks endpoint returns the most recent blocks with height, timestamp, and transaction count. Both return standard JSON, useful for monitoring, dashboards, or building on top of the testnet.
How to read the testnet activity
Testnet numbers tell a story if you know how to read them. Here's what each metric in the explorer actually indicates:
Confirms the chain is producing blocks
A climbing block height with recent timestamps means the chain is active. Block height should be growing quickly on an active testnet; the official site states 50 blocks/sec while the July 9 AMA described operational variation around 30-50 blocks/sec and explorer catch-up behavior. A stalled block height could mean the testnet is paused, restarting, or the explorer is temporarily out of sync.
The cumulative activity on-chain
Every interaction, wallet transfers, contract deployments, contract calls, adds to this count. On testnet, this includes developer testing, faucet activity, and any public experimentation. It's a useful volume signal even if it includes automated transactions.
Wallets that have been seen on-chain
Each unique address that has sent or received a transaction. A growing address count during testnet suggests increasing developer and community engagement. One person can create many addresses, so treat this as a floor estimate of participants.
How close to the current cadence target
Check the time gap between recent blocks on the explorer. The official site currently states 50 blocks/sec and 20ms block time. In the July 9 AMA, Albert described variation around 30-50 blocks/sec and said the explorer may look paused before catching up. Treat the figures as project-reported until independent measurements are published.
What TEE consensus means for testnet
Most testnet explorers show you chain activity with no particular insight into what's validating it. On Aeredium, the validator architecture is itself one of the things being tested. Each validator has two components: a Parent Compute Instance that handles networking, mempool, Geth EVM execution, storage, RPC, and logging; and a TEE Component that handles private key storage, block signing, consensus voting, and attestation generation. The parent instance cannot sign blocks or influence consensus without the TEE component.
This means what you observe on the explorer is the output of hardware-attested consensus: no block can appear there unless a threshold of independent TEE components across multiple cloud providers agreed to sign it.
Each block is TEE-attested
Every block on the explorer was finalized by a consensus of TEE enclaves, hardware-isolated environments that produce cryptographic attestation proofs of what code ran inside them. You're not just watching transactions, you're watching attestation-backed consensus in action.
AWS, Azure, GCP: no single provider dominates
The validator set is distributed: 50% AWS Nitro Enclaves, 30% Azure SEV-SNP, 20% GCP Confidential Space. No single cloud provider can unilaterally control the chain, and each provider has an independent hardware root-of-trust.
State-root commitments on Bitcoin ~every 100 blocks
Approximately every 100 blocks (5–10 minutes), an OP_RETURN transaction on Bitcoin records Aeredium's proof and state-root commitments. That makes Aeredium's state history independently verifiable against the Bitcoin blockchain, the most tamper-resistant distributed ledger in existence.
Parallel execution · 250,000 TPS described on public testnet
Aeredium uses Block-STM parallel EVM execution, the same approach pioneered by Aptos, rather than sequential transaction processing. The June 25 AMA described the live public testnet around 250,000 TPS end to end, while a separate peak ingestion benchmark recorded 1,436,820 TPS under controlled load conditions.
Developer access: build on the testnet now
Because Aeredium is fully EVM-compatible, the developer onboarding path is familiar. You can connect MetaMask, deploy Solidity contracts, and use Hardhat with minimal configuration changes from your standard Ethereum setup.
Official network configuration details (RPC endpoints, chain ID, faucet) should be sourced from the official Aeredium documentation and the Airdrop campaign page, not from unofficial Discord servers or Telegram links. The official resources to check:
The white paper confirms Solidity compatibility, MetaMask support, and Hardhat compatibility. Standard ERC-20, ERC-721, and other contract patterns deploy normally. What you're testing isn't just your contract. You're also testing how it behaves in a TEE-attested, anti-MEV, parallel-EVM environment. That's a meaningfully different execution context from standard Ethereum or L2 deployments. The July 9 AMA said a DApp Store has started with one example and that weekly DApp competitions and developer rewards are being finalized. Treat participation and reward details as pending until published.
What comes after testnet
The white paper describes a three-phase roadmap. Testnet is where Phase 1 is being validated. Here's what the remaining milestones look like:
Testnet: TEE validators, EVM, AES-256-GCM encryption, Bitcoin anchoring
The core stack is running: TEE-based validator network, standard EVM execution, AES-256-GCM protocol-level encryption, and Bitcoin anchoring. The testnet is where all of this is being tested under real (if controlled) conditions.
Mainnet launch, then AERX exchange listing
Mainnet is the transition from test to production. The July 9 AMA set an August 1 objective without guaranteeing delivery. AERX exchange listing follows later, with no named venue or date. Albert said a faucet may continue until listing and could make early deployment free or nearly free for a couple of months.
Cross-chain bridges, observability dashboard, validator metrics
Phase 2 expands the cross-chain infrastructure, adds public monitoring tools, and publishes validator performance data. This is when the 10-chain interoperability becomes more fully visible to external observers.
Privacy transactions, post-quantum signatures, advanced DeFi
Long-term: privacy-preserving transaction processing, dynamic cloud optimization, post-quantum user transaction signatures, and advanced DeFi primitives. Separately, the July 9 AMA said a quantum-resistance report and libraries could be released within roughly a week for community contribution; that near-term claim is not yet a completed Phase 3 release.
Per white paper v3.7 (May 2026), AERKey Privacy Layer Layers 1 and 4 are planned for mainnet. The July 9 AMA set August 1 as the newest mainnet objective, without guaranteeing it. Layers 2, 3, and 5 remain post-mainnet with no confirmed dates.
Sources
1.4 Million TPS Benchmark Announcement
Exact figures: 1,436,820 TPS, 2M transactions, 1.39s, 0% failure rate. Group Model architecture, micro-batching transport, 64-worker parallel enclave processing. Methodology: production hardware, real TEE attestation, no simulation.
The Key That Nobody Holds
Albert Dadon AM: first block April 16, 2026, AERKey architecture, geographic distribution, public attestation registry.
Decentralisation Through Cryptography and Mathematics
AEREDIUM Foundation: two-component validator architecture (Parent Compute Instance + TEE Component), attestation chain, control hierarchy.
AERKey Privacy Layer White Paper (formerly AEGISKey v2.1)
Five privacy layers, MEV elimination, US Patent Application 63/977,868. Layer timeline superseded by white paper v3.7: Layers 1 and 4 planned for mainnet, Layers 2/3/5 post-mainnet.
Testnet safety checklist
Early networks attract scammers targeting people who want to participate early. Before interacting with anything related to the Aeredium testnet:
- Get network settings (RPC, chain ID, faucet) only from official Aeredium documentation, not from social media, Telegram, or unofficial Discord servers.
- Open the explorer only from the verified domain: explorer.aeredium.io.
- Use a dedicated test wallet for testnet experimentation. Never use a wallet holding real funds.
- Never enter a seed phrase or private key into any website, faucet, support chat, or bot.
- Testnet AERX has no exchange value. Do not buy "testnet AERX" from anyone.
- Contract addresses for any interaction should be confirmed through official Aeredium documentation before use.
- The KIMA conversion is a separate flow through StablePro Wallet, with the current transfer deadline extended through August 1, 2026. It has nothing to do with testnet participation.
Related Aeredium guides
FAQ
Where is the Aeredium testnet explorer?
Live at explorer.aeredium.io. Blockscout interface, no login required. You can see blocks, transactions, and addresses right now.
What's special about this testnet?
The validators are TEE enclaves across AWS, Azure, and GCP, not human node operators. Every block is finalized by hardware-attested enclaves executing in isolation. No validator can see the transaction data it processes. That is the core security claim being demonstrated on testnet.
Is the Aeredium testnet EVM-compatible?
Yes. Aeredium is fully EVM-compatible: it supports Solidity smart contracts, MetaMask, Hardhat, and standard ECDSA transaction signatures. Developers familiar with Ethereum can deploy to Aeredium testnet without new tooling. The difference is under the hood: execution happens inside multi-cloud TEE enclaves.
Does testnet activity mean AERX is listed?
No. Testnet activity and AERX exchange listing are completely separate. The listing follows mainnet launch. Do not buy anything sold as AERX before the official listing is announced through official Aeredium channels. There is no legitimate way to buy AERX yet.
What comes after testnet?
The July 9 AMA set an August 1 objective for mainnet, without guaranteeing it. Exchange listing follows later. A faucet may bridge the period, while DApp rewards and quantum-resistance libraries remain announced but unpublished.