@imran-siddique thank you for merging #115. Our mirror of this registry runs every 30 minutes from ogasurfproject-jpg/trace-registry-mirror, fast-forwards only, and records each canonical head it sees with an OpenTimestamps proof.
A question in the other direction. Would someone at agentrust-io be willing to hold a copy of the NENRIN ledger (https://ledger.horizonshield.dev), the append-only, Bitcoin-anchored ledger of outside observations of agent endpoints that we operate?
Why it might be worth it to you: the ledger is where trace-pin-v0 anchors TRACE Trust Records (pinned by the sha256 of their RFC 8785 form, signature checked, postdated iat refused). A pin adds an outside bound on when a record existed, next to the transparency receipt the record already carries; a copy held by agentrust-io would mean those anchors do not depend on us alone. To be plain about the current state: no TRACE record from an outside party has been pinned yet.
What it takes: one workflow file, no secret and no key. Put nenrin-mirror.yml at .github/workflows/ in any repository and run it once. Every six hours it fetches mirror.py at a pinned commit (refused unless its sha256 matches), pulls what is new, verifies every digest offline, and commits the copy to a branch of that repository. It only reads the public ledger. A run of the same file in a repository of ours, https://github.com/ogasurfproject-jpg/nenrin-mirror-selftest/actions/runs/37319244914 , copied entries 1 to 68 and 7 records with no problem reported, content_sha256 661c3e3f347ab59dc35ad782735c066af2228649de9a0ef43a2af3e012f6fb64 (a self-held copy, so it does not count as independent).
What a copy establishes, and what it does not: that these bytes, with these digests, were obtainable from the ledger at a time, and that anyone holding the branch can recompute every digest offline. It does not establish that any claim in the ledger is true; each anchor is checked against Bitcoin headers with any OpenTimestamps client.
If you would rather not, that is a fine answer and it changes nothing about our mirror of this registry.
@imran-siddique thank you for merging #115. Our mirror of this registry runs every 30 minutes from
ogasurfproject-jpg/trace-registry-mirror, fast-forwards only, and records each canonical head it sees with an OpenTimestamps proof.A question in the other direction. Would someone at agentrust-io be willing to hold a copy of the NENRIN ledger (https://ledger.horizonshield.dev), the append-only, Bitcoin-anchored ledger of outside observations of agent endpoints that we operate?
Why it might be worth it to you: the ledger is where
trace-pin-v0anchors TRACE Trust Records (pinned by the sha256 of their RFC 8785 form, signature checked, postdatediatrefused). A pin adds an outside bound on when a record existed, next to the transparency receipt the record already carries; a copy held by agentrust-io would mean those anchors do not depend on us alone. To be plain about the current state: no TRACE record from an outside party has been pinned yet.What it takes: one workflow file, no secret and no key. Put
nenrin-mirror.ymlat.github/workflows/in any repository and run it once. Every six hours it fetchesmirror.pyat a pinned commit (refused unless its sha256 matches), pulls what is new, verifies every digest offline, and commits the copy to a branch of that repository. It only reads the public ledger. A run of the same file in a repository of ours, https://github.com/ogasurfproject-jpg/nenrin-mirror-selftest/actions/runs/37319244914 , copied entries 1 to 68 and 7 records with no problem reported, content_sha256661c3e3f347ab59dc35ad782735c066af2228649de9a0ef43a2af3e012f6fb64(a self-held copy, so it does not count as independent).What a copy establishes, and what it does not: that these bytes, with these digests, were obtainable from the ledger at a time, and that anyone holding the branch can recompute every digest offline. It does not establish that any claim in the ledger is true; each anchor is checked against Bitcoin headers with any OpenTimestamps client.
If you would rather not, that is a fine answer and it changes nothing about our mirror of this registry.