Pure bitcoin. No spam tolerated.
Plumb is Bitcoin Knots plus the spam-policy filters its maintainers have reviewed and ACKed, whether they were opened against Knots or against Plumb, and whether or not Knots merges them.
- Policy, not consensus. The filters change what your node relays and mines. They do not change which blocks are valid, so Plumb follows the same chain as the Knots release it is built on.
- A drop-in for Knots. Same
bitcoindandbitcoin-cli, samebitcoin.conf, same data directory. You can switch back to Knots at any time. - Every filter is its own option. All are on by default.
-corepolicyturns all of them off along with the rest of the Knots policy. - A 42-byte data limit.
datacarriersizestarts at 42, where Knots starts at 83. It is not a filter and has no switch of its own:datacarriersize=83matches Knots, and-corepolicysets 83 too.
Current release: v29.5.1.knots20260508.plumb14, built on Bitcoin Knots v29.5.1.knots20260508.
What Plumb ships
| Option | What it counts or refuses | From |
|---|---|---|
-rejectfakeoutputs | Outputs whose hash or key is data, counted as data carrier bytes. | knots#389 |
-rejectbareenvelopes | A run of pushes ended by OP_DROP or OP_2DROP, counted as data carrier bytes. | knots#319, in Knots since 29.4.3; the switch is Plumb's |
-rejectfakemultisig | Multisig keys that no signature in the spend proves, beyond 10 per script, counted as data carrier bytes. | knots#422, in Knots since 29.4.3; the switch is Plumb's. knots#470 since plumb9, in Knots since 29.5.1 |
-rejecttokenmessages | An OP_RETURN that holds a JSON token message or an Omni Layer message. | knots#489, under -rejecttokens; the switch is Plumb's. Plumb's own plumb#2 before plumb9 |
-rejectunverifiedwitness | Witness items that no verified signature check used, past 42 bytes per input, counted as data carrier bytes. | plumb#8, Plumb's own, since plumb12 |
Knots 29.4.3 took in the rules behind three of Plumb's earlier filters. The dead-branch rule (knots#400) is a Knots option now, so Plumb no longer lists it; the bare-envelope and unproven-key rules are in Knots with no switch, so Plumb keeps a switch for each; and Knots' new -rejectbpub (knots#463) comes along unchanged.
knots#470, in Plumb since plumb9 and in Knots since 29.5.1, adds to the unproven-key rule: a key in a witness script counts as proven only when a signature in the spend verified against it, so a signature check that never runs, or fails on an empty signature, proves nothing. Plumb also carries two Knots pull requests that are not filters. knots#487 relays the penalty spend of an LND simple taproot channel, counting the key its revocation leaf drops toward datacarriersize instead of refusing it as non-standard data, behind -permitlnrevokeleaf, default on; permitlnrevokeleaf=0 refuses the spend as Knots does. knots#488 serves headers and blocks past the fork to a peer with the download permission even when it does not advertise NODE_BLAKE2B, so an indexer behind [email protected] keeps syncing; since plumb10 it leaves out a peer that advertises NODE_NETWORK or NODE_NETWORK_LIMITED, a full node still on the SHA256d chain.
Plumb 10 moves to Knots 29.5, which changes no consensus code. Plumb's -rejectfakeoutputs now skips the leading zero bytes of a hash or key, when there are seven or fewer, as a vanity address has them, so a payment to an address whose hash or key starts with six or seven zero bytes is no longer refused.
Plumb 11 moves -rejectfakeoutputs to the new head of knots#389: three or more distinct P2WSH outputs sharing one value now count as data at 353 sat or less, down from 546. Plumb 10 counted them up to 546 sat, which could refuse a Lightning force close whose commitment carried three HTLC outputs of one amount from 354 to 546 sat. Plumb 11 also carries knots#470's three new commits: two change how the recount runs and the third tests it. From block 961640 to 982017 cesspool.lol grades no transaction differently for them.
Plumb 12 adds Plumb's own -rejectunverifiedwitness (plumb#8). After the script check it counts the bytes of witness items no verified signature check used, past 42 per input, as data carrier bytes. The padded fake-key reveals since block 981910 put 13 items of 64 bytes, dressed as signatures, behind OP_SIZE 64 OP_EQUAL OP_NOTIF and drop them; Plumb 11 already refused those through knots#470, and now the items count too. From block 961640 to 982707 cesspool.lol grades one transaction differently for it: a tapscript at block 981837 that drops 555 bytes, which Plumb 11 relayed, is sewage now.
Plumb 13 fixes CVE-2026-117348, which Bitcoin Core disclosed on 2026-11-20. A peer could send a node an orphan transaction with many missing parents, then inv messages that repeat its wtxid 50,000 times; for each repeat the node checked every missing parent again and handled nothing from other peers, blocks included, until it was done. The fix is bitcoin/bitcoin#35878, as Knots carries it in v29.5.1.knots20260508rc1. The filters and their defaults do not change, and in the conf files below only the release name changes.
Plumb 14 moves to Knots 29.5.1 and carries its consensus rules; upgrade promptly. The filters and their defaults do not change, and the four conf files below start Plumb 14 with no warning.
FILTERS.md says what each one rejects and leaves alone, with an example transaction and the line that turns it off. The node logs which filters are active at startup:
Plumb filter -rejectfakeoutputs=1 (knots#389)
Plumb filter -rejectbareenvelopes=1 (knots#319)
Plumb filter -rejectfakemultisig=1 (knots#422)
Plumb filter -rejecttokenmessages=1 (knots#489)
Plumb filter -rejectunverifiedwitness=1 (plumb#8)
Have a filter of your own? Plumb takes anti-spam policy filters as pull requests. If it is open against Knots, open it against Plumb too and link the two.
Get it
On Umbrel, install the Plumb app from Leo Haf's Misc community app store: step-by-step instructions for Umbrel.
On StartOS 0.4, sideload Plumb's package (x86 only, a pre-release): step-by-step instructions for StartOS.
Releases are signed git tags named after the Knots release they are built on. Each release page carries the source and a pre-built bitcoind and bitcoin-cli for x86_64 Linux with a signed SHA256SUMS; the verify steps are on the release page.
git clone https://github.com/plumb-node/plumb
cd plumb
git checkout v29.5.1.knots20260508.plumb14
git verify-tag v29.5.1.knots20260508.plumb14
cmake -B build -DBUILD_GUI=OFF
cmake --build build -j"$(nproc)"
Tags are signed by Jason Sopko, 89F0 E41D 72CE 523F 4AA1 CDB6 92CD FFB7 C40C D1BA. Fetch the key from keys.openpgp.org or github.com/jasonsopko.gpg.
Build dependencies are the same as Knots. The binaries land in build/bin/. To switch from Knots 29.5.1, 29.5 or 29.4.3, stop bitcoind, install the new binaries and start it again; the data directory and bitcoin.conf stay as they are, unless bitcoin.conf sets bytespersigop, bytespersigopstrict, maxscriptsize, limitancestorsize or limitdescendantsize out of range, which Knots 29.5.1 refuses at startup.
To build on a faster PC and copy the result to your node, use the recipe that makes the release tarball. It needs Docker and runs from the checkout above:
JOBS=8 CPUS=8 MEMORY=16g plumb/tools/release-tarball/build-tarball.sh v29.5.1.knots20260508.plumb14 ~/plumb-build
Set JOBS and CPUS to your core count, with about 2 GB of MEMORY per job. It builds in Debian 11 with libevent, SQLite and the other libraries linked in, and the tarball lands in ~/plumb-build/out. Copy it to any x86_64 Linux with glibc 2.31 or newer (Debian 11, Ubuntu 20.04 and later), untar it and run bin/bitcoind from the directory it creates. The plain cmake build above uses the build machine's own libraries, so it belongs on that machine. The recipe's README lists each step.
To hear about new releases, use Watch, Custom, Releases on the repository.
Recommended bitcoin.conf
One file for Plumb and one for Knots, the same files as on cesspool.lol/check, which also has the settings for Umbrel and StartOS. Each writes its filter settings out, so a corepolicy=1 set elsewhere can no longer reset them (it still changes settings they do not set, such as the minimum relay fee), and sets three values stricter than Knots' defaults: datacarriersize=42 (Plumb's own default since plumb7), datacarriercost=2 and bytespersigopstrict=51. The comment above each says what it does, and cesspool.lol explains the third: it refuses most fake multisig, which gets past every Knots data limit. If your bitcoin.conf already sets one of these options, change or remove that line rather than adding a second one.
Download plumb.conf or knots.conf. The Plumb file:
# Recommended bitcoin.conf for Plumb 13
# https://cesspool.lol/check/
#
# Plumb's spam filter settings, written out so that a corepolicy=1 set
# elsewhere can no longer reset them. Two are stricter than the
# defaults, datacarriercost and bytespersigopstrict; the comment above
# each says what it does. The comments above some of the defaults say
# what they refuse that is not spam. The last five are Plumb's own; the
# rest match the Knots file, and rejectdeadbranches and rejectbpub are
# Knots' own since 29.4.3. Fee, dust, rate-limit, package-size,
# unknown-witness and bare-anchor settings are left alone. A
# corepolicy=1 set elsewhere still changes settings this file does not
# set, such as the minimum relay fee.
#
# If your bitcoin.conf already sets one of these options, or turns one
# off with a no line such as nodatacarrier=1, change or remove that line
# rather than adding a second one: with two lines, which one wins
# depends on their order and form. A line under [main] wins over lines
# outside it. settings.json and bitcoin_rw.conf in the data directory
# win over this file, as does the command line. Restart the node after
# editing.
corepolicy=0
acceptnonstdtxn=0
rejecttokens=1
rejectparasites=1
rejectdeadbranches=1
rejectbpub=1
# The default. With it, a version 3 transaction that pays no fee and
# carries a pay-to-anchor output of at most 240 sat is refused even
# beside a child that pays for both: the package Lightning's zero-fee
# commitment channels use. It relays only with subdustfeepenalty=0 and
# mempooltruc=enforce, plus permitephemeral=anchor,-send,dust when the
# anchor holds 1 to 239 sat; the Lightning file at
# https://cesspool.lol/check/#lightning sets all three. None was mined
# from block 961640 to 978047.
subdustfeepenalty=1
datacarrier=1
# Plumb's default since plumb7; Knots' is 83. Written out so that a
# corepolicy=1 set elsewhere does not raise it to 83. From block 961640
# to 976619 (3,569,710 transactions, not counting coinbases),
# cesspool.lol lists 108,535 as sewage, graded at Plumb 13's defaults.
# Plumb refuses 108,535 of them, and would relay 80,988 of those at 83.
# 42 keeps 32-byte commitments such as OpenTimestamps.
datacarriersize=42
datacarrierfullcount=1
# The default is 1. At 2, each byte of data counts as 2 vbytes instead
# of 1 when the node sizes a transaction for relay and for the blocks it
# builds, so data pays twice the fee per byte.
datacarriercost=2
# The default. It refuses data outside OP_RETURN, which includes a push
# that a script drops unused. In the same blocks it also refuses 5
# Rootstock PowPeg spends of Flyover deposits, whose scripts start with
# a 32-byte value dropped that way. cesspool.lol does not count those as
# sewage: https://cesspool.lol/about/#bar.
acceptnonstddatacarrier=0
# The default. It refuses a transaction whose only output is an
# OP_RETURN. In the same blocks it also refuses 279 sweeps of Lightning
# anchors and other dust into fees, whose OP_RETURN holds 4 bytes or
# less of padding. cesspool.lol does not count those as sewage.
permitbaredatacarrier=0
permitbarepubkey=0
permitbaremultisig=0
permitephemeral=anchor,-send,-dust
# The default, sized for a 15-of-15 multisig spend. A lower value would
# refuse the fake multisig below, but it also refuses every ordinary
# multisig spend bigger than the value: at 590 it refuses 0 sewage
# transactions and 552 that are not, nearly all multisig, some as large
# as 1,609 bytes.
maxscriptsize=1650
maxtxlegacysigops=2500
bytespersigop=20
# The default is 20. Knots counts signature checks in a multisig script:
# one for each key in segwit, four for each key in plain P2SH, 20 for
# any multisig over 16 keys. It refuses a transaction with fewer than
# this many weight units for each check. In segwit each signature adds
# about 72, so a 2-of-3 P2WSH spend has about 139 for each check and a
# segwit 2-of-15 about 55. Fake multisig, one signature for 15 keys of
# which 14 are data, comes in at about 50. Other multisig with many keys
# and few signatures can fall below 51 too, such as a segwit 2-of-17
# spending many coins; none did in these blocks. In the same blocks
# cesspool.lol lists 700 fake multisig transactions, and
# rejectfakemultisig and Knots' own rules refuse all 700 of them
# already. 51 would refuse 675 of them on its own and nothing else;
# nothing that is not sewage is refused below 56. It stays as a second
# check that depends on neither the key count nor the file format: a
# reveal with ten or fewer unused keys in each script and no BPUB header
# passes both Knots rules. https://cesspool.lol/check/#fake-multisig
# says more.
bytespersigopstrict=51
rejectfakeoutputs=1
rejectbareenvelopes=1
# In the same blocks it also refuses 1 Liquid-layout emergency spend,
# very likely Liquid's own recovery. The layout cannot prove that the
# unsigned keys are real, so cesspool.lol still counts it as sewage.
rejectfakemultisig=1
rejecttokenmessages=1
# Plumb's own since plumb12 (plumb#8). It counts the bytes of witness
# items no verified signature check used, past 42 per input, as data
# carrier bytes: data handed to a P2WSH, P2SH-P2WSH or tapscript spend
# as witness items that the script drops, or passes to a signature check
# that never runs. It leaves alone signatures and the keys they verified
# against, copies of those keys, and up to 42 bytes per input that no
# signature verified: a hash preimage or a key a script only hashes,
# with a selector beside it. From block 961640 to 982707 the only
# transaction it refuses that Plumb 11 relayed is a tapscript at block
# 981837 that drops 555 bytes.
rejectunverifiedwitness=1
Behind a Lightning node. Everything a CLN or LND node broadcasts relays with the files above, apart from a mutual close that burns a tiny balance into an OP_RETURN over 42 bytes and, with the Knots file, the penalty spend of an LND simple taproot channel. A zero-fee commitment channel, which LDK 0.2 and later can open between LDK peers and eclair 0.14 has as an option that is off by default, needs three settings changed: subdustfeepenalty=0, mempooltruc=enforce and permitephemeral=anchor,-send,dust. Its commitment transaction is version 3, pays no fee itself beyond a trimmed remainder and carries one pay-to-anchor output of at most 240 sat, with a child paying for both, and three Knots defaults refuse it. The Lightning files are the files above with those three lines changed and the dust fee settings written out at their defaults. What the three lines let through: a version 3 transaction that pays less than the 1 sat/vB relay floor on its own, with at most one pay-to-anchor output under its dust limit, when it arrives with a version 3 child that pays the floor for both. From block 961640 to 978047 nothing mined fits that description. Do not raise dustrelayfee or turn on dustdynamic on such a node: anything above the default makes the 330-sat anchors dust, and every anchor force close is refused. cesspool.lol/check says the rest, and the comments above each changed setting say what it does.