Scott Dykstra Profile picture
Jul 15 3 tweets 2 min read Read on X
Welcome new SXT community members! The Gigabrains are on fire this month.

A few months ago, @SpaceandTimeDB delivered the industry's first sub-second ZK proof, allowing smart contracts to execute trustless SQL queries
🏎️💨🔥

𝗛𝗼𝘄 𝗱𝗼𝗲𝘀 𝘁𝗵𝗶𝘀 𝗽𝗼𝘄𝗲𝗿𝗳𝘂𝗹 𝗻𝗲𝘄 𝗽𝗿𝗶𝗺𝗶𝘁𝗶𝘃𝗲 𝗰𝗵𝗮𝗻𝗴𝗲 𝗰𝗿𝘆𝗽𝘁𝗼 𝗳𝗼𝗿𝗲𝘃𝗲𝗿? 👇
2/ Space and Time ($SXT) is a decentralized data warehouse that lets smart contracts run full SQL against custom offchain data and get a cryptographically proven answer in < 1 s. No centralized indexers, no oracle trust.... just verifiable aggregations of data on demand.

How it works:
Your contract emits a query job → client contract calls the SXT relayer contract, which emits an event on mainnet for the world to see: "HEY I HAVE A QUERY TO RUN AND A PAYMENT FOR ANYONE THAT FULFILLS IT!"

SXT executes it, wraps the result in a Proof of SQL (ZK-proof), and the relayer contract returns an already-verified query result to the client contract next block via a callback function. Fast, cheap, tamper-proof. 🔒📈

Queries can be executed against a client's own custom tables that they inserted their own signed data into, or tamperproof tables of indexed data from popular chains.
3/ What can you build?
• Live DEX indices 📊
• DAO profit splits 💰
• AI trade guardrails 🤖🚦
• TVL-based airdrops 🎁
• Auto LTV risk 📉
• Liquidity rebalancer 🌉
• Treasury buybacks 🔄
• Funding-rate oracle 🪙
• KPI options 🎯
• Predict-market settlement ⚖️

•Live DEX pricing or DeFi Yield Indices– Query every Uniswap & Hyperliquid trade in the last 5 mins, prove the median, and settle perps without any sketchy TWAP logic.

•DAO profit splits – Weekly SQL over protocol fees returns a proof; if revenue ≥ target, the contract self-distributes LP rewards: no multisig or CRON-bot required.

•AI trade guardrails – Before an on-chain AI agent buys a token, a guardrail contract proves m-cap > $50M and 24h volume > $5M; failing the proof, the trade reverts.

•TVL-based trustless airdrops – SXT proves each wallet’s cumulative deposits/stakes; the airdrop contract mints rewards directly, ending CSV drama and list tampering.

•Auto-LTV risk checks – A lending pool proves “borrowers with health < 1.2 across chains” in real time; if any exist, the contract instantly lowers max LTV or pauses draws across all chains where the lending protocol is deployed.

•Liquidity rebalancer – A pool proves imbalance > 20 % between chains/AMMs and auto-moves capital to restore peg without human intervention.

•Treasury buybacks – If 30-day revenue minus spend is positive (proved by SQL), the treasury contract executes a market buyback of its own token.

•Funding-rate oracle – Periodic SQL over perp DEX funding tables outputs a ZK-verified average, letting synths or lenders settle fairly and on-chain.

•KPI options – When SxT proves daily active wallets hit 10k, the option contract automatically vests; no trusted attestor needed.

•Prediction-market settlement – Query an official election/results API, get a proof, and close the market trustlessly the very next block. Even better is trustless results based on predictions around onchain activity like future gas prices.

THE TICKER IS $SXT 🚀⏳

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Scott Dykstra

Scott Dykstra Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @chiefbuidl

Jun 23, 2024
𝗪𝗵𝘆 𝗶𝘀𝗻'𝘁 𝘁𝗵𝗲 𝗗𝗲𝗳𝗲𝗻𝘀𝗲 𝗗𝗲𝗽𝗮𝗿𝘁𝗺𝗲𝗻𝘁 𝘂𝘀𝗶𝗻𝗴 @SpaceandTimeDB?

A lot of folks have been telling us recently that @SpaceandTimeDB should deploy our ZK proof of SQL technology with the defense department. Although this is not our focus or something we plan to pursue, it brings up a larger discussion on the future of verifiable compute and how pervasive it will be to society.

TLDR:
1) ZK replaces BFT consensus for just about everything except sequencing
2) the ability to prove to party A that party B didn't tamper has broad applicability in tradfi and defense, but will be slow to adopt in both verticals for different reasons, explained below
3) AI agents will require ZK proofs to pass messages (output of computations) between eachother without manipulation. ZK is much more conducive for autonomous agents which swiftly transact programmatically than for clumsy humans.
4) In conclusion, any vertical where the negative financial/security/legal/personal/defense impact of data manipulation outweighs the non-zero computational overhead of ZK proving... will eventually leverage it

Let's get into it 🧵👇
1) Bitcoin brought about the idea of BFT consensus for sequencing and inserting rows of transaction data into a globally replicated database, to ensure that database can never be tampered and data can never be lost. Ethereum expanded on this idea, with simple JavaScript-like scripts called Smart Contracts that execute over the "database inserts" of the chain like a stored procedure, to govern the writes to its globally replicated database of transactions. These scripts together can form decentralized applications that are *highly inefficient* yet tamper-resistant when executed redundantly across the various global chain validators.

But those scripts (Smart Contracts) don't need to be executed hundreds/thousands of times redundantly prior to BFT consensus ✨if✨ zero knowledge VMs can instead execute them only once and prove their output. But here's the big question: where does their input data come from? Who sequences the transactions ("database inserts") in a fair, censorship-resistant way? BFT consensus is still needed to complement ZK in that aspect.

Now, you're probably thinking... what does this have to do with the defense sector? 🤨
2) In other verticals outside of cryptocurrency, centralization of an org's resources is generally necessary and encouraged. Banks want to own their data and keeps their books private. Military organizations want full root-level control over all machines in their network. But what about multiple military branches communicating (i.e. joint operations between Air Force and Homeland Defense, or joint ops between multiple allied nations)? What about multiple banks in a consortium communicating today's mark-to-market with eachother to set global bond prices?

Yes, each bank wants centralized control of their local database/compute resources (their books), but it would solve a lot of market inefficiencies (and frankly, fraud) if banks prove to the other banks that they are not lying about their PnL. 💸 They won't need BFT consensus to sequence transactions, as they'd generally want to do this in a centralized manner to have complete control of which transactions get added to their local ledgers (which, to be honest, is very problematic--- but ZK compute doesn't solve this specific issue)... but they DO want the ability to verify that the other banks have calculated their mark-to-market fairly.

Similarly, the Department of Defense is not necessarily looking to decentralize via a global network of commodity node operators gossiping BFT consensus, but rather are looking to allow machines on military base A to prove to machines on military base B that the output of a computation (passed to base B as a cypher via encrypted messaging, usually) was done correctly and has not been manipulated by state actors or foreign enemies that have breached.

Zero knowledge virtual machines are the future of computation, specifically for these secure environments where there is significant skin in the game-- where there is something at risk of manipulation and not all parties can be trusted (bond prices, your wallet balance, or the nation's security)-- where the costs and computational overhead of ZK are far outweighed by what's at stake.

Unfortunately, though, these sectors move extremely slow to adopt technologies which, at first glance, limit their ability to control data in a centralized way. Ironically, ZK technology would give these orgs MORE control (the ability to verify every calculation or data point they ingest), but since ZK has been lumped in with web3's decentralization narrative, a sales cycle would be painfully slow. Banks don't want 3rd parties to verify their own books, they just want to verify everyone else's. 😂 Defense organizations don't want anyone else to be able to verify their work-- they just want to be able to verify that the computational outputs being passed between machines in their centralized global network haven't been compromised.
Read 4 tweets
Dec 13, 2023
Lot of discussion recently with crypto minds I respect about AI x Blockchain.

Here is my thesis as to why autonomous agents will be transacting primarily onchain in a couple years… 🧵
1) PKI INFRA. First off, this isn’t primarily about blockchain, but more about private keys. 🔑💳

The human instructing an autonomous agent has a credit card, but the AI does not. It has a private key.

Tbf, it could lever payment APIs like Stripe to transact digitally, but Stripe is regulated to Valhalla and is already starting to require human-approval-in-the-loop due to compliance oversight.

Even if I’m wrong, consider that PKI infra is self-programable (rather than being at the mercy of a 3rd-party API) which lends enormous benefit to the code-generating bot at your bidding. More on this later.
2) Procuring online services.

AI agents must autonomously purchase computing and storage services from hypervisors in order to complete their instructed goals. Doing so with the credit card of the human who instructed them is problematic…

Imagine a “team” of hundreds of agents working together to accomplish a goal while you’re away for the day. You hit the slopes ⛷️and tell your AI to “build a Web3 app for sports betting” while you’re gone. They must find and subscribe to a 3rd-party sports data API, set up a database, deploy a contract, maybe write some server-side, host a frontend somewhere, etc etc… none of which is local on your laptop (or your in-house anarchist GPU cluster), meaning it’s purchased from a 3rd party. If you hand the agent your credit card and set a spending limit for the day while they work, Chase Fraud department is gonna text you while you’re on the lift. No dice. L.
Read 8 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(