Open source · Apache-2.0 · on the DuckDB Community Extensions registry

Squeeze the compute
you already own.

Duckton turns idle laptops, desktops, and servers into a secure, peer-to-peer DuckDB compute grid over QUIC. Queries run redundantly across independent nodes, results are verified byte-for-byte by a quorum, and nodes can optionally earn — settled directly on The Open Network (TON), with no central broker.

# install + run a verified query, out of the box
INSTALL duckton FROM community;
LOAD duckton;
SELECT * FROM p2p_query('SELECT 42 AS x');

Live network — real nodes

connecting…

Real, not a simulation — independent node processes with distinct Ed25519 identities, running real distributed p2p_query jobs across each other over QUIC with quorum verification. Counts climb live as jobs execute.

Online host nodes
independent peers
Real jobs executed
distributed + verified
Verified
quorum-agreed
Avg latency
cross-node commit

A trustless query grid, in plain SQL

No central broker sits in the data path. You broadcast a query; independent nodes execute it and cross-check each other. You rely on the answer, not on any single machine.

Use what you already have

Idle laptops, desktops, and servers become independent compute nodes — privately inside your company network, or across the world.

Verifiable by quorum

Every query runs redundantly. Results are reduced to a canonical hash and accepted only when a configurable quorum agrees byte-for-byte.

Secure by design

Mutually-authenticated QUIC (TLS 1.3), Ed25519 node identity, OS-sandboxed execution, and short-lived scoped credentials — hosts never hold your keys.

Earn on TON, no middleman

Public jobs are free and fully off-chain. Paid jobs settle through a per-job on-chain escrow on TON — nodes set their own rates.

How it works

01

Fund & submit

The requester broadcasts a query over QUIC and, for paid jobs, locks a bid in a per-job escrow on TON.

02

Execute & read

Independent nodes run the query in parallel, reading data straight from your encrypted object storage.

03

Verify by quorum

Each result is hashed; the first answer a quorum agrees on byte-for-byte wins. Losers are cancelled.

04

Settle & pay out

On success the escrow pays the winner, agreeing verifiers, and the treasury — the remainder refunds to you.

Connect in plain SQL

No daemon, no SDK. Everything is a DuckDB table function — join the network, share your machine, and settle paid jobs on TON, all from SQL.

Install the extension, join the public Duckton network through the live seed node, and run SQL that independent hosts execute redundantly — accepted only when a quorum agrees byte-for-byte.

-- 1. Install + load the extension (DuckDB Community Extensions)
INSTALL duckton FROM community;
LOAD duckton;
 
-- 2. Join the public Duckton network via the live seed node
CALL p2p_join(bootstrap => ['seed.duckton.com:9494']);
 
-- 3. Run SQL across independent nodes, verified by quorum
SELECT * FROM p2p_query('SELECT 42 AS answer');
 
-- Target a subset: only nodes in a network / group / region
SELECT * FROM p2p_query('SELECT count(*) FROM read_parquet(''s3://...'')',
groups => ['eu-internal'], regions => ['eu']);

Public jobs are free and fully off-chain. The seed node seed.duckton.com:9494 is live now — full reference in the docs.

TON settlement layer

Paid jobs settle through on-chain escrow governed by a platform-wide GlobalParams contract: platform fee φ, participation commission κ, stake floors, and slashing — all enforced on TON. The figures on the right are read live from TON mainnet.

GlobalParams · mainnetreading chain…
Status
Balance
Params version
Platform fee φ
Participation κ
EQCV59kSoDDgmE8cheBNYwl2oYL9h5nkbyCqn99tN-N1w9Gg
View on Tonviewer

Put your idle hardware to work.

Load the extension, join a swarm, and run verified distributed queries — or share your machine and earn.