Aetheris Development Milestones
A technical progress report on the core architecture built and validated in the Aetheris development environment.
Core architecture, built end to end
The team has completed the core architecture and network layer in a development environment, from local node setup and smart contract compilation to wallet-based transactions. Everything described here ran on the local devnet, not a public network. The overall plan is explained in the white paper.
Milestones achieved
- 1Private local blockchain nodeAn independent, private local blockchain node with custom parameters (Chain ID 84337, currency symbol AETH) that produces sequential ledger blocks on demand.
- 2Smart contract compilation and local deploymentFoundation contracts developed, compiled with Solidity v0.8.24 and deployed locally, including the AetherisStorage contract and a baseline ERC-20 token ledger that manages account balances.
- 3Client state managementA modular React Context Provider and a shared state hook that handle MetaMask session monitoring and account synchronization across the interface.
- 4Wallet-to-web interfaceAn interactive console built with Vite, Ethers.js v6 and client-side transaction services. It prompts the wallet to switch to the correct custom network and formats account details clearly.
- 5Live contract execution and validationTransactions were submitted, signed and processed on the local chain using MetaMask, confirming working contract payloads, block validation and token distribution in the development environment.
Technology stack
Network settings such as the Chain ID and the local RPC endpoint are listed once, on the local devnet and sandbox page. The client code is written as ECMAScript Modules (ESM).
Development environment only. These milestones were completed on a local devnet. They do not mean the Phase 2 network layer has launched, and no public launch date is stated here. See the roadmap for current status.
How the pieces fit together
The milestones in this report build on each other, from the chain itself up to the screen a user sees. At the bottom is the node, a Hardhat local blockchain that creates blocks and stores account balances. Above it sit the smart contracts, written in Solidity, which define rules such as how balances are stored and transferred. Above the contracts is the client layer, a React interface that talks to the chain through Ethers.js and to the user's wallet through MetaMask.
Why a baseline ERC-20 ledger
ERC-20 is the widely used standard for fungible tokens on EVM-compatible chains. Implementing a baseline ERC-20 ledger in the development environment shows that account balances and token transfers behave as expected with familiar tooling. It also matches the public AETH token, an ERC-20 utility token with a fixed supply of 21,000,000, which is described on the tokenomics page.
Client state and wallet handling
Wallet sessions change constantly. Users switch accounts, change networks or disconnect. The React Context Provider and shared state hook keep the interface in sync with those changes in one place, which avoids duplicated logic across components. The interface also asks the wallet to switch to the custom network, so users are on Chain ID 84337 before they send anything.
What validation means here
The fifth milestone confirms that the full path works. A user signs a transaction in MetaMask, the node mines it into a block, and the interface shows the updated state. That end-to-end test is the strongest evidence in this report, but it was carried out on a private local chain.
Why build in a development environment first
Building the full stack on a private chain first lets a team connect every layer, from contracts to wallet, and fix integration problems cheaply. Mistakes made here cost nothing, which is why this phase comes before any public release. The trade-off is that a private chain cannot reproduce public conditions, so these milestones are a foundation rather than a finished network.
Reading this report responsibly
These milestones show engineering progress, not a finished product or a public release. Results on a local node do not predict performance on a public network, and this page makes no promises about timelines or token value. Follow the roadmap for official updates.
Key terms explained
Understanding a few terms makes the milestones easier to follow. You do not need a technical background to see the main point: each layer was built and tested together on a private chain before anything is exposed to the public.
Chain ID: A number that identifies a blockchain network, so wallets and apps can tell networks apart and avoid sending a transaction to the wrong one. The value used by the Aetheris sandbox is listed on the sandbox page.
Hardhat: A development tool for Ethereum-style software that runs a local blockchain node, compiles contracts and runs tests.
Solidity: The programming language used to write smart contracts for EVM-compatible chains. This work uses version 0.8.24.
ERC-20: A standard interface for fungible tokens. It defines common functions such as checking a balance and transferring tokens.
Ethers.js: A JavaScript library for reading data from a blockchain and sending transactions from a web application. Version 6 is used here.
MetaMask: A non-custodial browser wallet that holds the user's keys and asks for approval before signing a transaction.
RPC endpoint: The web address a client uses to send requests to a node. In this environment it points to the local machine.
Together these tools form a complete development loop, which is why the team could move from a blank node to signed, mined transactions inside one controlled environment.
Frequently asked questions
What do these milestones cover?
Local node setup, Solidity contract deployment, client state management, a wallet-to-web interface and live transaction validation, all on the local devnet.
Were they tested on a public network?
No. Every result was produced on the local Hardhat node. Public network results are not part of this report.
Where can I find the network settings?
They are listed once on the local devnet and sandbox page, including the Chain ID and the local RPC endpoint.
Explore the local sandbox
See the network configuration and what developers can test in the Aetheris sandbox.
Digital assets carry risk, including loss of funds. Nothing on this website is financial advice. Do your own research before you participate.
