Pins a pasted GLEIF Golden Copy record to a SHA-256 digest as of a capture time you state, so a later reader can tell whether the entity data in front of them is the same data your evidence was built from.
GLEIF Golden CopyISO 17442CC0 1.0Zero PIIClient-side only
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Scope
This records that these exact bytes were pinned at the stated capture time. It is not a statement that the record is still current, not a validation of the entity data, and it carries no ongoing monitoring duty. One pin per run: no scheduler, no freshness promise, nothing to keep up to date afterwards.
⚠ The digest covers the raw bytes, exactly as pasted
Nothing is trimmed, case-folded, re-serialized or otherwise normalized before hashing. Leading and trailing whitespace, line endings and byte order all change the digest, which is the point: anyone holding the original file can reproduce this number, and a digest over a cleaned-up form could not be reproduced by anyone. Paste the record segment exactly as it came out of the file.
Paste in, never fetched
This page makes zero network calls. The GLEIF Golden Copy download page is named in the output for the reader to follow; it is never contacted from here. LEI reference data is public registry data published by GLEIF under CC0 1.0 Universal, so hashing and redistributing a pasted excerpt is licence-clean.
Presets
Snapshot
Execution Hash & §4 Artifact
SHA-256 execution hash (JCS canonical, RFC 8785):
Chain Handoff → art-600
Pass the execution_hash above as parent_hashes[0] when calling check_lei_relationship_consistency (art-600), so the relationship check is bound to the same pinned snapshot.