Launch Preparation

Testnet Dashboard

Prepare for the Aethelred testnet launch with the exact specifications, launch access model, and endpoint settings your team needs. Validate free token flows, weekly refresh cadence, bridge readiness, and observability before the network goes public, then move into the integration docs and the tooling workflows that support launch-day testing.

Launch Specs Free tAETHEL Weekly Refresh Analytics Ready

Testnet Coming Soon

Finality Goal

Deterministic settlement with sub-2-second target finality.

Faucet Access Model

Planned allocation: 10,000 tAETHEL per address every 24 hours for integration testing.

Launch Operations

24-validator target cohort, explorer visibility, and developer support channels aligned for launch.

Target Specifications

Planned network performance profile

Reference specifications for testnet launch readiness and integration planning.

Target Throughput

50K+ IPS

Consensus

PoUW

Compute Capacity

400 PFLOPS

Block Finality

<2s

Target Block Time

Sub-2s

Model Support

32B params

Token Supply

10B

Token Standard

ERC-20

Architecture

Testnet architecture matrix

Core components and current implementation status for launch planning.

Component	Technology	Description	Status
Settlement Layer	Cosmos SDK / CometBFT	Deterministic finality with sub-2s block times	In Development
Compute Layer	TEE Workers (SGX/TDX)	Hardware-attested AI inference with 400 PFLOPS target	In Development
Cryptography	ML-DSA-65 / ML-KEM-768	Post-quantum hybrid signatures and key encapsulation	Implemented
Bridge	AethelredBridge.sol	64-block finality, multi-sig guardian, rate-limited	In Development
Smart Contracts	Solidity (EVM)	6 audited contracts for tokenomics and governance	Deployed

Feature Set

What teams can validate before mainnet

The reference testnet environment adds practical developer workflows beyond basic chain access. These are the feature expectations being carried into the Aethelred public testnet launch model.

Developer Workflow

Testnet is designed for rehearsal, not just connectivity

Use the environment to validate onboarding, token issuance, endpoint failover, seal visibility, and post-reset recovery before production cutover.

Faucet Window Every 24 Hours

Reset Cadence Sunday 00:00 UTC

Support Path Community + Core Devs

PARITY

Protocol Readiness

Full protocol parity

Test the same Proof-of-Useful-Work, Digital Seal, and verification flows expected on mainnet so application logic does not fork between environments.

TOKEN

Access Policy

Free test token access

The reference faucet model allocates 10,000 tAETHEL per address every 24 hours so teams can run onboarding, integration, and load-testing workflows without financial exposure.

SPEED

Iteration Speed

Rapid iteration loops

Use faster block cadence and testnet-safe operating conditions to rehearse retries, failure paths, and deployment rollouts before production launch windows open.

TRACE

Observability

Explorer and analytics visibility

The reference page highlights real-time visibility for transactions, seal generation, and request traces. This testnet page now carries those observability expectations into launch planning.

RESET

Environment Hygiene

Planned weekly refresh window

The reference environment uses a weekly reset cadence. For launch planning, teams should expect a scheduled refresh window every Sunday at 00:00 UTC for clean-state testing.

SUPPORT

Developer Enablement

Community support channel

The reference testnet includes an active developer help path. Expect onboarding support through community channels so teams can resolve endpoint, faucet, and integration questions quickly.

Bridge

Testnet bridge

Bridge test tokens between Ethereum Sepolia and Aethelred testnet once launch is activated.

Launch Guardrails

Bridge access opens only when settlement and guardian workflows are ready

Teams can pre-wire the cross-chain route now, then move into live transfer testing once confirmations, guardian approval, and rate-limit controls are active.

Source Route Ethereum Sepolia

Destination Aethelred Testnet

Status LOCKED UNTIL LAUNCH

FLOW

Transfer Path

Rehearse asset movement before activation

Plan application flows around Sepolia-to-Aethelred token transfers so deposit, settlement, and verification steps are ready on launch day.

Cross-chain route targets Ethereum Sepolia and Aethelred testnet
Use it to validate deposit UX, explorer visibility, and downstream application handling

RISK

Security Controls

Guarded transfer policy

The planned bridge profile uses launch-time protection controls so teams can test asset flow without exposing an unbounded transfer surface prematurely.

Availability

Bridge is currently locked until testnet launch.

Connectivity planning is available now; test token movement activates only when the public network window opens.

Faucet

Testnet faucet

Get free test AETHEL tokens for development workflows once public testnet is live.

Distribution Model

Faucet policy is tuned for onboarding and repeat testing

The reference access model is built for developer setup, QA loops, and failure rehearsal rather than one-time token drops.

Allocation 10,000 tAETHEL

Cadence Every 24 Hours

Value TEST USE ONLY

DROP

Issuance Policy

Designed for repeated developer workflows

Teams can use recurring allocations to test wallet provisioning, API setup, automation loops, and reset recovery without exhausting a one-off balance.

Per-address issuance follows the 24-hour request cycle
Tokens are intended for onboarding, integration, and load testing

USE

Operational Guidance

Use faucet cycles to test edge cases

Plan your launch drills around replenishment, exhaustion handling, and weekly refresh recovery so developer tooling behaves predictably during rollout.

Availability

Faucet requests open at launch.

Planned issuance follows the reference access model: 10,000 tAETHEL per address every 24 hours for onboarding, integration testing, and failure-mode rehearsal.

Network Configuration

Planned connection details

Endpoints will activate when testnet launches. The reference configuration adds GraphQL, gRPC, explorer, faucet, and native token details for faster integration prep.

Access Surfaces

Prepare every connection path before activation

Separate core chain endpoints from developer-facing services so teams can wire applications, dashboards, and support tooling before launch day.

Chain aethelred-testnet-1

Token tAETHEL

Status ACTIVATES AT LAUNCH

Core Access

Chain endpoints

Chain ID

aethelred-testnet-1

Native Token

tAETHEL

HTTP RPC

https://testnet-rpc.aethelred.io

WebSocket

wss://testnet-ws.aethelred.io

Developer Surfaces

Tooling and discovery

GraphQL

https://testnet-gql.aethelred.io

gRPC

testnet-grpc.aethelred.io:443

Explorer

https://testnet.explorer.aethelred.io

Faucet

https://faucet.aethelred.io

Activation note

Use these values for integration planning now. RPC, explorer, GraphQL, gRPC, and faucet surfaces are expected to activate together when the public testnet window opens.