Target-byte 0x3D tri-state closure
Applying the next target byte 0x3D to V51 defers should resolve nearly all remaining cases and reveal whether a zero-suffix deferral can still satisfy PoW.
Diagnostic work, exact algebra and local capabilities are not treated as end-to-end mining advantage.
What was tested?
Applying the next target byte 0x3D to V51 defers should resolve nearly all remaining cases and reveal whether a zero-suffix deferral can still satisfy PoW.
Why the test is meaningful
The same recursive comparison applies at the next byte. A tie defers to a suffix that, under the registered target boundary, is constrained to zero; testing these ties against full PoW determines whether the deferred branch has any valid support.
given V51=DEFER, compare b with 0x3Db<0x3D⇒ACCEPT; b>0x3D⇒REJECT; b=0x3D⇒DEFER_ZERO_SUFFIXvalid defer requires remaining digest suffix=0How it was tested
Evaluate two independent 20,000-record V51-deferred cohorts, classify against 0x3D, test all zero-suffix defers with full PoW and audit conditioning and action safety.
What happened
Replicate A produced 4,796 accepts, 15,126 rejects and 78 zero-suffix defers; B produced 4,770, 15,145 and 85. None of the 163 deferred records satisfied full PoW. All conditioning and safety errors were zero; incremental work was 152 units.
Exactness and statistical controls
Every deferred case was retained and fully evaluated; the zero-valid result was not inferred from probability. Independent replicate counts support the closure of this registered deferred branch.
What the result means
The 0x3D boundary is exact and the observed zero-suffix branch closes negatively. This narrows the target-comparison path without implying faster mining.
Limitations
- Zero valid defers is an empirical result for 163 observed ties.
- The registered target bytes define the scope.
- The capability remains comparison-only.
Evidence trail
Condition on V51 DEFER, apply the unsigned 0x3D comparison, fully evaluate every tie and require zero safety errors in both cohorts.
Canonical variants
SUBENGINE-V52ASUBENGINE-V52BSUBENGINE-V52CSource: internally audited canonical reports. Local filesystem structure, private headers and operational identifiers are excluded from publication.