Forward contextual lane from W3
For a fixed job, the early nonce-dependent lane begins from one 32-bit source W3 with exact A4/E4 translations.
Diagnostic work, exact algebra and local capabilities are not treated as end-to-end mining advantage.
What was tested?
For a fixed job, the early nonce-dependent lane begins from one 32-bit source W3 with exact A4/E4 translations.
Why the test is meaningful
In the second SHA-256 block of a fixed Bitcoin header, the nonce enters the message schedule through W3 while earlier schedule words are fixed. Before that dependency reaches the state, R0–R2 remain constant; at the first affected round, modular state words become exact translations of W3.
W₃ = nonce under the registered word conventionA₄(W₃)=C_A+W₃ (mod 2³²)E₄(W₃)=C_E+W₃ (mod 2³²)How it was tested
Freeze a Bitcoin-format job, confirm R0–R2 constancy, vary W3 and test the modular A4/E4 relations through the forward context pipeline.
What happened
Across 150,000 samples, pre-R3 constancy and relation errors were zero. The first nonce-dependent round was isolated exactly.
Exactness and statistical controls
Pre-R3 constancy and both modular relations were checked against direct SHA-256 state evolution on 150,000 W3 samples. Zero relation errors makes this an identity for the frozen job context, not a fitted regression.
What the result means
The lane reduces representation to one source at this point, but downstream work and per-job setup remain.
Limitations
- Constants change with the header context.
- Later rounds restore nonlinear dependence.
- A one-source representation does not reduce the nonce search space.
Evidence trail
Fixed-job constants plus independent W3 samples, checked against full early-round computation.
Canonical variants
SUBENGINE-V10ASUBENGINE-V10BSUBENGINE-V10CSUBENGINE-V10DSUBENGINE-V10ESUBENGINE-V10FSUBENGINE-V10GSource: internally audited canonical reports. Local filesystem structure, private headers and operational identifiers are excluded from publication.