Maelstrom’s Bitcoin Grant Program Funds Core, Payjoin and Silent Payments עבודה

Maelstrom’s Bitcoin Grant Program just hit a useful milestone: 20 months in, five developers funded, four still active, and a stack of real Bitcoin work to show for it. No token nonsense, no marketing fog machine — just people grinding on Bitcoin Core, privacy tooling, and the infrastructure that keeps the network alive.

• 5 developers funded, 4 still active
• Bitcoin Core, Payjoin, and Silent Payments got real attention
• No tokens, no commercial strings, paid in Bitcoin
• Consensus safety and privacy, not hype, were the point

Maelstrom, the family office tied to BitMEX co-founder Arthur Hayes, released its first annual report on the Bitcoin Grant Program, which began in October 2024. The setup is refreshingly simple: fund open-source Bitcoin development directly, pay monthly in Bitcoin, and keep the focus on work that matters instead of the usual crypto theater.

The program is administered by Jonathan Bier, who authored the report. Grants run as 12-month contracts, can be stacked up to $400,000 per developer per year, and are funded entirely by Maelstrom. Hayes and Bier review the program, but the actual goal is not vibe-based “innovation.” It’s boring, high-value engineering — the kind that keeps Bitcoin useful, private, and hard to break.

Four active developers, real infrastructure work

The report says that “four active developers have collectively advanced Bitcoin’s privacy, security, and codebase resilience.” That’s the right lens. Bitcoin does not survive on memes, ETF inflows, or clownish price targets pulled from thin air. It survives because people keep checking the code, tightening the edges, and building tools that make the system safer to use.

Two of the active grantees work directly on Bitcoin Core, the reference implementation many nodes run. That matters more than most casual observers realize. Bitcoin Core is not some side project. It is the software backbone of the network, and bugs in consensus code can cause nodes to disagree on the state of Bitcoin — a failure mode with no clean recovery path.

“bugs in consensus code can cause nodes to disagree on the state of the network — a failure mode with no clean recovery path”

If that sounds grim, good. It should. Consensus bugs are not a “oops, deploy a patch and move on” situation. This is the base layer of a $100B+ monetary network. Get it wrong and you are not just dealing with inconvenience; you are dealing with a mess that can shake confidence in the entire system.

Rkrux: review work that actually keeps Bitcoin sane

One of the Bitcoin Core contributors, Rkrux, has been funded since October 2024. In 2025, he made 1,155 review comments across more than 200 pull requests, ranking as the 11th most active commenter on the codebase. He then added 400+ more PR comments in the first five months of 2026.

That may not sound sexy, because it isn’t. But code review is one of the most important jobs in open-source Bitcoin development. It is the part where bugs get caught before they become expensive problems. It is the kind of work that receives no champagne, no token airdrop, and no influencer applause — which probably means it’s valuable.

Rkrux also worked on MuSig2, a multisignature scheme that allows multiple parties to cooperate on a single signature more efficiently and privately than older approaches. He also contributed to legacy wallet deprecation in favor of descriptor-based wallets, which are more modern, more structured, and easier to manage safely. In plain English: better wallet architecture, less ancient baggage.

Stratospher: consensus safety and privacy plumbing

The other active Bitcoin Core contributor, Stratospher, joined in November 2025. He fixed an undefined behavior bug in FindMostWorkChain, contributed to removing the BLOCK_FAILED_CHILD flag, and worked on DLEQ cryptographic proofs in libsecp256k1 for Silent Payments.

DLEQ stands for a type of proof used to show two values are linked correctly without exposing private data. In other words, it helps verify cryptographic correctness without leaking the underlying secrets. Not exactly dinner-party material, but absolutely the sort of thing that keeps Bitcoin privacy features from becoming a security mess.

Stratospher also presented at the Africa Bitcoin Conference, a reminder that serious Bitcoin work is not limited to the usual coastal tech-club bubble. That matters. Bitcoin is global, and so is the work needed to keep it healthy.

Payjoin: privacy for ordinary users, not just cypherpunks

On the privacy side, Benalleng has been working full time on Payjoin since June 2025. Payjoin is a transaction method where both the sender and receiver contribute inputs to the same transaction. That breaks the tidy assumptions used by chain surveillance firms to guess who paid whom.

Bitcoin is transparent by default, and that transparency is both a strength and a liability. Anyone can audit the supply. Anyone can verify transactions. But anyone with enough data can also start mapping user behavior. Chain surveillance companies love that. Payjoin makes their job harder.

“even minority adoption of Payjoin degrades chain surveillance capabilities for the entire network”

That line matters. Privacy tools do not need universal adoption to be useful. They just need to make surveillance less reliable. If enough transactions use Payjoin, chain-analysis heuristics become noisier, less confident, and less profitable. That helps everyone — not just privacy purists, but regular users who don’t want their financial life turned into a spreadsheet for snoops.

Payjoin’s API has already been integrated into Bull Bitcoin and Cake Wallet, with five or more additional wallet integrations in progress. Bindings have also been released for Python, Javascript, Dart, and CSharp. That may sound like plumbing — because it is — but privacy tools do not scale through wishful thinking. They scale when developers can actually plug them into real software without wanting to jump out a window.

Silent Payments: reusable addresses without the privacy leak

Macgyver, another privacy-focused grantee since June 2025, has been working on Silent Payments. The core idea is simple and powerful: users can receive Bitcoin through a single static address without reusing that address on-chain in a way that ties payments together.

That matters because address reuse is a privacy footgun. Every reused address creates a breadcrumb trail for wallets, exchanges, analysts, and anyone else with the tools and motivation to connect dots. Silent Payments reduces that risk by giving users a more private way to receive funds without constantly generating new public-facing addresses.

Wallet support is already moving:

• Blindbit-Desktop, Cake Wallet, and Dana Wallet support send and receive
• Sparrow Wallet and Nunchuk have send support
• Bitcoin Core has draft implementations, but they are on hold due to libsecp256k1 dependency work

Macgyver also produced BIP-375 test vectors and proposed a Coldcard hardware signer implementation. He organizes monthly working group meetups too, which sounds dull only if you’ve never seen how much crypto development depends on coordination that would bore a normal person into a coma. Standards, test vectors, hardware signing support, working groups — that is how a feature becomes real.

Why this model stands out

Maelstrom’s program is explicitly open-source only, with no commercial strings attached and no token incentives. That is not a small distinction. Most of crypto is still obsessed with attention hacks, token emissions, and “ecosystem growth” that somehow always means more liquidity for insiders and more PowerPoint for everyone else.

This setup is different. It directs capital toward public goods: Bitcoin Core maintenance, privacy tooling, and protocol resilience. That is where the actual value is. Not in another recycled “decentralized” product with a token and a Discord army. Not in fake utility. Not in shameless price-pump cosplay.

To be fair, this does not solve Bitcoin developer funding as a whole. The program is still small, centrally funded, and dependent on a narrow set of decision-makers. That is a real limitation. Bitcoin’s long-term health needs a broader, more resilient funding culture, not just one decent family office doing the right thing.

Still, there is nothing wrong with giving credit where it is due. Reinvesting crypto wealth into the infrastructure that protects the network is a far better look than lighting it on fire for marketing stunts and “community” campaigns that amount to expensive nonsense.

What this means for Bitcoin’s future

Bitcoin’s future will not be decided by the loudest moonboy, the slickest chart, or the most confidently wrong price prediction. It will be shaped by the people who keep the network secure, private, and usable when nobody is clapping.

That means consensus safety. It means peer-to-peer reliability. It means wallet modernization. It means privacy tools like Payjoin and Silent Payments that make surveillance harder and self-custody more practical. It also means supporting the developers who do the unglamorous work of reviewing code, fixing edge cases, and building the cryptographic plumbing beneath the headlines.

Maelstrom’s Bitcoin Grant Program is a useful example of what serious Bitcoin funding can look like: direct, Bitcoin-denominated, open-source, and focused on infrastructure instead of hype. That does not make it a cure-all. But it does make it one of the more sensible uses of crypto capital going around.

And in a sector still drowning in token theater, that alone deserves attention.

Key questions and takeaways

What did Maelstrom’s Bitcoin Grant Program accomplish?
It funded five developers over 20 months, with four still active, and supported meaningful work on Bitcoin Core, Payjoin, Silent Payments, and cryptographic infrastructure.

Why does Bitcoin Core development matter so much?
Because Bitcoin Core is the reference software behind the network, and bugs in consensus code can cause nodes to disagree on Bitcoin’s state with no easy recovery path.

What is Payjoin?
Payjoin is a transaction method where both sender and receiver contribute inputs, making chain analysis harder and improving Bitcoin privacy.

What are Silent Payments?
Silent Payments let users receive Bitcoin through a reusable static address without on-chain address reuse, reducing a major privacy leak.

Why is privacy such a big deal for Bitcoin?
Because Bitcoin is transparent by design, and without privacy tools, chain surveillance firms can map transactions and user behavior far too easily.

Is minority adoption of privacy tools still useful?
Yes. Even limited Payjoin adoption can weaken surveillance heuristics across the network and improve privacy for everyone.

How is this grant program different from typical crypto funding?
It funds open-source Bitcoin work directly, pays in Bitcoin, and avoids token incentives and commercial strings that usually distort priorities.

What does this say about Bitcoin’s long-term resilience?
It shows that the network’s real strength comes from patient, technically difficult work on security, privacy, and protocol maintenance — not from hype.