A complete walk-through of the Aethelas pipeline — from a signed transaction to a finalized block — including where the AI layer operates alongside the blockchain core, and where it does not.
Every transaction follows the same pipeline: it is constructed and signed by a wallet, validated by the API layer, filtered by the AI engine and mempool, propagated across the P2P network, agreed upon through BFT consensus, applied to state, and persisted to RocksDB.
Hover any block to lift it out of the rail.
AI is not the consensus itself. It operates alongside the blockchain core as an advisory and security layer. Three subsystems read state and emit signals that the consensus and API layers can act on. Full details in TR‑04.
Hover a card — its layers separate in depth.
Scores each validator's historical behaviour and computes a proposer weight. The score influences selection probability — it does not replace BFT.
uptime · participationblocks_proposed · blocks_missedvotes_signed · double-sign detectionClassifies each incoming transaction with a risk score before mempool admission. This is the AIDecision record attached to every transaction.
Monitors the P2P layer for network-level attacks and writes a threat log that operators and the API can read.
A transaction is not "sent to a blockchain." It is hashed, signed, and then independently re‑verified by the node before it enters the mempool. Every step below is implemented in the current codebase.
Hover any card to lift it forward.
from · to · amount · nonce · gas · chain_id
hash = SHA-256(from:to:amount:nonce:gas:chain_id)
The private key produces a signature over the 32‑byte hash. chain_id binding prevents cross‑chain replay.
The node recomputes the hash, then verifies the signature against the sender's public key. It also checks nonce, balance, gas, and TX limits.
If all checks pass, the transaction enters the mempool with a priority derived from gas price.
Aethelas uses a Tendermint‑style BFT protocol with AI‑weighted proposer selection (iPoS). A block is finalized once two‑thirds of voting power reaches Precommit. Details in TR‑04.
Validators orbit the consensus core at three depths — the sweep arc marks quorum.
A finalized block is not a monolith. It is an ordered stack of layers — previous hash, transactions, Merkle root, timestamp, validator signature, and finally the block hash itself. Watch them assemble and separate as the rotation cycles.
Once a block is finalized, the state engine executes each transaction and applies its effects. Every mutation is committed to RocksDB and becomes part of the permanent chain state.
Move your cursor over a card — it tilts in 3D space.
Move AETH between accounts; update balances and nonces.
Lock or release AETH from validator bond; update stake records.
Charge gas per execution step; refund unused gas.
Apply double‑sign and downtime penalties; jail validator.
Distribute block rewards to the proposer and voters.
Persist validator AI scores and threat logs across restarts.
Enter a record ID to verify its existence and integrity on the Aethelas chain. Verification uses the Merkle root, the block timestamp, and the validator's cryptographic signature — the same primitives described above.
Combine multiple verification reports into a single auditable PDF. Everything runs client-side — no file ever leaves your browser.
The codebase already connects these pieces: the node starts the blockchain core, the P2P network, the REST and JSON‑RPC APIs, the transaction pool, the AI engine, and the consensus loop in a single coordinated runtime.
Explore the terminal, verify a record, or read the whitepaper for the full technical specification.