AETHEL Token TOKEN
The fixed-supply native asset of the network. It powers staking, fees, governance, and the tokenomics around Proof-of-Useful-Work rewards.
Searchable Protocol Terminology
This glossary replaces stale terminology from older site concepts and keeps the language aligned with the current protocol. Use it when you need a quick definition for Proof-of-Useful-Work, Digital Seals, vote extensions, TEE attestation, zkML verification, and the operating surfaces that appear across the site.
The fastest way to break architectural discussions is to mix current protocol terms with older site language.
Terms cover consensus, verification, wallets, relay, builder tooling, and operating model concepts.
When a term matters operationally, the surrounding site already has a deeper page for it.
Terms
Definitions below are constrained to the current Aethelred protocol, tooling, and operating surface.
No glossary terms match the current filter.
The fixed-supply native asset of the network. It powers staking, fees, governance, and the tokenomics around Proof-of-Useful-Work rewards.
A cryptographic statement tied to a computation. In the current protocol this most often refers to TEE-backed evidence bound to model, input, output, block height, and chain ID.
The consensus engine Aethelred extends through ABCI++ so verified AI execution can participate in the block lifecycle.
The validator agreement data attached to a verified job and later preserved in the Digital Seal context.
The registry that stores proof-system verification artifacts such as verifying key hashes and model-linked zk metadata.
The on-chain attestation record minted when a supermajority of validators agrees on a computation result. It is the portable trust object of the protocol.
The post-quantum signature primitive referenced in the whitepaper as part of Aethelred's hybrid cryptographic posture.
Native contract entry points for zk proof verification and TEE job submission. The current docs expose them at 0x0300 and 0x0400.
The governance and treasury control posture that delays sensitive protocol actions rather than allowing immediate privileged execution.
The verification mode that requires TEE attestation and zkML proof output commitments to match, providing defense-in-depth.
A dedicated hardware trust boundary for protecting keys. HSM-aware operational posture appears in the node standards and validator model.
The cross-chain relay path for Digital Seals. The current port name in the docs is aethelred.seal.
The local rehearsal environment for devnet orchestration, compliance linting, seal inspection, and policy-aware experimentation.
The unique identifier for a submitted workload. It is central to job tracking and Digital Seal creation.
The trusted on-chain reference set used to validate acceptable TEE measurements for attestation verification.
The committed hash of the model artifact associated with a computation, registry entry, and eventual seal context.
The consensus mechanism where validators earn rewards by performing and verifying useful AI inference workloads rather than arbitrary puzzles.
The protocol's hybrid cryptographic posture that combines familiar blockchain primitives with post-quantum signature support.
The ABCI++ stage where valid seal creation transactions are injected at the front of the block when the conditions are satisfied.
The tooling surface for inspecting and validating Digital Seal evidence outside the application runtime.
The protocol posture that keeps jurisdiction, confidentiality, and data handling rules in scope for workload design.
The institutional transfer model described in the tokenomics and whitepaper, including issuer-authorized channels and TEE-attested issuance flows.
The hardware-backed proof surface using SGX, Nitro, SEV-SNP, or H100 Confidential Computing to attest execution.
The public network rehearsal path described on the site with faucet, bridge, explorer, and endpoint categories.
A node that participates in consensus and AI inference verification. The current site documents TEE-capable GPU validators and a 100,000 AETHEL minimum stake.
The CometBFT/ABCI++ vehicle that carries computation verification data into the consensus process.
The signing surface for network actions. The current site documents CLI wallet flows, Python dual-key operations, and offline manifest handoff.
Zero-knowledge machine-learning proof generation and verification. The current site documents five proof systems and contract-level precompile support.
The EVM verification entry point at 0x0300 used for zero-knowledge proof verification inside contracts.
Most terms here map directly into the documentation hub, the Digital Seal page, the comparison page, or the workload-specific use cases.