From 8c1e8d926a0c98fa2c67ed277c725983d22f5d0a Mon Sep 17 00:00:00 2001 From: Pavlenex <36959754+pavlenex@users.noreply.github.com> Date: Fri, 28 Apr 2023 09:33:44 +0200 Subject: [PATCH 1/2] improve hero copy improve hero copy to be more technically correct and avoid confusion --- src/index.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/index.md b/src/index.md index 748f469..ba65476 100644 --- a/src/index.md +++ b/src/index.md @@ -4,8 +4,7 @@ layout: Home background: /assets/hero-background.jpg heroImage: /assets/stratum-v2-icon-with-text.svg heroText1: Stratum V2 is the next generation protocol for pooled mining. It increases security, makes data transfers more efficient, and reduces mining infrastructure requirements. It also introduces three new sub-protocols that let miners select transaction sets and -heroTextHighlight: improve decentralization -heroText2: by negotiating with pools. +heroTextHighlight: improve decentralization. tagline: One giant leap for bitcoin mining documentationCtaText: Get started documentationCtaLink: /getting-started From 4b0e077166ec332e9d304dbc91fb83773342d361 Mon Sep 17 00:00:00 2001 From: Pavlenex <36959754+pavlenex@users.noreply.github.com> Date: Fri, 28 Apr 2023 09:35:53 +0200 Subject: [PATCH 2/2] rewrite text to cater to new Job Declaration --- src/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/index.md b/src/index.md index ba65476..88e5501 100644 --- a/src/index.md +++ b/src/index.md @@ -28,7 +28,7 @@ configurationTabs: value: config_A visualSrc: /assets/config-a.svg mobileVisualSrc: /assets/config-a-mobile.svg - textContent: Before Stratum V2, transaction sets were selected by pools. With this SV2 configuration they’re selected by individual miners, making the network more censorship-resistant. Miners run SV2 firmware, connecting to the SV2 proxy server. Miners can pick their transactions locally and negotiate them with an SV2 pool. + textContent: Before Stratum V2, transaction sets were selected by pools. With this SV2 configuration they’re selected by individual miners, making the network more censorship-resistant. Miners run SV2 firmware, connecting to the SV2 proxy server. Miners can pick their transactions locally and declare them to an SV2 pool. - name: Config B value: config_B visualSrc: /assets/config-b.svg @@ -43,13 +43,13 @@ configurationTabs: value: config_D visualSrc: /assets/config-d.svg mobileVisualSrc: /assets/config-d-mobile.svg - textContent: In this configuration miners run mining devices with SV1 firmware and connect to the translation proxy which translates the SV1 to SV2 messages and sends them to the SV2 pool. Transaction selection is done by the miners locally and then negotiated with the pool. + textContent: In this configuration miners run mining devices with SV1 firmware and connect to the translation proxy which translates the SV1 to SV2 messages and sends them to the SV2 pool. Transaction selection is done by the miners locally and then declared to the pool. roadmapTitle: Progress and Roadmap roadmapTagline: This is where the Stratum V2 protocol’s progress currently stands. roadmapSteps: - __MVP1__ will allow users to run SV2 where a miner runs existing SV1 firmware with a proxy that translates messages into SV2. In this configuration, the pool selects transactions. - A pull request that implements a **block template provider** will be submitted to the Bitcoin Core repository for review which will make MVP1 complete. - - Implement the **job negotiator**, which a miner or miners can use to negotiate a block template with a pool. + - Implement the **job negotiator**, which a miner or miners can use to declare a block template to a pool. - Once a translator, template provider, and job negotiator are running, we will launch an MVP2. In this configuration, a miner handles mempool transaction selection, and the pool accepts it. - Apply early adopter feedback and tailor configurations that will move MVP1 and MVP2 from beta to production-ready. # Specification authors section