{"endpoint": "midas-ops-anchor", "sealed": false, "seal_count": 0, "last_seal": null, "seals": [], "signer_address": null, "what_this_proves": "The anchor proves the attestation registry's LIST was not pruned or reordered as of the last seal's date -- it does NOT prove any individual verdict is correct (the EIP-712 signature on each attestation already does that), and it does NOT make the registry permanent -- what sustains Algorand's history is its archival nodes, same as pins sustain IPFS. See docs/ALGORAND_ANCHOR_SPEC.md for the canonical digest, the chain, and a publishable test vector a third party can recompute independently.", "test_vector": {"description": "Un registro de ejemplo y su digest esperado, publicados junto a la spec para que 'reproducible' sea algo que cualquiera puede chequear, no una afirmacion que nadie verifica.", "example_record": {"b": 2, "a": 1}, "expected_canonical_json": "{\"a\":1,\"b\":2}", "expected_record_digest_hex": "43258cff783fe7036d8a43033f830adfc60ec037382473548ac742b888292777"}, "note": "No seal has landed yet on this deployment. Sealing runs separately (run_daily_seal.py, on a daily cadence via algorand_anchor_scheduler.py) against the live attestation registry -- this route only serves what that process already wrote."}