Repository navigation
docs(mirrors): register the HORIZON SHIELD mirror - #114
Closed
ogasurfproject-jpg wants to merge 1 commit into
Closed
ogasurfproject-jpg wants to merge 1 commit into
ogasurfproject-jpg wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018rPJAX4DKvmBS5CWM5jifv
Member
|
Closing as a duplicate of #115, which carried the same change with the updated description and is now merged. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Registers a second independent mirror, following
docs/mirroring.md.main, head athttps://api.github.com/repos/ogasurfproject-jpg/trace-registry-mirror/commits/main.maincarries no commit of ours and is at canonical0248406c5862as of this PR.:17and:47) from themirror-opsdefault branch, with themerge-base --is-ancestorgate from the recipe. On a refusal the mirror stays where it was and the run fails. Pushes use a deploy key scoped to the mirror repository. The job also keeps canonical's own workflows switched off in the mirror repository, so they never run there.One addition beyond the recipe, in case it helps with the witness time item in
ROADMAP.md: on each new head, and once a day otherwise, the mirror writes a canonical JSON record of what it observed (canonical head, our head, every registry NDJSON file at that head with its SHA-256, and each line's Merkle root and MMR checkpoint, copied and not re-verified) and stamps it with OpenTimestamps. The first record,witness/heads/2026/10/20261003T144635Z_0248406c5862.jsononmirror-ops, is anchored in Bitcoin block 969745. That fixes the observed head and checkpoint roots in time by a clock neither of us controls. It does not verify any signature, and it does not show that every observer saw the same history. Happy to change or drop it if it gets in the way.