plumb
Thriving Thriving C++ C+ Python PY
โ†‘ 60
plumb plumb-node/plumb

Bitcoin Knots with every reviewed spam-policy filter. Policy only, same consensus.

HEALTH 100 / Healthy
// solo builder// release machine bitcoinbitcoin-knotsfull-nodemempool-policy

// momentum

tracking since W47

// why it's here

  • Active: last commit today
  • Built almost entirely by one person
  • 10 releases in the last 90 days

// how to help

// readme

Plumb is Bitcoin Knots plus the spam-policy filters the Plumb maintainers have reviewed and ACKed, whether they were opened against Knots or here, and whether or not Knots merges them. Each release is one Knots release plus those merges, the few other Knots pull requests listed below, and one default of its own: -datacarriersize starts at 42 bytes, where Knots has started at 83 since v29.2.knots20251110.

It is a policy project, not a consensus project. The filters change what your node relays and what your node mines. They do not change which blocks are valid, so Plumb follows the same chain as the Knots release it is built on.

It is a drop-in replacement for Knots: same bitcoind and bitcoin-cli binaries, same bitcoin.conf, same data directory. You can switch back to Knots at any time.

What Plumb ships

Read the full README on GitHub โ†—

Health score

Is the project alive and maintained right now? A 0โ€“100 pulse recomputed nightly from commit recency, rhythm, how fast issues close, and how quickly PRs get merged.

How it's calculated

Undervalued score

Activity relative to attention (stars + watchers). Above 50 means a lot of activity for a project its size. Recomputed nightly from commit velocity, contributor effort, issue resolution, fork utility, release cadence, and project maturity โ€” divided by a logarithmic reach factor.

How it's calculated

Tags

Tags are independent behavioral signals computed nightly. A project can hold multiple at once. They drive the home page sections.

How it's calculated