Deep Dive
1. Purpose & Value Proposition
Smart contracts operate in a data vacuum; they cannot natively access historical records, aggregate data across chains, or process complex analytics. Space and Time fills this gap by becoming a verifiable compute layer. It ingests on-chain and off-chain data, processes it into tamper-proof tables, and delivers query results back to smart contracts with a cryptographic guarantee that the data and computation are correct (Space and Time). This enables a new generation of sophisticated, data-driven decentralized applications (dApps) in DeFi, gaming, and AI.
2. Technology & Architecture
The network is a three-piece, decentralized system. Indexers pull raw data from major blockchains in real-time. Validators then verify this data, participate in a Byzantine Fault Tolerant (BFT) consensus, and sign cryptographic commitments to its state. Provers run the key innovation: Proof of SQL. This ZK coprocessor allows a single node to execute a standard SQL query and generate a succinct zero-knowledge proof that the result is accurate and derived from the validated data (Space and Time). The proof is verified on-chain before the smart contract uses the result, creating an end-to-end verifiable pipeline.
3. Tokenomics & Ecosystem Utility
The SXT token is the economic engine of this decentralized network. Validators must stake SXT as collateral to participate in consensus and sign data commitments; malicious behavior risks slashing their stake. The token is also used for all protocol payments: developers pay in SXT to run queries or insert data, with fees distributed to validators and data contributors (Space and Time). This model aligns incentives to secure the network and supply high-quality data, aiming for a self-sustaining ecosystem.
Conclusion
Space and Time is fundamentally a decentralized infrastructure project that brings verifiable, large-scale data compute to blockchain, anchored by the SXT token's staking and payment utilities. Will its Proof of SQL become the standard primitive for trustless data access in Web3?