Run a node · Bitcoin Ghost

what makes a ghost node

Bitcoin Core, plus everything Ghost adds.

A Ghost node runs alongside your Bitcoin Core daemon. It adds a mesh layer, an incentive layer, and a privacy layer on top of stock Bitcoin — every feature below is built into the Ghost binary, every one toggles in config.

BUDS

Tier-based mempool policy dial. Accept or reject transactions by class — T0 financial, T1 data, T2 content, T3 abusive — without forking or recompiling.
Reaper

Consensus-safe dead-code filter. Rejects inscription envelopes, runestones, drop stuffing, fake multisig, P2TR annex abuse and oversized OP_RETURNs at the policy layer.
Shroud

Randomised relay delays that defeat timing-correlation attacks used to fingerprint originating nodes and link wallets to IPs.
Ghost Mode

Blocks-only relay. Your node never announces transactions into the mempool, preventing origin-address leakage from passive network surveillance.
Exorcism

Defensive block storage. Blocks are validated in RAM, then hazeable fields — witness, scriptSig, OP_RETURN, coinbase data — are stripped before disk. Harmful bytes never persist.
Tor or clearnet

Embedded Tor subprocess or clean clearnet P2P routing, configurable per node. The mesh counts both identically — no privacy penalty for running hidden.
Decentralised voting

67% Byzantine-fault-tolerant quorum on payouts and consensus actions, gossiped over a ZMQ mesh. Every node can propose, vote, and sign checkpoints.
Incentivised share system

0.5% of every block subsidy plus the full L2 node side of settlement fees flow to the node reward pool. Paid on-chain, every block, to your address.

capabilities

Opt into more. Earn more shares.

The reward pool is split by capability shares. Every node that meets the uptime gate gets at least one share; each capability you opt into — and prove via random peer challenges — adds more. Five capabilities, maximum fifteen shares.

Archive mode +5

Keep the full Bitcoin Ghost chain from genesis and serve block data to peers. Verified via random block-retrieval challenges. Heaviest on storage; highest reward.
Ghost Pay +4

Run the L2 payment service — accept instant payments, serve light wallets, process settlements. Verified via L2 block-lookup challenges. Earns L2 settlement fees on top.
Public mining +3

Open your Stratum ports so external ASICs can point at your node. Verified by peers connecting to your stratum endpoint. Adds miner hashrate to the pool.
Reaper +2

Run the consensus-safe dead-code filter — reject inscription envelopes, runestones, drop stuffing, fake multisig, P2TR annex abuse and oversized OP_RETURNs. Verified by peers submitting policy-classification challenges.
Elder +1

One of the first 101 nodes registered with valid proof-of-work. Slots issued in deterministic order; once burned or retired they stay burned.

the gate

One rule: stay up.

Before any node's shares count toward payout, it must maintain 95% uptime over the trailing 7 days. Measured by peer health-ping receipts, tamper-resistant by mesh cross-validation. This is the only gatekeeper in the system — everything else is capability-based and opt-in.

window

7 days

trailing, rolling

threshold

95%

of samples must be online

consequence

no payout

until you climb back above 95%

hardware

What you need.

Ghost runs alongside Bitcoin Core on the same box. Minimum specs scale with the capabilities you opt into — a pruned Bitcoin-only node is far cheaper than a full-archive node with Pay enabled.

Config	RAM	Disk	Bandwidth	Notes
Minimum	4 GB	700 GB SSD	1 Mbps ↑↓	Bitcoin Core full node + Ghost consensus. No archive, no Pay.
Recommended	8 GB	1 TB SSD	10 Mbps ↑↓	Comfortable margin. Enables Pay. Headroom for mesh gossip and share traffic.
Archive	16 GB	2 TB SSD	50 Mbps ↑↓	Full historical block serving. Pass archive challenges under load.
Public mining	+2 GB	—	+10 Mbps ↑	Add to any config. Share-propagation latency matters; low-ping bandwidth helps.

A home server, PC or laptop running Bitcoin Ghost can be a Ghost node. Tor is supported for operators who want to stay off clearnet — the mesh counts Tor and clearnet nodes identically.

quickstart

From zero to node in five steps.

Full walkthrough in the operator docs; this is the sketch.

1

Install Bitcoin Ghost

Download the binary from the downloads page, verify the signature, and run ghost-pool --help to confirm.
2

Point at Bitcoin Core

Ghost talks to your existing Bitcoin Core daemon via RPC + ZMQ. Add an RPC user and open the two ZMQ ports (hashblock, hashtx) in bitcoin.conf.
3

Configure capabilities

Edit pool.toml — set public_address, pick your mempool policy.profile, flip archive_mode, [ghost_pay], and public_mining to match what you want to offer.
4

Add seed peers + start

Drop a few mainnet seed nodes into seed_nodes and run systemctl start ghost-pool. The mesh does peer discovery from there.
5

Pass the gate

Stay online. After ~7 days of 95%+ uptime, you're eligible for the reward pool. Each capability verifies over the same window via random peer challenges.

ready?

Join the mesh.

Every node makes the pool harder to capture. Get the binary, spin it up, help Ghost run forever on its own.

Download → Read the full operator guide

Run a Ghost node.