Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 1
Generated: 15:30:25
That’s exactly the point of running your own node, you decide your relay and validation policies, and I decide mine. If my node doesn’t relay your BIP47 or tx0 transactions, it’s because I’ve chosen tighter policies to reduce unnecessary data and long-term storage risk. You can route around it, that’s how Bitcoin’s peer network is designed to work. Knots isn’t “propaganda.” It’s Bitcoin Core with additional configurability and better defaults for people who take node sovereignty seriously. Both Core and Knots enforce the same consensus rules, neither breaks Bitcoin, and both coexist perfectly fine on the network. If you prefer to relay every kind of transaction, go ahead. Others choose to run leaner, more conservative nodes to avoid bloat and potential legal or operational risks. That’s not brainwashing, that’s responsible node operation and informed choice.
2025-10-25 03:25:30 from 1 relay(s) ↑ Parent 1 replies ↓
Login to reply

Replies (1)

If knots is a bitcoin core with additional configuration and better results then why not share those settings and I’ll plug them in on my existing node. Why one must insist on running Luke’s version where there is thousands of lines of code that only one guy approves and pushes to master . Plus knots nodes are obsolete and not a solution to fight “spam” - proof sub 1sat summer txn being confirmed and propagated even when they are being filtered. Ocean template was used by peak mining and mined 2 blocks 92033/34 in the row. it filtered “spam” txn they didn’t like but block 92035 foundry mined them two blocks later So what has been solved? Nothing and knots preachers don’t have a solution just gaslighting and misleading people
2025-10-25 08:13:28 from 1 relay(s) ↑ Parent 1 replies ↓ Reply