# The measurement law and its three corollaries

> Canonical: https://blazephoenix.xyz/learn/the-measurement-law/
> License: CC BY-NC-ND 4.0 (attribution + link) · © 2026 BlazePhoenix
> Updated: 2026-11-16

Metrological Design means building a contract as an instrument: code that believes is attack surface, code that measures is defence. The contract never acts on a modelled, nominal or assumed value when an on-chain measurement exists, and treats whatever a proposer supplies (a route, a declared fee, a claimed depth, a pool id) as a coordinate to read for itself and fail closed on.

## The short answer

Metrological Design means building a contract as an instrument. Its thesis in one line: code that believes is attack surface; code that measures is defence. The working form is the measurement principle: the contract never acts on a modelled, nominal or assumed value when an on-chain measurement exists. Whatever a proposer supplies (a route, a declared fee, a claimed depth, a pool id) is a coordinate, a place to point the instrument, which the contract then reads for itself and fails closed on.

## The law underneath

No permissionless datum may choose a venue's shape or domain, the (factory, init-code-hash) pair that identifies it, or lower a floor. A security parameter comes only from an immutable or a sealed source. The measurement principle is the working form of that law.

## The three corollaries



## What gets classified

The repository publishes the classification of every caller-writable field under this rule, in docs/assurance/fields.json. The whitepaper reports 25 fields: 17 confirmed against an observation, 5 steering, 3 declared with the reason. The registry's ranking, the protocol floor and the fee base are computed only from confirmed quantities (docs/AUDIT_METHOD.md, lines 74 to 79).

## The nine public guarantees, one by one

The README lists nine public guarantees (lines 239 and 246 to 254). Each can be traced to a measurement or a named check. File names below are under test/ in the DEX repository at 969bcc6.

## Where measurement ends

Some numbers can be neither measured nor re-derived: a caller's floor, a caller's declared scale, the caller's own minimum. For those the discipline allows two other exits, re-homing and monotonicity, covered in the article on monotonicity against the caller.

The instrument is calibrated too: each assurance instrument was checked against a defect already known by another route before its number was printed (whitepaper section 15).

## Check it yourself



**Verify it yourself:** In a clean checkout of Blaze-Phoenix-Dex at 969bcc6: sed -n 239p README.md; awk 'NR>=246 && NR<=254' README.md; sed -n 74,79p docs/AUDIT_METHOD.md; open docs/assurance/fields.json. Whitepaper 2.4: section 2.3 (the law and the corollaries) and Appendix C (the reproduction commands, including the release-profile size build).

Related: https://blazephoenix.xyz/learn/measured-not-nominal/ · https://blazephoenix.xyz/learn/verify-your-instrument/ · https://blazephoenix.xyz/learn/monotonicity-against-the-caller/ · https://blazephoenix.xyz/learn/absence-is-not-a-value/
