The evidence pin is not a block receipt
A hash can be printed on a page and still never have been accepted by a block. The useful question is whether a running node stored that hash and can prove membership.
What is not proof
- A local signature count.
- An HTTP success from a registry.
- A query that only reports whether a hash is pinned.
What this software prepares
The seal signs the evidence, then hashes that signed message with SHA-256. The transaction name is PinEvidenceAnchor. The account is jil1evidenceanchor. Both already exist in the JIL Layer-1 engine. This product does not copy that engine and does not invent a transaction hash. The field chain_anchor stays empty until a running node returns an inclusion proof.
Three gas figures in that engine still disagree, and a fresh chain does not boot until the evidence account is pubkey-pinned at genesis. Those fixes belong in the Layer-1 repository. They are not claimed as done here.
Next: who operates this site.