SRI - An independent, community run, 100% free and open-source reference implementation of the Stratum V2 protocol. https://xitter.cf/t.co/nqh0s7u1s6
Joined March 2022
- Tweets506
- Following0
- Followers3.5K
- Likes370
Pinned Tweet
We’re excited to welcome @AntPoolofficial @blocks @f2pool @FoundryServices @MARAFoundation_ @SpiderPool_com @DMND_Sv2 to the Stratum V2 Working Group.
With founding members @BraiinsMining, @spiral_btc, and FOSS community, their experience will help accelerate the protocol and adoption.
Stratum V2 retweeted
We’re excited to announce the Q3 2026 Btrust developer grant recipients. 🚀
Ten Bitcoin open-source developers are receiving support: five starter grant recipients and five long-term open-source cohort members.
This quarter also marks an important first: Btrust developer grants are going directly to developers outside Africa. Through our recent expansion of long-term grants across the Global Majority, we’re now supporting developers in Brazil 🇧🇷 and India 🇮🇳.
Their work, alongside that of recipients in Nigeria 🇳🇬 and Kenya 🇰🇪, spans @bitcoincoreorg, mining ⛏️ infrastructure, Lightning⚡, wallet libraries, and privacy-preserving payments.
Meet the recipients and learn about their work:
Stratum V2 retweeted
.@plebhash is a developer based in Brazil 🇧🇷 and another recipient of direct Btrust developer funding outside Africa.
His work focuses on @StratumV2, a protocol for communication between mining devices, proxies, and pools.
With the long-term grant, plebhash will maintain the specification and reference implementation, improve interoperability, and strengthen production reliability, helping developers and mining operators build on dependable open-source software.
Stratum V2 retweeted
Rare to report bugs and get a rebuilt security process back. Giant ups to the @StratumV2 team on the release, and thanks for being early with us.
New SV2 releases are out, bringing security hardening and various other improvements to our libraries and applications!
🧩 SV2 Protocol libs v1.12
🏗️ SV2 Apps v0.8
⛏️ SV2 UI v0.7 (coming soon on @umbrel)
Applications updates improve Job Declaration stability and Bitcoin Core integration, Translator Proxy overhaul, and add automatic discovery of ASIC telemetry endpoints.
Protocol library highlights include a deep hardening pass over channels_sv2, a breaking refactor of the codec and framing layer, BIP323 adaptations across the protocol stack. Noise_sv2 was improved with regards to memory hygiene, nonce reuse, RNG quality, and buffer recovery. Every published crate that changed takes an incompatible version bump, so downstream consumers should expect to adapt.
We’re proud to have been early participants in @ProjectLoupe . Their findings helped shape this release and gave us a head start in adapting how we triage reports, prioritize fixes, and organize development around security. Thank you to the Loupe team for their work and support!
New SV2 releases are out, bringing security hardening and various other improvements to our libraries and applications!
🧩 SV2 Protocol libs v1.12
🏗️ SV2 Apps v0.8
⛏️ SV2 UI v0.7 (coming soon on @umbrel)
Applications updates improve Job Declaration stability and Bitcoin Core integration, Translator Proxy overhaul, and add automatic discovery of ASIC telemetry endpoints.
Protocol library highlights include a deep hardening pass over channels_sv2, a breaking refactor of the codec and framing layer, BIP323 adaptations across the protocol stack. Noise_sv2 was improved with regards to memory hygiene, nonce reuse, RNG quality, and buffer recovery. Every published crate that changed takes an incompatible version bump, so downstream consumers should expect to adapt.
We’re proud to have been early participants in @ProjectLoupe . Their findings helped shape this release and gave us a head start in adapting how we triage reports, prioritize fixes, and organize development around security. Thank you to the Loupe team for their work and support!
Thanks to a growing community of contributors that made these new updates possible and to @btrustteam @HRF @OpenSats @spiral_xyz @Vinteum_org
for ensuring sustainability of the most active contributors.
Stratum V2 retweeted
Vinteum Grantee Spotlight: @plebhash
From Bitcoin Core IPC integration to Job Declaration and the Stratum V2 Working Group, Plebhash has been working on the infrastructure needed to bring @StratumV2 into production.
More from our fourth year: vinteum.org/4
Stratum V2 retweeted
What does Stratum V2 change for Bitcoin miners?
In the first episode of hashhuddle, f2pool sits down with independent @StratumV2 contributor @pavlenex to discuss mining efficiency, miner-built block templates and the path to wider adoption.
🎙️ Watch the conversation below.
Stratum V2 retweeted
Interviews at @ORIGINseoulBTC 2026 | SLP770
00:00 @gitgab19 of @StratumV2
15:38 @jimmykostro
29:10 @_checkmatey_ of @_checkonchain
Stratum V2 retweeted
We're excited to join this SV2 Working Group to further mining decentralized with client-side support in Mujina Firmware and server-side support in Hydrapool!
We’re pleased to welcome @256FOUNDATION to the Stratum V2 Working Group!
Through their support for open-source projects like Mujina and HydraPool, they’re helping make SV2 more accessible to miners and pool operators everywhere.
We’re pleased to welcome @256FOUNDATION to the Stratum V2 Working Group!
Through their support for open-source projects like Mujina and HydraPool, they’re helping make SV2 more accessible to miners and pool operators everywhere.
The @256FOUNDATION joins @AntPoolofficial @blocks @Braiins @DMND_Sv2 @f2pool @FoundryServices @mempool @SpiderPool_com @spiralbtc and FOSS community, in our mission to maintain an open, Bitcoin mining standard serving as a free public good for the entire mining ecosystem.
Stratum V2 retweeted
Update after 3 days of the stratum v2 experimental code. I'm very pleased with the performance of the protocol and plan to make it a permanent feature of solo ckpool. After a few more pool updates to tighten sv2 conformance and performance upgrades for anticipated heavy usage in future, everything is still running smoothly. At this point I'll let it run till next week unchanged, and if no further improvements come to mind and it remains stable I'll deploy it on all the solo pools as dual instance SV1/SV2 endpoints from all locations. This should be a transparent process to miners. Regular stratum mining should remain unaffected, and there should be no discernible downtime to miners.
Stratum V2 and solo.ckpool.org experiment.
sv2solo.ckpool.org:3336 - stratum V2
sv2solo.ckpool.org:3337 - stratum V2 with job declaration support
Pool Stats: sv2solo.ckpool.org/sv2pool
User Stats: sv2solo.ckpool.org/sv2users/…
I have experimental code implementing stratum V2 for ckpool and want to conduct an experiment to see how much demand there is for the protocol. This required a vast chunk of code in ckpool and I'd like to gauge what level of interest there is for supporting the protocol. If you are running an SV2 compatible miner, or have an SV2 proxy, and mining on solo ckpool, I'd appreciate testing of the implementation. This being experimental means it will likely not be a permanent setup, nor have guaranteed uptime whilst improvements/fixes are committed.
It's worth pointing out that although SV2 offers encrypted communications, privacy, protection against MiTM attacks, and some trivial decrease in bandwidth, adding an SV2 proxy at the client end adds latency compared to regular stratum, or hardware that natively supports SV2.
Far more important to point out, though, is that despite job declaration (mine your own transactions and templates) being the main feature people are seeking with implementing SV2, it is only of meaningful benefit for a shared (i.e. non-solo) pool as it adds quite a bit of latency that can not be obviated by the pool implementation, as the protocol will make clients refuse any templates from the pool. This is despite the fact the pool hardware is going to be vastly faster at updating blocks than client level implementations. Furthermore, if you are doing job declaration at your miner end, you already have _everything you need_ to mine solo locally at the miner, so there is precisely zero point using SV2 with job declaration to a solo pool apart from feeling good about the templates - you'll just waste a lot more work, and have a significantly higher risk of stale aka orphaned blocks.
That said, the experimental code has been created, and would still be useful for a non-solo install of ckpool. I'm curious to see how many miners will try it out. SV2 suffers from a chicken-and-egg problem that hardware doesn't support it because pools don't, and pools don't because hardware doesn't.
Stratum V2 retweeted
Huge endorsement for Stratum v2 the protocol and the reference implementation from OG mining software FOSS dev @ckpooldev. Appreciate the time you have taken.
The protocol was defined 7(!) years ago and reference implementation got underway 6(!) years ago. Dozens of developers have contributed to it from a variety of organizations. It is the epitome of a public good project. One that is neutral and good for the entire mining and pool ecosystem. Thank you to all who have contributed!
Update after 3 days of the stratum v2 experimental code. I'm very pleased with the performance of the protocol and plan to make it a permanent feature of solo ckpool. After a few more pool updates to tighten sv2 conformance and performance upgrades for anticipated heavy usage in future, everything is still running smoothly. At this point I'll let it run till next week unchanged, and if no further improvements come to mind and it remains stable I'll deploy it on all the solo pools as dual instance SV1/SV2 endpoints from all locations. This should be a transparent process to miners. Regular stratum mining should remain unaffected, and there should be no discernible downtime to miners.
Legendary @ckpooldev adds experimental SV2 endpoints.
stratum2+tcp://sv2solo.ckpool.org:3336/9anrRNhBh7869XtNnFcCuGBRZP51E635qGbu457J5kHdszhfRc3 - Non JD
stratum2+tcp://sv2solo.ckpool.org:3337/9anrRNhBh7869XtNnFcCuGBRZP51E635qGbu457J5kHdszhfRc3 - JD Support
Let's start with the SV2 UI. 🧑🎨
v0.5.O introduces fallback drag and drop feature, where you can define as many fallback pool as you like and prioritize their order.
Another new feature allows you to verify coinbase payout of a solo pool, ensuring your address is in the coinbase, otherwise SV2 falls back to a different pool.
New pool @_PyBlock_ added to the list of compatible solo pools with more pools to be added in the next release.
We fixed annoying issue where you could't copy the connection string is fixed - thanks everyone for reporting it!
Momentum for SV2 adoption continues to grow, with companies and projects across the mining ecosystem working on integrating SV2.
There’s already so much happening, and we’re only getting started. ⛏️
Thanks to a growing community of contributors that made these new updates possible and to @btrustteam @HRF @OpenSats @spiral_xyz @Vinteum_org
for ensuring sustainability of the most active contributors.
