Damus
₿eno⚡️ · 52w
So are Knots numbers up now? nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4sppemhxue69uhkummn9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshscy566r nostr:nprofile1qq...
Bitcoin Mechanic profile picture
Hard to say, this aint the kind of network with official stats ya know?

There seem to be about 1000 listening Knots nodes out of 21,000 total.

Non-listening is only tracked on Luke's site but it takes forever to update so basically hasn't moved yet.
55❤️17🤙2👍1🔥1🖤1🙂1
Arthur Morgan · 52w
That's quite impressive
IDW · 52w
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.
nostrich · 52w
Looks like more than that 💪 https://primal.net/e/nevent1qqsq8pr3gylq4zlhdtnw0qug4jshldm789rttpew43h3cux4yzu240cpq8ag5
nomadshiba⚡ · 52w
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 h...
cheesypleb · 52w
Does this include those behind tor?
nostrich · 52w
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.
ShiShi21m · 52w
You really just need one decent mining pool to agree to run this to achieve what you want.
Smaug · 52w
I'm running knots and datum
Kuba · 51w
+1 now