AIP-23: the proof kinds AERE produces, with their conformance envelopes (aips/aip23-kinds/: fifteen kinds, authorization, settlement and provenance added 2026-09-28; KINDS.json lists each kind's required fields); correction: the notary on chain 2800 has held digests since 2026-09-17 (the measured status of 2026-09-27 said nothing was notarized there), Errata 1

This commit is contained in:
Aere Network committed 2026-09-29 11:44:27 +03:00
1 parent f86746a376
commit a464214626
18 files changed
+816 -2

No files matched your search

+17 -2
View File
@@ -56,7 +56,8 @@ A proof is a JSON object:
- `statement` is the payload: what happened. Its `kind` names the proof type (`aere-proof-of-software`, `aere-proof-of-data`,
`aere-proof-of-ai`, `aere-proof-of-execution`, `aere-proof-of-identity`, `aere-proof-of-compliance`, ...). The type-specific
fields are that type's business; the protocol constrains only the envelope.
fields are that type's business; the protocol constrains only the envelope. The kinds AERE produces, with their fields and one
conformance envelope each, are listed in `aere-research/aips/aip23-kinds/` (added 2026-09-29).
- `statementHash` binds the statement.
- `signature` (optional) is the producer's signature over the canonical statement text.
- `notarization` (optional) records that `statementHash` was written to the on-chain notary. It is a claim of the producer; a
@@ -166,6 +167,10 @@ covering anchor post-quantum from the presence of a certificate; it is replaced
certificate check exists in one place. `node verify-proof.mjs <envelope.json> [--rpc <url>] [--chain 2800|28001] [--json]`.
- `aere-node/tools/proof-vectors/`: envelopes with their expected verdicts, a real Proof-of-Software attestation among them, and one
notarized on the public testnet 28001.
- `aere-research/aips/aip23-kinds/` (added 2026-09-29): the proof kinds AERE produces, fifteen on that date (data, execution,
identity, compliance, runtime, location, device, payment, ownership, time, block, authorization, settlement, provenance, AI; the
last three before AI were added on 2026-09-28), each with its required fields in `KINDS.json` and one envelope. A `settlement`
carries its transaction and block as 32-byte hashes as they are, never re-hashed; a `provenance` names a non-empty list of parents.
### Measured status (2026-09-27)
@@ -180,6 +185,15 @@ covering anchor post-quantum from the presence of a certificate; it is replaced
is refused by its code hash. With a check removed in a copy of the verifier (the header binding, the code hash, the node hash, the
anchor verdict), the corresponding case no longer gives the expected verdict, four of four.
- On chain 2800 nothing is notarized yet; there the verifier proves the absence of a hash from the certified state.
*Corrected 2026-09-29:* the sentence above was wrong when written. The notary on chain 2800 does hold digests (measured: one
first seen at 2026-09-17T21:08:06Z); what holds is that none of the published conformance vectors is notarized there, so for
them the verifier proves the absence of their hash from the certified state.
### Measured status (2026-09-29)
- Each of the fifteen envelopes in `aere-research/aips/aip23-kinds/` is `VALID` with the reference verifier offline (form and
integrity pass; signature and finality are `ABSENT`). The folder is written from one source, and a copy altered, a foreign file,
a kind without its description or a vector whose statement no longer hashes to its `statementHash` stops the publication.
### Adoption path
@@ -189,7 +203,8 @@ verification layer rather than one more product. Concretely: the verifier and ve
## Errata
None.
1. *2026-09-29, Measured status (2026-09-27), last item.* It said that nothing was notarized on chain 2800. The notary there held
digests from 2026-09-17; the statement was true only of the published conformance vectors. Corrected in place, with its date.
## Post-Acceptance Outcome Record