Space and Time
Use Case: Airdrop

Ship trustless airdrops with zero-knowledge proofs

No Merkle trees. No backend. Publish your allocation list as a SQL table, deploy a claim contract, and let Proof of SQL verify every payout onchain. Claimants get cryptographic proof that their reward was read from your data. Not spoofable, fully auditable.

Transparent allocations
Your allocation table lives onchain. Anyone can verify who is eligible and for how much.
Proven payouts
Every claim triggers a ZK-verified SQL query. The contract only pays out when the proof checks out.
No backend required
No server, no API keys, no admin multisig. Deploy once and walk away.

How It Works

Traditional airdrops rely on Merkle trees or centralized APIs to validate claims. This approach replaces both with a verifiable SQL query. Your allocation data is the source of truth, and Proof of SQL is the verification layer.

1. Publish your allocation table

Upload your allocation CSV and write it to an onchain SXT Chain table. This becomes the canonical, publicly auditable source of who gets what.

2. Deploy a claim contract

We generate for you an airdrop claim contract. It can be used on any chain supported by the SXT Network, and it can use as the airdrop reward token any ERC-20 token you want to configure.

3. Users claim with ZK verification

A claimant calls claim() on your contract. It sends the query to SXT, which executes the SQL and returns a zero-knowledge proof that the result is correct.

4. Verified payout settles onchain

The callback delivers the proven allocation amount. If valid and funded, the reward token is transferred to the claimant.

Why Proof of SQL?

Most airdrops use Merkle trees: generate a tree off-chain, publish the root, and let users submit proofs. It works, but it has real limitations. Here's how a Proof of SQL airdrop compares.

Merkle TreeProof of SQL
Allocation dataOff-chain JSON/CSV, root published onchainFull table stored on SXT Chain, queryable by anyone
AuditabilityRequires trusting the tree generatorFully transparent. SQL table is public
UpdatableNew root = new contract or migrationInsert rows to the same table, same contract
Claim UXUser must obtain their proof from an APIUser just calls claim(). No proof needed
BackendAPI server required to serve proofsNo backend. Contract + SXT handle everything
VerificationMerkle inclusion proof (hash chain)Zero-knowledge proof of correct SQL execution

Connect your wallet to complete this tutorial

Connect your wallet to run this builder.

Step 1: Publish Your Allocation Table

Paste or upload a CSV with address,amount columns. Each row is validated, totals are computed, and the data is written to AIRDROP_YOUR_ADDRESS.AIRDROP_LIST on SXT Chain.

Namespace Prefix

Full: AIRDROP_YOUR_ADDRESS

Table Name12/64
Valid Allocations
2
Total Allocation
1450.5
Estimated Credits
40.001
Namespace + table + insert
Available SXT Chain credits:
0
AddressAmount
0x1111111111111111111111111111111111111111250
0x22222222222222222222222222222222222222221200.5

Step 2: Choose Your Reward Token

Pick the ERC-20 token claimants will receive. Use an existing token for a real airdrop, or deploy a demo token to test the full flow end-to-end.

Step 3: Deploy the Claim Contract

Deploy a self-contained claim contract with your reward token. The proof plan for your SQL query is compiled automatically and embedded in the contract.

Network
Ethereum
Claim deposit
100 SXT
Callback gas
2M / 20 gwei
Query Router
0x220a7036a815a1Bd4A7998fb2BCE608581fA2DbB

Step 4: Fund and Share

Transfer reward tokens into the contract and share the claim URL with your community. The suggested amount covers your full allocation. Increase it for reserves if needed.

Important Notes

  • Each claim costs the claimant 100 SXT as a query payment deposit. This covers the Proof of SQL execution and verification. Excess is refunded.
  • Permit flow: available on this chain. Claimants sign once instead of approving + claiming.
  • The deployed contract is immutable. Double-check your allocation table, reward token, and query plan before deploying.
Downloaded templates are reference code. Audit thoroughly before production use.