🚨 Mempool Bomb Alert — Core v30 🚨
Core v30 ships permissive OP_RETURN defaults and relaxed relay behavior.
That’s not neutral — it’s an invitation.
Cheap OP_RETURN payloads + package/ancestor relay = an easy mempool bomb:
nodes fill, eviction churn spikes, block templates slow, wallets lag.
Pretty quickly your node is doing unpaid work for spammers.
Runbook for honest ops:
• disable datacarrier (-datacarrier=0) or cut -datacarriersize hard
• tighten mempool limits (-maxmempool, ancestor/descendant caps)
• enable pruning, disable txindex if you don’t serve explorers
• run observer-mode tests (DamageBDD) to fingerprint peers
This is not FUD. It’s an operational reality. If you care about uptime, latency or proving you’re running a clean node — act now.
Proof, telemetry and hardened configs coming from DamageBDD.
#Bitcoin #Core #Knots #DamageBDD #Mempool #OpReturn #ECAI #NetOps
🚨 Mempool Bomb Alert — Core v30 🚨
Core v30 ships permissive OP_RETURN defaults and relaxed relay behavior.
That’s not neutral — it’s an invitation.
Cheap OP_RETURN payloads + package/ancestor relay = an easy mempool bomb:
nodes fill, eviction churn spikes, block templates slow, wallets lag.
Pretty quickly your node is doing unpaid work for spammers.
Runbook for honest ops:
• disable datacarrier (-datacarrier=0) or cut -datacarriersize hard
• tighten mempool limits (-maxmempool, ancestor/descendant caps)
• enable pruning, disable txindex if you don’t serve explorers
• run observer-mode tests (DamageBDD) to fingerprint peers
This is not FUD. It’s an operational reality. If you care about uptime, latency or proving you’re running a clean node — act now.
Proof, telemetry and hardened configs coming from DamageBDD.
#Bitcoin #Core #Knots #DamageBDD #Mempool #OpReturn #ECAI #NetOps
Login to reply
Replies (1)
At this point I'm committed. Every time I see someone shit talk core I will run an additional core and btcd node.