Repository navigation
next: cloud-copy join returns the log URL and genesis item - #630
Merged
Merged
Conversation
…item A joining device must pin the collection's genesis (sync.json genesis_hash) before trusting the log; the answer now returns the exact appended seq-1 bytes (candidate bytes the device verifies against its trust pins), as create does.
callumalpass
enabled auto-merge
October 6, 2026 05:45
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Oct 6, 2026
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
1 participant
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.
A device joining a cloud copy has to pin the collection's genesis (
sync.jsongenesis_hash) before it trusts the log. The create answer already returns the genesis; this makes the join answer (POST /v1/next/collections/:id/devices) carry it too, aslog_urlandgenesis: {seq: 1, item}. Those are the exact appended seq-1 bytes. They are candidate bytes only: the daemon verifies them against its trust pins.