Hostile-read repairs across the kernel artifacts: 17 confirmed over-claims fixed to honest

A 6-lens hostile panel with adversarial verification confirmed 17 attacks that
would hold in a public takedown. All repaired: the MI contract now carries the
two base-fee floor-lapse windows (12,978,617-13,087,959 and
13,596,033-13,596,141) as explicit ruleset validation exceptions, so a stranger
implementing the written rules no longer halts where our own follower did; the
honesty boundary now states the full record of reject-on-disagreement including
the windows, and why the fact stays load-bearing; the independence claim is
bounded (upstream skeletons yes, AERE ruleset has one author in both forks, so
a common-author bug passes any differential gate by construction); the harness
verdict claims only what it measures, records engine identity via
web3_clientVersion on every run, refuses same-URL endpoint pairs, and prints
its NOT MEASURED block on every run; stage 4 names the live engine (upstream
parallel processing enabled by default, idling on empty blocks) and its
oracle's model limits; 'governed registry' became 'owner-controlled' with the
single-key fact stated. The panel also confirmed the import-proof doc claimed
a two-month validation history where six days is the truth; fixed.
This commit is contained in:
Aere Network committed 2026-08-15 23:28:24 +03:00
1 parent 46c42164de
commit f2ab368c36
5 files changed
+116 -19

No files matched your search

+1 -1
View File
@@ -6,7 +6,7 @@
*
* "Post-quantum" is not one algorithm frozen into the protocol. A chain that means to outlast the
* cryptography it ships must be able to add a scheme and retire another without a hard fork. AERE
* puts that in a governed on-chain registry, AereCryptoRegistry at
* puts that in an owner-controlled on-chain registry (the owner is a single-key account today, stated plainly rather than dressed as governance), AereCryptoRegistry at
* 0xaE6fC596bb3eCcbf5c5D02D67B0Ef065b3Afbaa5
* which maps each registered algorithm to the precompile that verifies it, its parameters, and a
* status. This tool asks the live chain to prove three things: