I don't like the pattern of calling things `Manager` in Bitcoin Core. It is always unclear what design pattern they are actually using underneath and it seems to invite kitchen sink class design.
Why no nano S? Is the memory too limited or just some SDK compat thing?
I was in a tiny dry stone walling museum a couple of days ago. It was interesting that they showed a bunch of techniques that were still highly specific to the region. Most of the walling was done with small slate-style rocks - very different from the Jura chalk I am used to, where we sometimes work with boulders a quarter the size of a car. They also showed a free-standing raised bed supported by dry stone, which I would love to have in my garden some day. We also came across these free-standing dry stone structures on our hikes in the region, something I've never seen around here.



I'm in Switzerland. Never seen them before, but haven't been up north in winter either.
Makes it look so easy π
Musig merged in secp π
Hopefully Bitcoin Core's RPC will be superceded by something different and better soon - be it a multi-reader DB or an IPC interface. But keeping everything stable while evolving the codebase is not a happy task to be doing and will create more problems in the future.
I am kind of curious if they end up going for the establishment hack, or the serial scammer.
It is cool to look at, but with a lot of it being a modern restoration the feeling inside was a bit weird. Like it made it harder to imagine what it must have been like to live within the citadel. 
Re. de macht van pools: het is goed dat (bij zowel Stratum v2 als Datum) pools een block template actief moeten afwijzen. Dan wéét je al miner tenminste dat er censuur is, nu kom je daar maar moeilijk achter.
Stratum v2 op BitAxe staat ook op mijn wensenlijstje, er is een Github issue voor. Maar is niet iets wat ik zelf kan.
cc nostr:npub17h7h2jzhq3hn06h93jvz67sfjxaq3jvk7kenjrazht28aun33hks42sd76
https://fountain.fm/episode/UOM4HtDHQ1Yol8LCd0uf
nostr:nevent1qvzqqqpxquqzpn9jvvx8sdhfw4sqqv2570mke5l8g44dydc87mjgjxpv7z4rshftfpv2w9
Mmh, this might require bitmain firmware support by the looks of it? But wouldn't https://github.com/stratum-mining/stratum/tree/main/roles/translator be enough for now?
So these "lite" wallets connect to a remote node and, query the transaction data from them through a rpc interface and scan through it on their side. They trust the remote node to speak the truth when scanning to not feed it fake transaction data. So in the worst case you might calculate a faked balance and transaction history.
You can't spend unconfirmed transactions in Monero, so the mempool is much simpler.
You scan through everything client-side, many monero wallets do this. There is no SPV and headers are not checked either.
Mmh, I can't recall anymore precisely and the code for it might be gone, but I think I at least used arti to submit tx to an electrum server.
Yeah, need to catch up on txdownloadman.
Seems like so many other devs were fed up with that for loop too such that my PR got no less than four ACKs and five Concept ACKs π
That ocean mining DATUM protocol thing feels very much like not invented here syndrome.
That's kind normal for how new features are introduced in Bitcoin Core. E.g. the recently introduced encrypted v2 transport was first feature gated behind a flag and then switched on by default on the next release.


