@Spiral should post on Nostr more!!

https://x.com/spiralbtc/status/2041570185740452261?s=20

Realised I had a lot of knowledge gaps to fill so I filled some of them in writing this piece

http://deadmanoz.xyz/posts/2026/bitcoin-node-roles-p2p

📣📣📣

Perth BitDevs/Bitcoin Meetup for April 2026
When: TONIGHT - Thursday 2nd April, 6pm
Where: Rocky Ridge Brewing Co, Burswood

Topics:
* BIP-54 Consensus Cleanup - timewarp fix, validation time limits, Merkle tree hardening, deployment debate
* BIP-110 update - Sybil nodes exposed, willcl_ark crawler shows only 254 genuine nodes out of 3,312
* PQ signature advances - lattice-based HD wallets (BIP-32-style key derivation for post-quantum)
* SHRIMPS - Jonas Nick's 2.5KB multi-device stateful hash-based PQ signatures, successor to SHRINCS
* IBD optimizations - l0rinc's ~16% speedup, Ruben Somsen's SwiftSync (5x faster), LevelDB tuning
* Bitcoin TUI - terminal user interface for Bitcoin Core
* Fuzzor Dashboard - Niklas Goegge's live fuzzing coverage dashboard for Bitcoin Core
* Channel splicing BOLT merged - 8 years from concept to spec, resize channels without closing
* Rare 2-block reorg at height 941,881
* ProductionReady - new "conservative" Bitcoin client, 501(c)(3) from Jimmy Song, Samson Mow, Parker Lewis
* ...and more!

Suggestions are open for additional topics to discuss!
https://github.com/PerthBitDevs/PerthBitDevs/issues/34

https://perth.bitdevs.com.au/

Pick almost any aspect of Bitcoin and prepare to be humbled and ready for a deep rabbit hole.

Currently digging into addr, addrv2, getaddr, et al and boy, there’s much more to these aspects than appears on the surface.

"Token bucket" rate limiters, 6 or 7 different peer types, 24-hour cache for getaddr response, etc etc 😅

Pretty impressed with qwen3.5 35B as a private local model.

Integrated vision, decent tool calling, reasoning/thinking that can be toggled.

It’s slow but has proven adequate in an OpenClaw harness for a few workflows I’ve got - private document interpretation/processing/organisation

I do wonder what the hardware requirements are for such local models to be capable of most general consumer use cases (this model at 35B is not there), probably100s of GB at this point in time?

Remember machine-to-machine payment discussions that were all the rage a few years ago??

Maybe we will finally see some traction in this area with agentic payments!!

Another solid report from @OrangeSurf and @mempool