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.
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 TEE-BFT consensus targets 1–2 second finality. 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 →
Two 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 network. Second, the benchmark was on a three-node network. 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. TEE-BFT targets 1–2 second finality, so block height should be growing quickly. 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 2-second finality target
Check the time gap between recent blocks on the explorer. If blocks are arriving roughly every 1–2 seconds, the TEE-BFT consensus is performing as specified in the white paper. Gaps or irregularities during testnet are normal during load testing and network adjustments.
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 targeting 10,000+ TPS
Aeredium uses Block-STM parallel EVM execution, the same approach pioneered by Aptos, rather than sequential transaction processing. On testnet, this sets up the infrastructure for the claimed 10,000+ TPS throughput once mainnet load arrives.
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.
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, ZK-STARK, Bitcoin anchoring
The core stack is running: TEE-based validator network, standard EVM execution, ZK-STARK attestation proofs, and Bitcoin anchoring. The testnet is where all of this is being tested under real (if controlled) conditions.
Mainnet launch + AER exchange listing
Mainnet is the transition from test to production. AER exchange listing follows. That's when AER becomes a live tradable asset. The KIMA-to-AER conversion window (June 1–30, 2026) is also tied to mainnet launch timing.
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 13-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 built on the settled TEE infrastructure.
A separate roadmap from the AEGISKey Privacy Layer white paper (v2.1, April 2026) covers the encryption infrastructure timeline: wallet-level encryption (Layer 1) in development Q2 2026, chain-native and mempool encryption (Layers 4 and 2) architecture complete for Q3 2026, smart contract and DeFi operation encryption (Layers 3 and 5) in design phase for Q4 2026.
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, AEGISKey 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.
AEGISKey Privacy Layer White Paper v2.1
Five privacy layers, Q2–Q4 2026 implementation roadmap, MEV elimination, US Patent Application 63/977,868.
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 AER has no exchange value. Do not buy "testnet AER" 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 during June 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 AER is listed?
No. Testnet activity and AER exchange listing are completely separate. The listing follows mainnet launch. Do not buy anything sold as AER before the official listing is announced through official Aeredium channels. There is no legitimate way to buy AER yet.
What comes after testnet?
Mainnet launch is the next major milestone. After that: AER exchange listing, full StablePro Wallet launch, and the KIMA-to-AER conversion window (June 1–30, 2026). Phase 2 adds cross-chain bridges and an observability dashboard. Phase 3 adds privacy-preserving transactions and post-quantum signatures.