Live on Bitcoin mainnet — anchoring daily

Verifiable work, anchored to Bitcoin.

peck.network is a network of nodes that do real work — starting with uptime checks — sign every result, and anchor each UTC day as a Merkle root on Bitcoin. Anyone can verify any claim against the chain. Trust no one — check it yourself.

checks anchored
daily roots on BSV
nodes
endpoints up
latest root: loading… Verify any proof yourself →
How it works

Proof of work done, not promises.

The same primitive — a node does a unit of work, signs it, and the day's work is anchored on-chain — generalizes from "is this URL up" to any verifiable, paid task.

A node does the work

Each node performs a check with full timing, the server's TLS fingerprint and a body hash — artifacts you could only have by actually doing it.

It signs the result

Every result is signed with the node's secp256k1 key. The record can't be altered after the fact, and you know which node produced it.

The day is anchored

Each UTC day, every signed result becomes a leaf in a Merkle tree whose root is written to an OP_RETURN on Bitcoin mainnet.

Don't trust — verify

Check any claim against the chain.

A proof bundle is the signed result, the Merkle path to the day's root, and the anchor transaction. A standalone script verifies all of it with no trust in our servers — the signature, that the leaf is in the tree, and that the root is in a mined Bitcoin OP_RETURN.

One command, zero trust

Re-implemented from spec — it imports nothing from this network. Block-inclusion is checked via Bitcoin headers (chaintracks), never a trusted block explorer.

# fetch a proof, verify signature, Merkle path, and on-chain inclusion
node tools/verify-proof.mjs <result-hash>

Read the verifier →

Join the network

Run a node.

A node only needs to reach the coordinator over HTTP — run it on a cloud VM, a home server, or a Raspberry Pi. Open enrollment, curated approval (the Forta model). The network is early and growing — every independent node, in a different place on a different network, makes the proof harder to dispute. That's why we want you on it.

# 1) build the node agent
docker build -f Dockerfile.agent -t peck-network-agent .

# 2) generate an identity (prints a key)
docker run --rm peck-network-agent

# 3) run it against the coordinator
docker run -d --restart=always \
  -e COORDINATOR_URL=https://pulse.peck.host \
  -e NODE_PRIVATE_KEY=<hex> -e NODE_NAME="my node" \
  peck-network-agent

Full instructions on GitHub →

Get early access.

Building on verifiable work, or want to put your own endpoints on the network? Leave your email — we're onboarding early.