Question 1

What programming languages does Autheo support for smart contracts and dApps?

Accepted Answer

Autheo's Eigensphere Engine (AEE) natively supports Rust, Solidity, and any WebAssembly-compatible language, including Go, C++, and TypeScript via WASM compilation. This multi-language runtime sets Autheo apart from single-language chains, letting developers build without abandoning their existing toolchain.

Question 2

How do I deploy a smart contract on Autheo?

Accepted Answer

Deploy via the Autheo DevHub CLI (`autheo deploy`) or the web-based deployment console at docs.autheo.com. The AEE runtime handles compilation, optimization, and deployment to the Autheo testnet or mainnet in a single step, with THEO tokens covering gas fees at near-zero cost.

Question 3

What is the Autheo DevHub?

Accepted Answer

The Autheo DevHub is an integrated development environment combining a web-based IDE, multi-language SDK, CLI deployment tools, testnet access, and documentation in a single platform. It is designed to give developers everything they need to build, test, and ship on Autheo without cobbling together external tooling.

Question 4

How does Autheo compare to Ethereum for developers?

Accepted Answer

Autheo provides developers with a more unified stack than Ethereum: native AI inference, post-quantum security, sovereign identity, compute, and storage are all built into the OS layer, compared to Ethereum's modular approach requiring developers to integrate Chainlink for oracles, IPFS for storage, Lens for identity, and separate AI middleware. Autheo targets sub-second finality and near-zero fees versus Ethereum's variable and historically higher gas costs.

Question 5

What is AutheoID and how do developers integrate it?

Accepted Answer

AutheoID is Autheo's post-quantum sovereign identity layer, giving users a single portable digital identity across all applications built on the Autheo network. Developers integrate it via the Autheo SDK using standard OIDC/OAuth patterns for authentication, with selective disclosure for privacy-preserving data sharing, secured by CRYSTALS-Dilithium signatures instead of traditional ECDSA.

Question 6

How does THEO AI assist developers on Autheo?

Accepted Answer

THEO AI is the AI orchestration engine built into the Autheo OS layer. For developers, it provides two key capabilities: (1) a callable API for integrating AI inference, natural language processing, and intelligent workflow orchestration directly into dApps; and (2) an infrastructure intelligence layer that monitors validator health, routes transactions optimally, and detects anomalies, all transparently available without third-party AI provider setup.

Question 7

What is the Autheo Eigensphere Engine (AEE)?

Accepted Answer

The Autheo Eigensphere Engine (AEE) is the unified execution runtime at the core of AutheoOS. It merges consensus, compute, and cross-chain interoperability into a single quantum-resilient environment, enabling multi-language smart contracts, AI-assisted execution, and cross-chain data routing without the siloed architectures that create vulnerabilities and fragmentation in traditional blockchains.

Question 8

Does Autheo support EVM-compatible smart contracts?

Accepted Answer

Yes. Autheo's Eigensphere Engine includes an EVM adapter layer that allows Solidity smart contracts to be compiled and deployed on Autheo with minimal changes. Existing Ethereum dApps can be ported to Autheo to benefit from higher throughput, lower fees, post-quantum security, and native AI, while retaining Solidity as the development language.

Question 9

How does cross-chain interoperability work on Autheo?

Accepted Answer

Autheo's cross-chain interoperability is built on IBC (Inter-Blockchain Communication) protocol compatibility, extended by the AEE's quantum-encrypted state channels. Developers can route assets, data, and contract calls between Autheo appchains and IBC-compatible networks (Cosmos, etc.) using standard IBC relayer patterns, with Autheo adding post-quantum encryption to all cross-chain message payloads.

Question 10

What are the transaction fees for developers building on Autheo?

Accepted Answer

Autheo transaction fees are denominated in THEO tokens and are designed to stay at or below Solana-level costs, targeting approximately $0.00025 per transaction at a $1 THEO price. This fee model is intentional: high-frequency developer workloads, automated scripts, and microservice-pattern dApps need to be economically viable, not priced out by variable gas markets like Ethereum's.

Question 11

How does Autheo handle gas optimization for smart contracts?

Accepted Answer

Autheo's EVM-compatible Layer-1 is engineered for low-cost execution, with THEO AI providing automated gas profiling and optimization suggestions within the DevHub. Developers benefit from Autheo's high-throughput architecture (internally tested at 1B+ TPS) which distributes computational load to keep per-transaction fees predictably low. Built-in gas estimation tools and pre-audited contract templates further reduce unnecessary computation.

Question 12

What testing frameworks are available in the Autheo DevHub?

Accepted Answer

The Autheo DevHub supports the full suite of standard EVM testing frameworks, including Hardhat, Foundry, and Truffle, alongside Autheo-native tooling powered by THEO AI for automated contract validation and security scanning. Developers can run unit tests, integration tests, and governance simulations within a unified workspace without leaving the platform.

Question 13

How does Autheo handle contract upgradability?

Accepted Answer

Autheo supports EVM-standard upgradability patterns including Transparent Proxy and UUPS (Universal Upgradeable Proxy Standard), allowing developers to upgrade contract logic without changing the contract address or losing state. Autheo's DevHub provides proxy deployment templates and THEO AI-assisted upgrade validation to ensure upgrades do not introduce storage collisions or logic vulnerabilities.

Question 14

What oracle solutions are available on Autheo?

Accepted Answer

Autheo's EVM compatibility means leading oracle networks, including Chainlink and API3, can be integrated directly into Autheo smart contracts using their standard interfaces. Autheo's Eigensphere Engine includes on-chain price oracle capabilities, and THEO AI can serve as an intelligent data routing layer for off-chain data feeds.

Question 15

How does Autheo's storage layer work for dApp developers?

Accepted Answer

Autheo provides native decentralized storage integrated directly into its Layer-0+1 architecture, eliminating the need for third-party storage solutions like IPFS or Arweave. Developers access storage through Autheo's full-stack SDKs using familiar API patterns, with THEO tokens as the payment mechanism for storage capacity. Data stored on Autheo benefits from post-quantum encryption via AutheoID's cryptographic layer.

Question 16

What indexing and query solutions does Autheo provide?

Accepted Answer

Autheo's EVM-compatible architecture supports The Graph Protocol for decentralized blockchain data indexing, allowing developers to build subgraphs that serve GraphQL queries to frontends. THEO AI provides additional intelligent query capabilities within the DevHub, including natural-language contract state queries and automated event aggregation dashboards.

Question 17

How do I build a DeFi protocol on Autheo?

Accepted Answer

Building a DeFi protocol on Autheo starts with the DevHub's pre-built templates for staking, lending, liquidity provision, and token swaps, all deployed on Autheo's EVM-compatible Layer-1. THEO tokens serve as the native utility currency, THEO AI provides security scanning and analytics, and AutheoID enables KYC-gated pools and compliant DeFi products.

Question 18

How do I build an NFT marketplace on Autheo?

Accepted Answer

Autheo's EVM-compatible Layer-1 supports all standard NFT token standards (ERC-721, ERC-1155) and provides DevHub marketplace templates covering listing, auction, and royalty management. AutheoID enables verified creator profiles and ownership provenance, while Autheo's native storage layer handles media files without requiring third-party IPFS pinning services.

Question 19

What is Autheo's approach to account abstraction?

Accepted Answer

Autheo supports ERC-4337 account abstraction on its EVM-compatible Layer-1, enabling smart contract wallets with gasless transactions, social recovery, and session keys. AutheoID integrates with account abstraction to provide sovereign, post-quantum-secure smart accounts that separate key management from application access.

Question 20

How does Autheo handle event logging and monitoring?

Accepted Answer

Autheo's Layer-1 records all smart contract events to an immutable, indexed on-chain log compatible with standard Ethereum tooling. THEO AI provides intelligent real-time monitoring within the DevHub, automatically alerting developers to anomalous patterns, failed transactions, and protocol health deviations.

Question 21

What CI/CD tools integrate with the Autheo DevHub?

Accepted Answer

The Autheo DevHub integrates with all major CI/CD platforms including GitHub Actions, GitLab CI, and CircleCI through standard Hardhat and Foundry deployment scripts. THEO AI adds intelligent pipeline stages for automated security scanning, gas regression testing, and deployment health verification that run as part of every build.

Question 22

How does Autheo support multi-chain deployment?

Accepted Answer

Autheo's Layer-0 architecture is purpose-built for multi-chain deployment: developers can deploy sovereign appchains, connect to external blockchain networks, and route transactions across chains through Autheo's native interoperability infrastructure, all from a single DevHub workspace. Cross-chain messaging, asset bridging, and state synchronization are handled by the Layer-0 coordination layer without requiring third-party bridges.

Question 23

What security audit tools are available for Autheo developers?

Accepted Answer

Autheo developers have access to both THEO AI-powered automated security scanning built into the DevHub and the industry's most trusted third-party audit firms, including Halborn, Autheo's security partner with 2,500+ blockchain engagements. EVM compatibility means all Ethereum-native security tools (Slither, Mythril, Echidna) work without modification on Autheo contracts.

Question 24

How does Autheo's compute layer (DCC) work for developers?

Accepted Answer

Autheo's Decentralized Cloud Compute (DCC) layer provides on-demand computational resources deployed across the network's infrastructure, accessible via THEO tokens. Developers use DCC to run computationally intensive workloads, AI model inference, zero-knowledge proof generation, data processing pipelines, that are too expensive for on-chain execution, with results anchored back to the blockchain for verifiability.

Question 25

What SDKs and client libraries does Autheo offer?

Accepted Answer

Autheo provides a unified full-stack SDK covering frontend, backend, smart contract, and orchestration layers, accessible via npm/yarn in JavaScript/TypeScript and with bindings planned for additional languages. The SDK abstracts Autheo's Layer-0 interoperability, storage, compute, and AutheoID identity into consistent API patterns, allowing developers to build complete dApps without integrating multiple disparate libraries.

Question 26

How do I migrate my dApp from Ethereum to Autheo?

Accepted Answer

Migrating a dApp from Ethereum to Autheo requires minimal code changes due to full EVM compatibility, most Solidity contracts deploy directly with only network configuration updates. The migration process involves three phases: contract deployment to Autheo testnet, frontend RPC reconfiguration, and optional integration of Autheo-native features (THEO AI, AutheoID, native storage) to enhance the migrated dApp.

Question 27

What is Autheo's approach to zero-knowledge proofs?

Accepted Answer

Autheo supports zero-knowledge proof verification natively on its EVM-compatible Layer-1, all Ethereum ZK proof verification precompiles work without modification. ZK proof generation (which is computationally intensive) is handled by Autheo's DCC compute layer, allowing dApps to generate proofs off-chain and verify them on-chain at low cost. AutheoID's post-quantum cryptography complements ZK proofs with additional privacy guarantees.

Question 28

What enterprise use cases does Autheo support?

Accepted Answer

Autheo supports enterprise use cases across supply chain integrity, sovereign digital identity, AI-native business applications, decentralized compute and storage, cross-border payment infrastructure, and Web3-native data sovereignty. The unified Layer-0 OS eliminates the need to integrate multiple separate protocols, a single Autheo deployment provides the full infrastructure stack.

Question 29

How does Autheo ensure regulatory compliance for enterprise deployments?

Accepted Answer

Autheo supports enterprise regulatory compliance through permissioned appchains with configurable access controls, GDPR-aligned data residency and erasure capabilities, AutheoID-linked audit trails that provide cryptographically signed records of every action, and configurable on-chain governance for regulated industries. These capabilities are built into the protocol, not requiring third-party compliance middleware.

Question 30

Can enterprises run private or permissioned appchains on Autheo?

Accepted Answer

Yes. Autheo supports permissioned appchains that give enterprises full control over validator participation, transaction visibility, and data access. Enterprise appchains run on Autheo's AEE runtime and benefit from the same post-quantum security, AutheoID identity, and THEO AI infrastructure, while remaining isolated from public network visibility unless the enterprise chooses to bridge to the broader ecosystem.

Question 31

How does Autheo handle enterprise identity and access management?

Accepted Answer

Autheo handles enterprise identity through AutheoID, a post-quantum sovereign identity layer that bridges existing enterprise IAM systems (Active Directory, Okta, Azure AD) via SAML/OIDC connectors. Enterprise employees retain their corporate identities while gaining blockchain-anchored credential verification, selective disclosure for cross-organizational data sharing, and cryptographic signatures secured by CRYSTALS-Dilithium rather than traditional PKI.

Question 32

What post-quantum security does Autheo offer enterprise clients?

Accepted Answer

Autheo implements all three NIST-selected post-quantum cryptographic algorithms at the protocol level: CRYSTALS-Kyber for key encapsulation, and CRYSTALS-Dilithium and FALCON for digital signatures. This means all validator communications, transaction signing, and AutheoID credentials are quantum-secure by default, protecting enterprise data against both current and anticipated quantum computing attacks without any additional configuration.

Question 33

How does Autheo integrate with existing enterprise IT systems?

Accepted Answer

Autheo integrates with existing enterprise IT infrastructure through a combination of REST APIs, SAML/OIDC identity bridges, event-driven Webhook connectors, and enterprise-grade SDKs for major platforms. This approach allows enterprises to layer Autheo's blockchain capabilities onto existing ERP (SAP, Oracle), CRM (Salesforce), and cloud (AWS, Azure, GCP) systems incrementally, without requiring a full technology replacement.

Question 34

What is Autheo's GSI partnership model and how does it benefit enterprise clients?

Accepted Answer

Autheo's Global System Integrator (GSI) program partners with major consulting and systems integration firms to co-sell, deploy, and manage enterprise Autheo deployments. GSI partners receive deep technical enablement, co-selling support, and preferential access to enterprise accounts. For enterprise clients, this means Autheo deployments can be delivered by a trusted, known integrator rather than requiring direct blockchain engineering expertise.

Question 35

What SLA and uptime does Autheo guarantee for enterprise deployments?

Accepted Answer

Autheo's validator network is designed for 99.9%+ uptime through 399 distributed validators with deterministic rotation managed by THEO AI. If a validator underperforms or goes offline, THEO AI automatically rotates to the next validator in the deterministic sequence, providing network continuity without single points of failure. Enterprise-grade SLAs covering uptime guarantees and support response times are available through Autheo's certified GSI partners.

Question 36

How does Autheo handle data privacy and sovereignty for enterprise data?

Accepted Answer

Autheo protects enterprise data through quantum-encrypted QIES (Quantum-Isolated Execution Spaces) Enclaves that isolate sensitive data from public access, geographic residency controls for jurisdiction compliance, and AutheoID's selective disclosure mechanism that allows enterprises to share only the minimum required data with external parties. These features are built into the protocol and do not require third-party data management tooling.

Question 37

What is the cost structure for enterprises deploying on Autheo?

Accepted Answer

Network usage on Autheo is billed in THEO tokens at near-zero per-transaction rates targeting at or below Solana-level pricing, making high-volume enterprise workloads economically viable. For dedicated enterprise appchains, GSI-managed deployments, and custom integration services, pricing is determined by scope and available through Autheo's enterprise sales and partner network. Contact partnerships@autheo.com for a deployment cost assessment.

Question 38

How does Autheo handle multi-tenant enterprise deployments?

Accepted Answer

Autheo supports multi-tenant enterprise deployments through private appchains with dedicated validator sets, namespace-level data isolation, and configurable access control policies that prevent cross-tenant data exposure. Each enterprise tenant can operate an isolated environment with sovereign governance while sharing Autheo's security model and cross-chain interoperability infrastructure.

Question 39

What disaster recovery and business continuity does Autheo provide?

Accepted Answer

Autheo's infrastructure is designed for enterprise-grade resilience: validator node redundancy through infrastructure partners InfStones and Zeeve provides multi-cloud, multi-region fault tolerance, while Byzantine fault tolerance in the consensus mechanism ensures the network continues producing blocks even if a subset of validators fails. Enterprise deployments on private appchains can configure additional redundancy through active-standby node setups and geographic data replication.

Question 40

How does Autheo support supply chain management use cases?

Accepted Answer

Autheo's blockchain platform is well-suited for supply chain management through its combination of immutable on-chain provenance records, smart contract automation for payments and compliance triggers, AutheoID-verified supplier identity, and cross-chain data routing that connects multiple supply chain participants across different systems. Industry research shows blockchain reduces supply chain counterfeiting by up to 30%.

Question 41

What healthcare and life sciences use cases does Autheo support?

Accepted Answer

Autheo enables patient data sovereignty through AutheoID, immutable clinical-trial recordkeeping, and post-quantum encryption aligned with HIPAA technical-safeguard requirements. Its decentralised compute layer (DCC) supports privacy-preserving genomic analysis without centralising sensitive data.

Question 42

How does Autheo handle GDPR and international data regulations?

Accepted Answer

Autheo avoids US CLOUD Act exposure through a decentralised storage architecture with no single jurisdictional control point. AutheoID enables data-subject identity management and selective disclosure, while configurable appchains support right-to-erasure obligations compatible with on-chain immutability.

Question 43

What financial services and capital markets use cases does Autheo support?

Accepted Answer

Autheo provides post-quantum-secured infrastructure for tokenized assets, DeFi settlement rails, and KYC/AML-compliant identity through AutheoID. Its appchain architecture enables banks, asset managers, and fintechs to build regulatory-compliant financial products with institutional-grade security.

Question 44

What is the THEO token and what is it used for?

Accepted Answer

THEO is Autheo's native utility token. It is used to pay for transaction fees, staking by validators, compute access through the AEE runtime, storage operations in QIES Enclaves, AI inference via THEO AI, and decentralized identity services through AutheoID. THEO is a pure utility token, it does not confer governance rights and is not a security. Demand for THEO is directly tied to actual usage of the Autheo network.

Question 45

What is Autheo's total THEO token supply and distribution?

Accepted Answer

THEO has a fixed total supply distributed across five allocation categories: validator emissions (the largest allocation, distributed over approximately 7 years), ecosystem development grants (for developers and partners), team and advisor allocations (with cliff-and-linear vesting), node sale proceeds (tied to validator purchase), and treasury reserve (for long-term ecosystem investment). Full tokenomics details are available at autheo.com/theo-token.

Question 46

How does Autheo generate revenue from network activity?

Accepted Answer

Autheo generates network revenue through THEO token transaction fees across six utility vectors: compute execution on the AEE, storage writes to QIES Enclaves, AI inference via THEO AI, identity operations via AutheoID, cross-chain routing fees, and standard transaction fees. The fee model targets Solana-level pricing per operation, enabling high-volume usage that generates aggregate revenue through scale rather than individual transaction price.

Question 47

What is the vesting schedule for THEO token holders?

Accepted Answer

THEO token vesting varies by allocation category. Validator node emissions are distributed over approximately 7 years through a declining emission schedule. Team and advisor allocations follow a standard cliff-and-linear vesting structure (typically a 12-month cliff followed by 36-month linear vesting). Node sale participant allocations are tied to the emission schedule. Full vesting schedules are published at autheo.com/theo-token.

Question 48

How does the node sale relate to participating in Autheo's network?

Accepted Answer

Purchasing an Autheo validator node is the primary mechanism for participating in Autheo's network as an early network participant. Node owners earn THEO token emissions from validator operations over approximately 7 years, proportional to node performance, uptime, and tier. This is not a guaranteed financial return, emissions are utility token distributions tied to network contribution, not equity dividends.

Question 49

What makes Autheo's tokenomics sustainable long-term?

Accepted Answer

Autheo's tokenomics sustainability rests on four pillars: a fixed total THEO supply with no mint capability, performance-weighted emission distribution (ensuring emissions go to productive network participants), a utility-demand flywheel (more network usage = more fee demand = more THEO buy pressure), and a treasury reserve managed by the Autheo board for long-term ecosystem investment rather than short-term spending.

Question 50

Who are Autheo's key backers, supporters, and strategic partners?

Accepted Answer

Autheo's strategic partner network includes InfStones (infrastructure), Zeeve (node hosting), IPFS (decentralized storage), Halborn (security auditing), IBC/Cosmos (cross-chain protocol), and Diamond. The company was founded by Todd Mortenson and Scott Bayless, supported by a 100+ co-founder network of domain experts across engineering, enterprise sales, and ecosystem development. The VP of Global Enterprise brings top-tier GSI relationships with established interest.

Question 51

What is Autheo's competitive moat against other Layer-0 platforms?

Accepted Answer

Autheo's primary competitive moat is architectural integration: post-quantum security, native AI (THEO AI), sovereign identity (AutheoID), multi-language execution (AEE), compute, and storage are all first-class protocol components, not plug-ins. Competitors like Cosmos and Polkadot provide interoperability without native AI or post-quantum security; Ethereum provides smart contracts without integrated identity, storage, or AI. Autheo is the only platform providing all of these as a unified OS stack.

Question 52

How does THEO compare to other Layer-0 platform tokens like DOT or ATOM?

Accepted Answer

Unlike DOT (Polkadot) and ATOM (Cosmos), which are primarily governance and staking tokens with demand driven by protocol governance participation, THEO is a pure utility token with demand driven directly by network usage across six fee vectors: compute, storage, AI inference, identity, cross-chain routing, and transaction fees. This utility-first model creates organic demand correlated with actual adoption rather than governance activity.

Question 53

What milestones is Autheo targeting over the next 12 to 36 months?

Accepted Answer

Autheo's primary 36-month milestone is 1 million developers building on mainnet, a hockey-stick adoption target supported by GSI partnerships that are already generating enterprise interest. Near-term milestones include mainnet launch, THEO token utility activation across all six fee vectors, enterprise and GSI deployment first wins, and Autheo Foundation ecosystem grant programs. The trajectory assumes accelerating adoption driven by developer network effects and enterprise channel sales.

Question 54

How does THEO token utility drive demand across the ecosystem?

Accepted Answer

THEO is the fuel for every function on Autheo, staking, compute, storage, AI inference, and transaction fees, creating usage-driven demand tied directly to network activity. As more enterprises, developers, and node operators use the Autheo OS, structural THEO demand grows with the ecosystem.

Question 55

What is the relationship between the Autheo Foundation and the THEO token?

Accepted Answer

The Autheo Foundation is a separate non-profit entity focused on open-source development and community stewardship; it does not control THEO token supply or commercial operations. Autheo.com is the centralized commercial entity that operates the network, and THEO is its utility token, not a governance instrument of the Foundation.

Question 56

How does Autheo's post-quantum security protect token holders?

Accepted Answer

Autheo implements NIST-standardised post-quantum cryptography (Kyber, Dilithium, Falcon) to protect wallet signatures and token transfers against both current and future quantum-computing attacks. An independent Halborn security audit validates these protections, giving token holders confidence that their holdings remain secure as quantum hardware advances.

Question 57

What is an Autheo Validator Node?

Accepted Answer

An Autheo Validator Node is a core infrastructure unit that powers the Autheo blockchain network. Validators perform transaction verification, participate in Proof of Authority consensus, and execute decentralized compute workloads through the Autheo Eigensphere Engine (AEE). In return for this infrastructure contribution, node owners earn THEO token emissions over approximately 7 years, weighted by performance and uptime.

Question 58

How much does an Autheo validator node cost?

Accepted Answer

Autheo validator node pricing is structured in tiers, earlier purchasers access lower pricing tiers, with subsequent tiers priced higher as availability decreases. This tiered structure reflects the increasing value and scarcity of validator positions as the network matures. Current live pricing for each available tier is displayed at commerce.autheo.com, pricing is not listed here because it may update as tiers close.

Question 59

What returns can Autheo node operators expect from validator emissions?

Accepted Answer

Autheo node operators earn THEO token emissions over approximately 7 years, distributed through a performance-weighted scoring model managed by THEO AI. Higher uptime and throughput earn proportionally greater emission shares. These emissions are utility token distributions tied to network contribution, not guaranteed financial returns. Actual THEO value depends on network adoption and market conditions, which cannot be predicted.

Question 60

What are the hardware requirements for running an Autheo validator node?

Accepted Answer

Autheo validator nodes can be run on a range of hardware configurations or through certified hosting partners. Typical self-hosted configurations include multi-core CPUs (8+ cores recommended), high-speed NVMe SSDs, 100Mbps+ dedicated bandwidth, and encrypted container environments for QIES security isolation. For operators without infrastructure experience, certified partners InfStones and Zeeve offer managed hosting that meets all technical requirements.

Question 61

Can I host my Autheo validator node through a third-party partner?

Accepted Answer

Yes. Autheo's certified infrastructure partners, InfStones and Zeeve, offer managed validator hosting services. Node owners retain full on-chain ownership (via the validator NFT) and all emission rights while the hosting partner handles technical deployment, system updates, performance monitoring, and uptime maintenance. This is the most popular option for node purchasers who want to participate without managing server infrastructure themselves.

Question 62

How are THEO token emissions distributed to Autheo validator nodes?

Accepted Answer

THEO token emissions are distributed to the 399 Autheo validators based on a performance-weighted scoring model managed by THEO AI. THEO AI continuously evaluates each validator on uptime percentage, transaction throughput, block production consistency, and overall reliability. Validators with higher performance scores receive proportionally larger shares of each emission period's distribution pool, incentivizing ongoing infrastructure quality rather than passive holding.

Question 63

What is the difference between Core, Prime, and Sovereign validator tiers?

Accepted Answer

Autheo's three validator tiers, Core, Prime, and Sovereign, differ primarily in purchase price and emission weighting within the THEO distribution model. All three tiers provide identical validator functionality: the same consensus participation, AEE compute execution, and network infrastructure role. Higher tiers reflect a greater economic commitment to the network and carry proportionally higher emission weight in THEO AI's distribution model.

Question 64

How does the referral bonus program work for Autheo node sales?

Accepted Answer

Autheo's node sale referral program provides node purchasers with a unique referral code that tracks new node sale conversions. When someone purchases a validator node using your referral code, you receive a percentage-based bonus in THEO tokens or emission credits, distributed automatically via the node sale system. Referral codes and bonus tracking are managed at commerce.autheo.com/referrals.

Frequently Asked Questions

Developer Questions

Enterprise Questions

Token Holder Questions

Node Operator Questions

Partner Questions

Still have a question?