Verifyalphainvariants

Security invariants

Which security invariants and failure cases can be checked from outside?

Source and guide ↗
flop invariants --help

A security rule is broader than a passing API check. Explore the failure matrix, see the exact rule and find the evidence still missing.

Yellowpaper / sections 11 and 13

Where the evidence stops

Recorded, not live
Scoped match18

Some public fields agree. Read the remaining gaps.

Mismatch0

A scoped check found a disagreement.

No data14

A mapped check lacks usable evidence.

Not observable46

No current check can establish this rule.

Counts are source rows, not a security score. A scoped match leaves the rest of that rule open.
Evidence captured from to . Individual source times are inside each cell.
Actor by failure

Find the rule. Open the gap.

verifierComplete
indexerComplete
harnessComplete
specComplete

Recorded evidence. No devnet requests on this page.

54 of 78 source rows match. Open a cell for its quote and checks.

Page 1 of 4

Miner

Read the evidence in order

Quote. Observe. Bound the claim.

Start with the rule

The pinned paper describes requirements. Every row keeps its quote, source lines and explicit gaps.

Inspect the observation

The verifier, indexer audit, harness and spec differ run their existing checks against raw recordings.

Keep the boundary

Agreement in public fields cannot prove runtime enforcement, honest execution or consensus finality.

Download raw inputs

The page rechecks immutable recordings. It does not run attacks, submit transactions or refresh public endpoints. The report download preserves the original page evaluation time.