frankomosh retweeted
How do developers find bugs they don’t already know to look for?
Even when software passes its tests, an unusual input can expose a problem no one anticipated. Fuzz testing helps developers explore those possibilities by repeatedly generating and modifying inputs, looking for crashes, errors, and broken assumptions.
In our latest article, Btrust grantee @_frankomosh shares insights from his fuzz testing work, helping explain how the process works, why it matters for Bitcoin, and what it takes to turn a failure into a useful finding.
Read the article here 👇🏾 xitter.gq/btrustteam/status/2119…
frankomosh retweeted
Hello Nairobi 👋
Our monthly BitDevs meetup is almost here, we have some interesting topics around Bitcoin Core and Opensource mining and advancement in Bitcoin layer 2. Seee you soon @NodeNBO 🫡⚡️
RSVP 🔗 luma.com/fl5mu86v
Congrats to every participant
55 women. 10 open-source freedom tech projects shipped in two weeks in Nairobi 🇰🇪
Meet the winners of our biggest Hack4Freedom cohort yet 👇
blog.evento.so/hack4freedom-…
frankomosh retweeted
We built a 3D visualizer for different Bitaxe and NerdQAxe boards, letting you explore the components and understand the hardware.
Want to build your own Bitcoin miner locally?
asic-visualizer.vercel.app
Idea credit: @AnshSharma54105
#opensourcemining
frankomosh retweeted
I wasn’t going to comment since this is a really bad take IMO, but since it’s taken off I feel the need to. To my understanding, there is no evidence whatsoever pointing to a break of decades old hardness assumptions like elliptic curve cryptography. 1/n
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash.
Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase).
Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets.
IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster).
Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot.
Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time?
Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.)
Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once.
Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case.
I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026).
Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS.
Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security.
The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
frankomosh retweeted
A new release candidate of Bitcoin Core, v32.0rc2, is available for testing.
This is a new major release, and follows v31.1.
Work-in-progress release notes are here: github.com/bitcoin-core/bitc…
Binaries are available here: bitcoincore.org/bin/bitcoin-…
frankomosh retweeted
Sharon (@nkatha_kk) is a developer based in Nairobi 🇰🇪, and an alumna of @DadaDevs and @btrust_builders.
She completed the 2026 BOSS Challenge, where she made her first major Bitcoin open-source contribution.
Her grant-funded work focuses on @braidpool's mining infrastructure: strengthening Stratum V1 reliability, addressing gaps in protocol implementation, and improving scalability.
This work helps connect existing mining ⛏️ equipment with decentralized pool software.
Nkatha also helps lead discussions at @BitDevsNBO meetups, supporting learning and knowledge-sharing within the local developer community.
frankomosh retweeted
Preprint of my research paper: "Investigating the application of differential fuzzing to support the identification and suppression of equivalent mutants: An experimental study"
researchsquare.com/article/r…
frankomosh retweeted
Brandon is a @bitcoincoreorg contributor based in Kenya.
His work focuses on build systems, testing, continuous integration, functional tests, documentation, RPC improvements, GUI work, and code review.
During his previous grant period, he contributed across many parts of Bitcoin Core, including functional test enhancements, Signet configuration support, RPC coverage fixes, offline signing documentation, GUI improvements, and extensive review of CI and build-related pull requests.
@BrandonOdiwuor's long-term project focuses on improving Bitcoin Core’s CI pipeline using CTest and CDash.
With the long-term grant, Brandon will prototype CTest integration for Bitcoin Core tests, help set up and improve a CDash dashboard, update CI workflows, support sanitizer and coverage reporting, review CI and build-related changes, and continue mentoring new contributors.
Brandon also helps grow the Bitcoin developer community through @BitDevsNBO 🇰🇪, where he leads Socratic seminars and supports technical discussions around Bitcoin Core development.
frankomosh retweeted
Abiodun is a software engineer and Bitcoin open-source contributor based in Lagos, Nigeria.
His work focuses on wallet infrastructure in the @bitcoindevkit ecosystem. @_abiodunAwoyemi is a secondary maintainer of bdk-tx, a transaction-building library in the BDK ecosystem.
His contributions have covered many areas that directly affect wallet safety and reliability. These include fee calculation fixes, anti-fee-sniping support, Payjoin examples, CPFP fee-bumping support, locktime handling, BIP353 payment support reviews, PSBT creation, BIP322 message signing, and continuous integration improvements.
With the long-term grant, Abiodun will continue strengthening BDK and BDK-TX.
His work will focus on making Bitcoin transaction construction safer, more predictable, and easier for developers to use.
Abiodun also co-organizes @BitDevsLagos 🇳🇬, helping create space for technical Bitcoin discussion and contributor growth in Nigeria.
frankomosh retweeted
Behind every active Bitcoin open-source contributor is a system that helped them get there, one that helped them discover Bitcoin, develop the skills to work on it, and find a place within the open-source ecosystem. Supporting that system across the Global Majority is what Btrust grants are designed to do.
For a long time, open-source Bitcoin development has not reflected the full range of people Bitcoin is meant to serve. That gap was never about ability. It was about access, to learning paths, technical communities, mentors, and funding.
Since 2021, Btrust has been working to change that through grants, mentorship, and education programs for developers from Africa and the Global Majority.
@Camilla_rhi , @nagasha_ and @engb_os are three grantees from across Africa who found their way into serious Bitcoin open-source work through that system.
Three different backgrounds. Three different paths. One shared commitment to building.
frankomosh retweeted
A new release candidate of Bitcoin Core, v31.1rc1, is available for testing.
This is a new minor release, and follows v31.0.
Release notes: github.com/bitcoin/bitcoin/b…
Binaries are available here: bitcoincore.org/bin/bitcoin-…
frankomosh retweeted
Over the past few months, I've been conducting research on applying fountain codes to Bitcoin, together with @edil_medeiros. In my blog post , I'll give an overview of the idea and share the advances we've made so far.
Check out the full post here: lucasdbr05.com/posts/fountai…
frankomosh retweeted
Jan Kvapil and Ondrej Ceska has been doing meaningful contributions to the bitcoinfuzz project. This week Ondrej defended his MSc thesis - "Differential fuzzing of BIP32 implementations". 🎉
One of the great outcomes of this research is to realize the lack of adherence to evolving specifications (BIP). Specifications evolve, but maintainers and contributors may not be aware of recent updates.
frankomosh retweeted
1.
from #BOSSChallenge2026, I built Know Your Coin History l, a Bitcoin transaction graph explorer that lets you trace the origin of your coins.
Enter a txid, walk backwards through ancestor transactions, and label every input and output.
frankomosh retweeted
Our community is already quantum resistant!
Meet us every last Saturday of the month at our new home, @NodeNBO
We’ve been on a side-quest, and we have good news from the other side! 40 million Kenyans now have a bitcoin Lightning Address! They didn’t need to sign up for one because they had it this entire time, attached to the phone number in their pocket!
Try it: send bitcoin to [email protected] (254 is optional). The BTC arrives as KES in their M-Pesa. ⚡ EVERY M-Pesa number works. All 40,000,000.
Wallets with LUD-09 support give you a nice clickable link to see your M-Pesa receipt. For example: bitcoin.co.ke/receipt/6528a4…
🤖 Made with AI
frankomosh retweeted
Throwing it back to our 2025 Year in Review.
2025 was about strengthening the foundation for decentralized Bitcoin development across Africa and the broader Global Majority. After several years of experimentation and iteration, the year marked a shift toward more structured execution; deepening the programs, partnerships, and systems that support open‑source contributors across the Bitcoin ecosystem.
Throughout the year, we focused on building and strengthening the developer pipeline, from discovery and education to mentorship, grants, and long‑term contribution opportunities. Across our initiatives, more than 3,800 developers engaged with Btrust programs and ecosystem activities.
frankomosh retweeted
This month, we're celebrating five years of Sebastian Falbesoner (@theStack) working on Bitcoin Core and libsecp256k1 at Brink.
Sebastian started with often unglamorous test work, steadily widening his scope, and eventually stepping up to steward impactful privacy proposals…





























