Aere Network 6cb0140fae Republished from a clean root: the compiled artifact is gone from history, and the local line of work joins the sanitized public line

The public history carried kat/__pycache__/mlkem768_reference.cpython-314.pyc,
a compiled Python artifact embedding the operator's absolute local path. Text
secret scanners do not read compiled binaries, which is exactly how it slipped
through, and removing it from the tip would have left it reachable through the
old root commits. So this repository is republished from a single clean root.

This root also carries, from the previously unpublished line of work:
- corrected LICENSE year, LICENSING.md, VERIFY-POLICY.md, and
  CITATIONS-UNRESOLVED.md remeasured 2026-08-11 (101 paths, README aligned)
- O-018: run_consensus_verification.py ran 19 of 29 models and reported PASS;
  it now runs all 29, and computemarket_smt.py gains resolveByTimeout /
  reclaimUnsettled cases plus a negative control
- O-006: the word 'audited' removed from next to Bouncy Castle, twice, after a
  concurrent edit resurrected it
- O-014: prior art named and dated - Algorand's native falcon_verify shipped
  about ten months before AERE's precompiles; the primacy claim is withdrawn
  where it was implied
- bench/ scripts parametrized so they actually run for an outsider (the
  earlier textual sanitization left $STAGING unexpanded inside Python strings)
- AIP-2/AIP-3 errata with measured figures, spec remeasurements at 2026-08-01,
  and the spec-zk-stack retractions (owner is an operational key, not the
  Foundation; 'maximally sound' withdrawn; aggregator V1 deprecated)
The redacted bench-host environment files from the sanitized line are kept
exactly as published; the unredacted local variants are not carried.

2026-08-15 13:52:14 +03:00

2.3 KiB

Raw Blame History

AIP-N: Title in Title Case

Preamble

Field	Value
AIP	N
Title	Short descriptive title
Author	Name or handle
Type	Standards Track / Meta / Informational
Category	Core / Networking / Interface / ARC / (omit for Meta and Informational)
Status	Draft / Review / Last Call / Final / Living / Withdrawn / Stagnant
Created	YYYY-MM-DD
Requires	Comma-separated AIP numbers, or None
Ratification	Foundation-ratified (pre-decentralization), or the governance basis in force

Abstract

Two to four sentences. State what the AIP does in plain language. A reader should understand the whole change from this paragraph alone.

Motivation

Why this change is worth making. What problem it solves, who it helps, and what goes wrong without it. Be concrete. If the change is already live, say what prompted it.

Specification

The exact, unambiguous mechanism. This is the normative section. For a contract change, describe the interface, the state, the invariants, and the parameters with their values. For a consensus change, give the exact configuration keys and values and the activation point. Use MUST / SHOULD / MAY where a requirement is binding on implementers.

For anything that touches gas or size, cite only numbers that are measured on-chain or sourced from a repo fixture. Label any unmeasured number as "to be measured".

Rationale

Why the design is the way it is. Alternatives considered and why they were rejected. Trade-offs accepted.

Backwards Compatibility

What breaks, what does not, and how integrators migrate. "None" if nothing breaks.

Security Considerations

Attack surface, trust assumptions, and known weaknesses. This section is required and must be honest. If the change depends on a trusted operator, a small validator set, or an unaudited contract, say so here.

Reference Implementation and On-Chain Deployment

For a live change: the contract source path(s) in this repo, the canonical address(es) copied verbatim from sdk-js/src/addresses.ts, and the proving transaction hashes and block numbers where available. For a not-yet-live change: the branch or spec that implements it and the plan to ship.

2.3 KiB Raw Blame History