So, one way or the other, you still have to run Core? Kind of defeats the point of building your own blocks if you're forced into building them Core's way.
Today, we released a new version of SV2 Reference Implementation (SRI).
Starting today miners no longer need a custom BTC Core fork to build block templates with SV2. The bitcoin_core_sv2 crate is integrated into JDC and Pool, enabling direct communication with Bitcoin Core v30. This improves the UX and keeps SRI implementation-agnostic going forward.
With this release, we’re rolling out Docker support for SV2 Apps, making cross-platform deployments easier and shipping binaries for all major platforms. This is the first step toward a smoother UX. In the next release, we plan to ship UI for our miner-side apps: JDC and tProxy.
We’ve split the project into two repositories:
/stratum containing low-level protocol crates and /Sv2-Apps for end-user applications.
This makes the ecosystem easier to understand, contribute, and build on.
Want to test all the new improvements yourself?
Use our Web Deployment Wizard to spin up the full SV2 stack (Including your own pool) and share your feedback with the community.
https://stratumprotocol.org/get-started (for miners)
https://stratumprotocol.org/developers (for devs and full stack deployments)
Discussion
Quite the opposite, this makes us implementation agnostic even more it's just mining IPC that other implementations would have to port over so we can communicate with them out of the box.
So we don't have to use the bundled Core and can just configure any node via RPC?
If so, the page you linked needs an update:
When there’s an implementation with an ipc interface we will, so far Core is the only one.
Ah.
What's the advantage of the IPC interface vs. good old RPC?
Sjors nostr:nprofile1qqsgdp0taan9xwxadyc79nxl8svanu895yr8eyv0ytnss8p9tru047qpz3mhxue69uhhyetvv9ujuerpd46hxtnfduje6mks did a great writeup on RPC inefficiencies. https://github.com/Sjors/bitcoin/blob/sv2/doc/stratum-v2.md#advantage-over-getblocktemplate-rpc
