Thread

That's quite impressive

Some argue that since miners can already include transactions with large OP-return data fields we should remove the filter from nodes. Instead I suggest we consider a consensus rule change (fork) to block miners from including large op-return transactions.

Looks like more than that 💪 https://primal.net/e/nevent1qqsq8pr3gylq4zlhdtnw0qug4jshldm789rttpew43h3cux4yzu240cpq8ag5

i was thinking about having a podman and docker compatible image on the repo distributed with ghcr.io. that runs the node directly over tor. without doing any settings. so you can just set it up easily with podman, docker, distrobox, toolbox, etc. distrobox can even export the qt launcher to the host. making it run like a normal app on the host. things like BoxBuddy makes the UX great. or it can be a flatpak with tor built-in. less friction, more nodes.

Does this include those behind tor?

Inertia. People don't upgrade often. But the switch is the easiest it can be, litterally just run the Bitcoin Knots binary and all continues to work as expected. It will move.

You really just need one decent mining pool to agree to run this to achieve what you want.

I'm running knots and datum

+1 now