Okay so yesterday was just not a great day, but we bounce back. Right now I'm using GPT-5.6 to do blue team things on my infrastructure and on the @SeleneWallet codebase. It's had me thinking about everything I *have* been doing this year despite a lot of it not being immediately visible. Some reflection: Things have been moving very fast this year. I can't believe we're already in August. It seems like just yesterday we were all gathered in Slovenia, and it feels like there was snow on the ground 3 months ago, not six. We went into 2026 highly optimistic, and I still am very optimistic. There are some bear market vibes, sure, but overall I think BCH is in a great spot right now, and we should keep pushing in the direction we have been. AI has completely changed the way I work, and it's taken some getting used to. I'd say the first three months of the year would have been my "AI psychosis" phase that everyone seems to get when they start using these tools. Basically, finding out how far they can take you, how they work, how they integrate into workflow, how it interacts with new vs existing codebases... Undoubtedly there are some things I've accomplished that I otherwise would not have been able to do, or would not have been able to do anywhere near as quickly. But the problem is fighting the constant slop. That's the other part of this, a problem I've never had to deal with before. Even junior developers can be taught taste and conventions. With these models sometimes you just have to hope for the best and correct it yourself afterwards. Now, of course, humans were shipping bugs well before AI, and AI can even help catch some of those bugs. So it's ironic that its lack of domain awareness can sometimes lead it to writing terrible (imo) code. So that brings me to the blue teaming. First off, I'm pleased to inform everyone that the attack surface for Selene Wallet is very small. Almost every potential vulnerability requires your device to have already been compromised in some way. The rest of the vulnerability lies in supply chain risk, as we depend on a handful of external NPM modules. We have multiple measures in place to mitigate supply chain risks, and I have GPT actively hardening our CI process even further as I write this. There's been lots of travel this year - I spent the entire month of May attending conferences. In April, we were focused on getting our FundMe together (thank you, community!). We last shipped a Selene release in March. So what's been going on between June and now? I tried to get a last minute release out in time for BLISS that was going to have the PUSD-compatible Stablecoin mode (full release, no longer prerelease) and the WizardConnect implementation that Riften Labs contributed for us. There was going to be a special BLISS-related surprise in that release, but I wasn't able to get it out in time. So if the work was done then, why isn't it out now? Mostly because I personally lost the context after travelling, needed time to get back into the groove, and now we're back to the AI slop problem. There are a handful of issues that need to be addressed from the March release. I need to actually grok the incoming stablecoin and WizardConnect code because there were known bugs during pre-release that I wanted to solve. (Turns out one of the bugs was upstream, and I would have never known without AI!!) Then, during BLISS, I got a lot of feedback about how our UI could use some work. I totally agree, so I've been working on that too. And since we need to be able to reuse a lot of both frontend and backend pieces for other upcoming Selene products like Dance Cash and BChat, it was a good opportunity to work on some branding/look and feel things. So... that's also coming in this release. When I consider all of that, and then think that between March and now I've realistically been getting all of these things together mostly over the past 8 weeks, it doesn't seem so bad. I tend to make time estimates based on a fictional ideal self where I'm always in top condition to perform my best work, and that simply isn't realistic lol. So yeah, like I said in OP, I'm doing my best to honor my commitments, it's just slow because I am one person. But I do owe everyone accountability! So instead of staying in the dark forever I figured I should at least say something. Anyway, release is coming very soon, I'm wrapping up the code review for all of the stuff between April and now. We'll have UI updates, WizardConnect, Stablecoin mode, *maybe* CashConnect, and a fair amount of bug fixes. Thanks for your patience and support 💚

🚀 Knuth v1.0.0 is out. This is not an incremental release. It's a complete architectural rewrite. The node is now built end-to-end on C++23 coroutines, powered by a CSP-style synchronization model, and backed by UTXO-Z — a new flat, mmap-friendly storage engine for the Bitcoin Cash UTXO set. ⚡ Full mainnet IBD from genesis to tip in 37 min – 1 h on typical hardware in our test runs. Not a fast-sync. Not a UTXO snapshot. The chain is reconstructed locally from genesis. 🧵 C++23 coroutines across networking, validation and block synchronization 🗂️ UTXO-Z storage with incremental UTXO construction and an embedded Bloom filter 🌳 Lock-free header index, ready for fork-aware chain selection 🌐 BIP155 addrv2, CIDR-aware whitelist matching, and configurable IPv6 networking The previous architecture continues as the v0.x maintenance branch for users not ready to migrate yet. After years of research, prototyping, benchmarking and rewrites, UTXO-Z is finally at the heart of Knuth. 🔗 github.com/k-nuth/kth/releas… #BitcoinCash #BCH #Knuth #UTXOZ #Coroutines #FullIBD

Less than 24 hours to complete the @SeleneWallet FundMe! 91.85% complete! We only need 30 BCH to get this filled - many thanks to everyone who has contributed so far! Bonus: BCH firesale right now! 😅 Will you help us over the finish line?

The @SeleneWallet FundMe is currently 81.72% filled, with only 3 days remaining. I'm grateful for the contributions that have come in over the past few days! Hoping we can get through the final stretch here 🙏 If you have not yet contributed - do you have any feedback on why?