>The number of knots nodes i'm connected to has dropped off a cliff. fascinating. >I also ban all aws nodes from my node. surely a coincidence. Are we not splitting hairs? ASmap makes you disconnect/not connect in the first place to a set of nodes, which is defined in the dat file. Maybe it's not technically an (ip) ban, but the dat list acts de facto as a "shun list" the way i see it. Please correct me if i'm wrong.

I understand that the *intent* of Asmap is righteous; but at the end of the day your are banning/closung connections to peers that are "on the list" I just hate everything about it. Pseudo-scientitic labeling of "good vs bad" peers. We'll get a risk score next

How is ASmap heuristic node clustering much different from Chainalysis' heuristic utxo clustering?? Both are applying (questionable) heuristics to some public (or private) metadata; Are Bitcoiners really advocating for the use central banlists* now? REALLY?? 🤮 *yup, it's literally downloading a list from https://github.com/asmap/asmap-data/blob/main/latest_asmap.dat . But i'm sure our beloved governments will provide such a curated peer list going forward... 🤦

You don't have to use it for Silent Payments. It's a separate sub-wallet. Alternatively, use CakeWallet

Yes, they should have stayed put, or slightly increased the limits. But they didn't act rationally and totally i, pushing this through just to prove a point. ZKPs don't need that much data; fun fact, Citrea, cited as ine of the beneficiaries, rather uses Inscriptions instead of the op_return. Core burned all their social capital, and it was all for nothing. At the same time, they are stalling what would be the right way to enable proper two-way pegs and thus scale bitcoin: CTV+CSFS. It all makes no sense 🤷 (unless one subscribes to the theory this was a deliberate sabotage)

Dude, they are literally simply asking for a setting to remain as it was for over a decade. And bitcoin was obviously working just fine that way. You are totally turning truth by 180°.

One can just chieve the same thing with SQL against the database, right? 🤷 Can even fling a nice BI dashboard on top..

Ok i see, but what's and how things are getting clustered into a certain AS is important. These are all just heuristics; for instamce just because several nodes share the same AWS region doesn't mean they are one AS, and that you shouldln't connect to more than one.