Autheo 용어집

L2 decentralized storage system within the Autheo infrastructure stack, providing persistent and distributed data storage for applications.

Autheo Eigensphere Engine. A post-quantum, multi-language runtime environment that executes smart contracts and application logic across the Autheo stack.

The coordination of AI models and workflows within the Autheo ecosystem, handled by THEO AI for validator health monitoring, adaptive workflows, and on-chain inference.

The layer of Autheo's stack, above the compute fabric and below the developer platform, offering higher-order services such as AI inference, databases, hosting, and serverless functions.

A distributed cloud platform, built as a Layer-0 Operating System with an integrated Layer-1 blockchain, that uses blockchain to establish trust and coordination while a distributed mesh provides compute, storage, and networking infrastructure.

The mechanism by which Autheo's control plane matches infrastructure supply from providers with application demand from developers, coordinating discovery, policy, scheduling, execution, and settlement.

Post-quantum sovereign identity layer using Kyber, Dilithium, and Falcon cryptographic algorithms to provide authentication and digital asset sovereignty.

The layer of Autheo's distributed infrastructure stack where application workloads actually execute: CPU, GPU, containers, virtual machines, and storage, distributed across independently owned infrastructure providers.

The process by which a blockchain network agrees on the current state of the ledger. Autheo uses Proof of Autheo, a hybrid PoA/PoS model built on Cosmos SDK and Tendermint BFT.

The coordination layer of Autheo's developer platform that discovers resources, applies policy, schedules workloads, monitors capacity, and coordinates the marketplace between infrastructure providers and applications.

A cross-chain bridge is a protocol that enables the transfer of assets, data, or messages between two separate blockchain networks. Bridges allow tokens and information to move across chains that would otherwise be isolated, enabling interoperability in a multi-chain ecosystem.

The ability for different blockchains to communicate, share data, and transfer assets without relying on centralized bridges. Layer-0 architectures enable this natively.

Decentralized Cloud Compute. The compute infrastructure layer within Autheo that distributes processing power across the validator network.

Decentralized identity is a model of digital identity management where individuals control their own credentials and data without relying on a central authority such as a government database, social media platform, or corporate identity provider. On Autheo, decentralized identity is implemented through TheoID, a sovereign on-chain identity system built into the Layer-0 OS.

Native development workspace for testing, deploying, and scaling projects on Autheo. Provides integrated tools for frontend, backend, smart contracts, and orchestration.

The way Autheo describes itself at the highest level: a platform where a blockchain provides shared trust and coordination while a distributed mesh of independently owned infrastructure provides compute, storage, and networking, consumed by applications as programmable services.

The distributed delivery layer of Autheo's infrastructure stack, covering CDN, points of presence (PoPs), GeoDNS, BGP anycast routing, and web application firewall (WAF) capabilities.

A programming language designed for Autheo smart contract and application development, optimized for the AEE runtime.

An ecosystem participant who contributes compute, storage, or edge capacity, such as an enterprise datacenter, GPU cluster, cloud VM, university cluster, factory or IoT edge system, or home lab, to Autheo's distributed cloud platform.

The ability of different blockchain networks and systems to exchange information and value seamlessly, a core feature of Layer-0 architecture.

The foundational infrastructure layer that sits beneath Layer-1 execution chains, providing shared security, interoperability, and cross-chain communication.

A blockchain that handles transaction execution and consensus directly. Examples include Ethereum, Solana, and Autheo integrated Layer-1.

A scaling solution built on top of a Layer-1 blockchain that processes transactions off the main chain while inheriting its security. Examples include Optimism and Arbitrum.

The peer-to-peer layer of Autheo's infrastructure stack that handles discovery, routing, and relaying between independently owned infrastructure providers, enabling the distributed compute and edge fabric to function as one coordinated network.

The public offering of Autheo validator node licenses, allowing participants to purchase the right to operate validator nodes on the network.

Cryptographic algorithms designed to resist attacks from both classical and quantum computers. Autheo uses Kyber, Dilithium, and Falcon algorithms.

Autheo's hybrid consensus model combining licensed validator eligibility (NFT License gate) with stake-weighted block production (staking gate), built on Cosmos SDK and Tendermint core BFT.

The path an infrastructure provider takes to join Autheo's distributed cloud platform and start earning THEO: installing the runtime, generating an identity, registering a node, joining the mesh, and advertising resources to the marketplace.

Quantum-resistant Interoperable Encryption Standard. Security framework used across the Autheo stack for post-quantum data protection.

Quantum-Secure DAG-based finality. The consensus mechanism used by Autheo that provides fast transaction finality with resistance to quantum computing attacks.

The path a user request takes through Autheo's distributed cloud platform: from DNS and edge routing through authentication and compute to the final response.

The cross-cutting layer of Autheo's infrastructure stack that provides identity, authorization, TLS, post-quantum cryptography, and attestation across every other layer.

Self-executing code deployed on a blockchain that automatically enforces the terms of an agreement when predefined conditions are met.

Smart contracts are self-executing programs stored on a blockchain that automatically enforce the terms of an agreement when predefined conditions are met. They run exactly as programmed without the possibility of downtime, censorship, or third-party interference, enabling trustless transactions and decentralized applications.

An independent blockchain that maintains its own security and consensus while connecting to the broader Autheo ecosystem through Layer-0 interoperability.

Staking is the process of locking cryptocurrency tokens in a blockchain network to support its operations — such as validating transactions and securing consensus — in exchange for earning rewards. On Autheo, staking THEO tokens allows participants to run validator nodes that power the Layer-1 and receive THEO emissions from the validator pool.

Intelligent automation engine within the Autheo stack that handles validator health monitoring, adaptive workflows, and on-chain AI inference.

The native utility token of the Autheo ecosystem, used for staking, compute access, storage allocation, AI inference, and transaction fees. THEO is a utility token, not a governance token.

The collective term for Autheo's compute, edge, and mesh layers, which coordinate independently owned infrastructure (enterprise datacenters, GPU clusters, cloud VMs, university clusters, factory or IoT edge systems, home labs) so it behaves like one logical cloud.

A validator is a network participant responsible for verifying transactions, producing blocks, and maintaining consensus on a blockchain. On Autheo, validators operate licensed node infrastructure that secures both the Layer-0 OS and the integrated Layer-1 blockchain, earning THEO token emissions for their contribution to network integrity.

A network participant that validates transactions, produces blocks, and secures the Autheo blockchain in exchange for THEO token rewards.

A zero-knowledge proof (ZKP) is a cryptographic method that allows one party to prove to another that a statement is true without revealing any information beyond the fact of its truth. ZKPs enable privacy-preserving verification — confirming identity, credentials, or transaction validity without exposing the underlying data.