Legal nTime capability classes

Legal nTime values can dispatch exact R4 low-bit capability classes while version and merkle context remain fixed.

Claim statusNO MINING ADVANTAGE CLAIM

Diagnostic work, exact algebra and local capabilities are not treated as end-to-end mining advantage.

Date2026-08-14

HardwareClassical exact verifier

Run scopeSeven registered variants

ReproducibilityFixed version/merkle context, exhaustive legal-interval class construction and independent dispatch tests.

01 / Question & hypothesis

What was tested?

Legal nTime values can dispatch exact R4 low-bit capability classes while version and merkle context remain fixed.

02 / Scientific basis

Why the test is meaningful

nTime is a legal header field that miners may vary within protocol and job constraints. With version and merkle context fixed, it changes early-round constants and can therefore select different exact low-bit capability classes without changing the nonce-domain semantics.

q = class(nTime | version, merkle fixed)activation(nTime)=capability ID or baselinedispatch error ⇔ selected formula differs from direct R4 output

FIGURE / RESULT READINGVisual reading of the published metrics and gates for EXP-016; it summarizes the registered result, not a mining advantage.

03 / Method

How it was tested

Enumerate the legal nTime interval, group exact context truth tables, compile activation metadata and test dispatch on 20,000 samples.

04 / Observed result

What happened

Dispatch tests20,000

Errors0

Header fieldnTime

The legal interval was exhausted for the registered low-four-bit class rule and dispatch validation reported zero errors.

05 / Validation

Exactness and statistical controls

The registered legal interval was enumerated to build classes, then 20,000 independent dispatch cases were checked with zero errors. Exhaustive class construction and sampled dispatch validation answer different questions and are reported separately.

06 / Interpretation

What the result means

nTime can select availability of a submotor capability. Frequency across nTime is not nonce-runtime economics.

Limitations

Legal nTime bounds depend on the mining job and consensus policy.
Class frequency over nTime is not nonce-frequency advantage.
Changing nTime can introduce operational coordination costs.

07 / Reproduction

Evidence trail

Fixed version/merkle context, exhaustive legal-interval class construction and independent dispatch tests.

Canonical variants

SUBENGINE-V16ASUBENGINE-V16BSUBENGINE-V16CSUBENGINE-V16DSUBENGINE-V16ESUBENGINE-V16FSUBENGINE-V16G

Source: internally audited canonical reports. Local filesystem structure, private headers and operational identifiers are excluded from publication.