Domino Compass

since 0.8, rbitcoin's consensus engine has been subject to much scrutiny under a variety of lenses. it was used to add an additional rule and refine other rules of @HornetNode 's consensus spec; used to cross-validate @Rob1Ham 's btc-lean spec and contribute to that effort to fully specify bitcoin consensus; subjected to an attempted proof of equivalence in the LLVM IR by @TheBlueMatt ; and much more. honestly, it's fared remarkably well throughout. for that reason, we're revising how we talk about rbitcoin starting with the 0.9 release tomorrow. rbitcoin 0.9 will be Production Ready, unincorporated rather than Production Ready™️. this is a major step toward the real goal of a 1.0 software release that we can proudly call simply production ready. when I started rbitcoin this summer (as some combination of a joke and just to see if I could), I couldn't have imagined that it would come this far or attract so much positive attention. rbitcoin now has commits from 18 people, plus audits, scans, or reviews from many others. it's grown to over 200,000 lines of production code and another 200,000 lines of test code. it's contributed not only to the consensus specification efforts mentioned above, but to a new way of handling esplora and electrum wallet synchronization, additional testing in bitcoin core, bug fixes in rust-bitcoin, and probably more I'm forgetting. to say that I'm thrilled with the progress on rbitcoin would be a massive understatement. so, to everyone who has encouraged my AI psychosis, discouraged it, contributed to it, or contributed to rbitcoin in any way; thank you! special thanks to bitcoin CEO @Rob1Ham who basically strong-armed me into realizing the possibilities of LLM-assisted coding, and to @ProductionReady for still not forking the repo. not to put too fine a point on it, but the tokens for rbitcoin and my travel to @tabconf and the rust-bitcoin summit were funded by donations for rbitcoin. all of my time in building rbitcoin to date has been donated by me.