🛸Validator

Validators serve as the central nervous system for space and time, providing a set of microservices to facilitate platform functionality. Validators offer a means for data to enter the system (e.g., blockchain indexing) and exit the system (e.g., smart contracts).

Routing - Supports transaction and query interactions with the decentralized data repository network.

Streaming - Acts as a receiver for high-capacity customer streaming (event-driven) workloads.

Consensus - Provides high-performance Byzantine fault-tolerant capability for data entering and exiting the platform.

Query Proof - Provides SQL proofs to the platform.

Table Anchors - Offers storage proofs to the platform by anchoring tables on-chain.

ORISacle - Supports Web3 interactions, including smart contract event listening and cross-chain message passing/relaying.

Security - Prevents unauthorized and unauthenticated platform access.

Validator Services

Routing

Routing supports transaction and query interactions with the decentralized data repository network. It provides clients with an interface (via REST and GraphQL APIs and JDBC/ODBC) to interact with their data. Clients execute transactions and queries through this abstraction, as if connecting to a single infinitely available cluster. Behind the scenes, each request is routed to the appropriate data repository instance, handling data distribution across the entire network and any potential failures.

Streaming

Streaming acts as a receiver for high-capacity customer streaming (event-driven) workloads. The Streaming component of Validator provides a persistent and fault-tolerant service for Kafka, allowing user data to flow into the platform and be flexibly merged into stored data.

Consensus

Consensus provides high-performance Byzantine fault-tolerant capability for data entering and exiting the platform. Data enters the platform through redundant ETL processes (such as blockchain indexing) and submits its output. Then, consensus service instances running across different validators reach consensus on the input to produce a single output. Consensus ensures that incorrect executions or malicious activities do not impact critical platform data.

Query Proof

Query Proof provides SQL proofs to the platform. When users insert data into a table, a digital fingerprint (hash) is updated to represent the data. Then, when users request tamper-proof queries, the database engine calculates the result and an encrypted proof. Finally, the proof returned from the database is verified based on the digital fingerprint (novel SQL proof based on SxT) to ensure the query's correct execution. Query Proof goes hand in hand with consensus: the proof undergoes redundant verification and enters consensus, ensuring validators cannot maliciously manipulate data, providing end-to-end tamper-proof query execution for end-users.

Table Anchors

Table Anchors provide storage proofs to the platform by anchoring tables on-chain. When data enters the platform, the Table Anchors component updates the Merkle tree, whose root hash is periodically anchored to a smart contract. This allows validators to audit the data repository cluster without transferring large amounts of data. This process also paves the way for periodic self-auditing. When the root hash is anchored on-chain through the smart contract, an event is triggered. In turn, the SxT index primarily blockchain (including the SxT smart contract anchoring the Merkle tree root hash) offers an efficient, secure method for data verification.