The web3 backend for SQL-based applications. 99% of websites that matter run on SQL. Seal gives them decentralization, privacy, and post-quantum security — without changing how they work.
# Deploy your app seal app deploy --name myapp.seal --schema schema.sql # Query from anywhere seal sql "SELECT * FROM myapp.users" --node http://node:8545 # Your schema.sql is just PostgreSQL CREATE TABLE users ( id BIGINT PRIMARY KEY, email TEXT NOT NULL, balance BIGINT DEFAULT 0 );
ML-DSA-65, ML-KEM-768, SHA3-256. NIST-standardized. Future-proof against quantum computers. No classical crypto on-chain.
CREATE TABLE, INSERT, SELECT, JOIN, WHERE. Row-level security with CREATE POLICY. Your existing SQL skills work here.
Public tables, RLS-protected tables, and private tables encrypted at rest. MPC aggregates and ZK proofs for private data access.
Each app gets its own shard. Nodes choose which namespaces to serve. Scales horizontally as the network grows.
Every query result is backed by a Merkle proof against the state root. ZK proofs via RISC Zero / SP1 for privacy-preserving verification.
Built-in limit order book. Create custom tokens, trading pairs, and place orders. All signed with ML-DSA-65.
| Today | With Seal |
|---|---|
| You manage your own database servers | The network manages replication for you |
| You build auth from scratch | Cryptographic identity built-in (ML-DSA) |
| You trust your hosting provider with your data | Data encrypted at rest, verified by math |
| You hope your backups work | Replication across multiple nodes by default |
| Users trust you not to tamper with data | Merkle proofs and ZK proofs verify everything |
| Vulnerable to quantum computers (eventually) | Post-quantum from day one (ML-DSA, ML-KEM, SHA3) |
| Locked to a cloud vendor | Decentralized, no single point of failure |
All signing with ML-DSA-65 post-quantum signatures. SQL, tokens, DEX, MPC, ZK proofs.
Tests passing
Kani proofs
Fuzz targets
CVEs audited
git clone https://github.com/SealProjectDAO/seal-dao-public.git cd seal-dao-master cargo build --release -p seal-node -p seal-cli
./target/release/seal-node --slots 0 --rpc-port 8545
Runs forever, serves JSON-RPC on port 8545.
seal-cli sql "SELECT * FROM users" --node http://localhost:8545 seal-cli sql "INSERT INTO users VALUES (3, 'charlie', 750)" --node http://localhost:8545
curl -s localhost:8545 -H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","method":"seal_querySql",
"params":{"sql":"SELECT * FROM users"},"id":1}'
| Method | Auth | Description |
|---|---|---|
seal_querySql | No | Execute a read-only SQL query |
seal_submitSql | ML-DSA | Submit a write (INSERT/UPDATE/DELETE/CREATE) |
seal_getHeight | No | Get current block height |
seal_getStateRoot | No | Get current state root hash |
seal_getBlock | No | Get block by height |
seal_deployNamespace | ML-DSA | Deploy a new app namespace |
seal_createToken | ML-DSA | Create a custom token |
seal_mintToken | ML-DSA | Mint tokens to an address |
seal_createPair | ML-DSA | Create a DEX trading pair |
seal_placeOrder | ML-DSA | Place a limit order (bid/ask) |
seal_getOrderBook | No | View order book depth |
seal_mpcAggregate | Optional | Run MPC aggregate on private data |
seal_zkProve | Optional | Generate ZK proof (RISC Zero / SP1) |
PostgreSQL-compatible subset. Your existing SQL works.
CREATE TABLE, DROP TABLE INSERT, UPDATE, DELETE SELECT with WHERE, ORDER BY, LIMIT JOIN (INNER, LEFT) BIGINT, TEXT, BOOLEAN PRIMARY KEY, NOT NULL, DEFAULT CREATE POLICY (RLS) CREATE NAMESPACE
ALTER TABLE CREATE INDEX Subqueries Aggregate functions (SUM, AVG, COUNT) via MPC for private tables GROUP BY, HAVING Foreign keys Views
Algorand-style consensus: VRF leader election + committee voting. No mining, no GPUs.
| Requirement | Minimum | Recommended |
|---|---|---|
| CPU | 4 cores | 8 cores |
| RAM | 16 GB | 32 GB |
| Storage | 500 GB NVMe | 1 TB NVMe |
| Network | 100 Mbps | 1 Gbps |
| Stake | 1,000 SEAL | 10,000+ SEAL |
# Build cargo build --release -p seal-node # Start validator ./target/release/seal-node --slots 0 --port 4001 --rpc-port 8545 \ --bootstrap-peers /dns4/boot1.seal-dao.network/tcp/4001
Emission: 10% year 1, declining to 2% floor. Split between block proposer and committee.
Dynamic fees (planned). 50% burned, 50% to proposer. High usage = deflationary.
Double-propose or double-vote (planned) = stake slashed. 21-epoch unbonding period.
SEAL token holders. Vote on proposals with conviction voting (7 tiers). Delegation with 4% per-delegate cap.
7-11 members. Whitelist emergency proposals, veto dangerous changes. Term-limited.
Active validators. Advisory endorsement on operational proposals. SLA-based veto power.
| Track | Approval | Quorum | Timelock |
|---|---|---|---|
| Runtime Upgrade | 75% | 50% | 7 days |
| Treasury Spend | 60% | 40% | 3 days |
| Parameter Change | 66% | 33% | 2 days |
| Community Grant | 50% | 25% | 1 day |
| Emergency | 90% | 67% | None |
| Text / Signal | 50% | 10% | None |
| Tool | What it proves | Status |
|---|---|---|
| Lean 4 | Merkle tree invariants, VRF uniqueness | 0 sorries |
| Rocq/Coq | Token conservation, RLS non-bypass, SQL transitions | 0 Admitted |
| Kani | Overflow, bounds, arithmetic (16 harnesses) | All pass |
| Miri | Undefined behavior detection | Pass |
| cargo-fuzz | Crash-free on random input (9 targets) | 0 crashes |
| TLA+ | Consensus safety and liveness | Spec + trace |
| Crate | Purpose |
|---|---|
seal-crypto | ML-DSA, ML-KEM, SHA3, address derivation |
seal-vrf | PQ-VRF, LaV many-time VRF, lattice VRF |
seal-threshold | Ringtail lattice threshold signatures, NTT, Shamir |
seal-consensus | VRF election, committee voting, fork choice, epochs |
seal-sql | SQL parser, engine, RLS, namespaces |
seal-merkle | Merkle tree, persistent RB-tree indexes |
seal-storage | Block store, state pruning, HAMT |
seal-token | Staking, fees, emission, treasury, governance |
seal-p2p | libp2p GossipSub, mDNS, ML-KEM transport |
seal-zk | RISC Zero, SP1, GPU acceleration, batch proofs |
seal-mpc | SPDZ private aggregation, PSI |
seal-bridge | Solana + Stellar bridge observers |
seal-node | Node binary, RPC server, disk persistence |
seal-cli | CLI: dev, demo, sql, migrate, app deploy |
Source code, issues, pull requests. 17 crates, 804 tests, formal verification.
Developer chat, validator coordination, governance discussion. Coming soon
Announcements, releases, ecosystem updates. Coming soon
# Clone and build git clone https://github.com/SealProjectDAO/seal-dao-public.git cd seal-dao-master cargo build && cargo test # Run the full verification suite ./scripts/ci.sh quick # build + 804 tests + clippy ./scripts/ci.sh # + Kani + Miri + fuzz + audit
See BUG-BOUNTY.md for the security bounty program.