GM Knots Node Runners! View quoted note →

Drain oil ✔️ Take off filter ✔️ Start car to push oil out of pump ✔️ Clean up oil sprayed out of filter tube ✔️ Drop drain tube inside used oil jug ✔️ Put new filter on filled with new oil. ✔️ Fill engine with oil ✔️ Remember I didn't put enough in last time and look at user manual and realize I need almost 7 quarts instead of just 6 ✔️ Clean battery terminals ✔️ Coat terminals with grease ✔️ Wash car ✔️ Check fluids ✔️ Clean air filter ✔️ Clean up splashed oil from garage floor with floor-dry ✔️ Move old oil to new jug to retrieve drain tube ✔️ Clean up oil pans ✔️ Drain old filter ✔️ Sweep garage floor ✔️ Clean funnels ✔️ Burn oily paper towels ✔️ Take shower, get motor oil out of hair ✔️ Nothing is simple

There was a reason they killed Kennedy out in the open. It was a message with a seal.

Kids watch the ballgame, I go to sleep

Rev 2 - A 3 dimensional argument # Node Sovereignty and the OP_RETURN Debate Node runners are hodlers. A true hodler assays his UTXOs by running his own node, enforcing the rules he accepts as truth. Bitcoin’s design—10-minute blocks, limited block size—exists so pleb hodlers anywhere can verify cheaply. Sovereignty means owning an up-to-date copy of the chain according to rules you yourself enforce. The OP_RETURN and relay debate is not peripheral—it is the same struggle as the blocksize wars, now on three axes. ## 1. Efficiency (resource limits) - **Risk:** Opening OP_RETURN relay increases RAM, bandwidth, and CPU burden on every node before a transaction even touches the chain. Abusive payloads can overload inexpensive hardware, raising the barrier to sovereignty. - **Core stance:** Fees should decide; if users pay, relay the data. - **Knots stance:** Relay is an attack surface; filter to keep node requirements minimal. ## 2. Economics (market vs. filters) - **Core stance:** Elegance is neutrality—fees are the only legitimate filter. The mempool is a marketplace, and price is the throttle. - **Knots stance:** Elegance is restraint—protocol should defend itself against bloat before fees can even come into play. Relay filtering is a pre-consensus safeguard. ## 3. Legality (neutrality vs. liability) - **Core stance:** Plausible deniability. Nodes are neutral relays; responsibility lies with originators, not infrastructure. Censorship begins the moment software takes a stance. - **Knots stance:** Personal responsibility. Node operators must refuse to propagate arbitrary or potentially criminal data (CSAM, etc.). Sovereignty requires stewardship, not blind neutrality. ## The Divergence - **Core defines sovereignty** as plausible deniability: neutrality secured by refusing to discriminate, trusting the fee market to resolve usage. - **Knots defines sovereignty** as personal responsibility: pruning abuse at the relay level, even if that means software draws a line. Both postures arise from the same fear: what it means to run a node in a hostile world—whether sovereignty is preserved by claiming neutrality or by exercising judgment. ## Conclusion The OP_RETURN conflict is not technical trivia. It re-exposes Bitcoin’s core fracture: - Is the network defended by **fees and deniability**, or by **filters and responsibility**? - Does sovereignty mean *never censoring* or *refusing to carry abuse*? Forking code under these conditions is not drama—it is necessity.

Node runners are hodlers. A true hodler will run his own node to assay and verify his UTXO. The purpose of running a node is to possess the only source of truth: the blockchain, according to rules enforced in software. This is the core tenet that makes Bitcoin what it is. Every parameter is designed to enable pleb hodlers, anywhere in the world, to maintain an up-to-date copy of that truth, with their own rules defining which UTXOs they will accept. This is why block sizes are limited. This is why block time is ten minutes. Bitcoin is structured so anyone can run a node on inexpensive hardware. OP_RETURN touches relay rules, not chain rules—but expanding it creates an in-plain-sight attack vector. It opens the door to overloading the hardware and bandwidth required for sovereign participation. This is the same battle as the blocksize wars, replayed under another banner. Bitcoin’s defense is not who writes the code. It is whether users run it. The final safeguard is the hodler’s refusal to submit to rules that undermine node sovereignty. That the debate even arises means one thing: the core devs are infiltrated and captured, whether knowingly or unwittingly—a distinction that cannot be known. Forking the code (Knots is the first available option) is therefore a necessity, not a drama. View quoted note →

A problem with reparations is the accused is dead and unable to defend themselves. History is judging them from a different standard, which is ex post facto. Reparations being a Bill of Attainder. Protecting against this is written directly into the US constitution, a fundamental right, one not left to be included as an amendment, one even more fundamental than the first Amendment: Article I, section 9: No Bill of Attainder or ex post facto Law shall be passed. Keep this in mind when accusers come out after Bill Gates is gone.

RIP Z-Man

Some conversations from 20 or 30 years ago with people now passed echo through my head