Unleashing Peak Blockchain Velocity
A centralized, high-throughput blockchain architecture for trusted environments, engineered for speed and EVM-compatibility.
YaoVerse
Traditional EVM Chain
Architecture & Components
An interactive guide to the specialized microservices that power YaoVerse.
YaoPortal (曜阙)
Role: API Gateway & Transaction Ingress
The universal gateway to the YaoVerse ecosystem. It provides a standard Ethereum JSON-RPC interface, ensuring seamless compatibility with existing tools like MetaMask, Hardhat, and Web3.js. Its primary function is to validate incoming transactions and immediately offload them to the message queue, allowing for extremely high ingress capacity and instant response times to the client.
- Standard JSON-RPC interface for EVM compatibility.
- Rapidly offloads transactions to RocketMQ.
- Routes read-only requests (`eth_call`) for efficient data retrieval.
YaoChronos (曜史)
Role: Centralized Sequencer
The authoritative "heart" of the system. YaoChronos is the sole component responsible for ordering transactions, which eliminates the network and computational overhead of BFT consensus algorithms. It consumes raw transactions from the queue, arranges them into a definitive sequence, and publishes these ordered blocks for execution. The throughput of YaoChronos dictates the theoretical TPS limit of the entire system.
- Provides global, unambiguous transaction ordering.
- Eliminates the need for complex consensus protocols.
- Implemented in a Leader-Follower model for high availability.
YaoVulcan (曜焱)
Role: Parallel Execution Engine
The powerhouse of the network. YaoVulcan is a scalable cluster of stateless nodes that execute the transaction blocks produced by YaoChronos. Because the blocks are pre-ordered, execution can be perfectly parallelized. Each Vulcan node contains the embedded YaoOracle state library, enabling it to access world state data at nanosecond-level speeds from its local in-memory cache.
- Executes ordered blocks in a load-balanced, parallel fashion.
- Stateless design allows for rapid horizontal scaling.
- Utilizes the embedded YaoOracle for ultra-low latency state reads.
YaoArchive (曜典)
Role: Persistence & Cache Invalidation Service
The keeper of records and the guarantor of consistency. YaoArchive is the only service that writes data to the TiDB database. It consumes the execution results from the Vulcan cluster and commits them atomically using ACID transactions. Crucially, after a successful write, it broadcasts a precise list of modified state keys to a dedicated message queue topic, triggering a system-wide cache invalidation to maintain data consistency across all Vulcan nodes.
- Sole write-access to the database, ensuring data integrity.
- Uses ACID transactions for atomic state updates.
- Publishes cache invalidation messages to maintain consistency.
Powered by an Elite Tech Stack
Leveraging battle-tested, cloud-native technologies for unmatched reliability and scale.
TiDB Cluster
The horizontally-scalable, MySQL-compatible distributed database that acts as our Source of Truth. Provides ACID guarantees, infinite scaling, and powerful SQL querying capabilities.
Redis Cluster
The high-performance, in-memory L2 cache. It shields the database from excessive read requests and accelerates node warm-up by providing a shared pool of hot data for the entire Vulcan cluster.
RocketMQ Cluster
The neural network of YaoVerse. This enterprise-grade message queue decouples all services and provides critical dual-mode messaging: Clustering for load-balancing and Broadcasting for cache invalidation.
The YaoOracle Advantage
Our core innovation that transforms state access from a bottleneck into a superpower.
From Milliseconds to Nanoseconds
YaoOracle is an embedded, three-level caching library that brings state data directly into the memory of each execution node. This eliminates network latency for over 99% of state reads, allowing the EVM to run at its theoretical maximum speed.
Real-Time Consistency, Simplified
After a successful write to TiDB, YaoArchive broadcasts the precise keys of modified data via RocketMQ. Every single YaoVulcan node receives this message, surgically removing stale entries from its local L1 cache. This creates a self-healing, consistent, and ultra-performant data layer.