add canonical sigchain bundle format
This commit is contained in:
parent
76eb785ee2
commit
decff4b995
14 changed files with 1515 additions and 42 deletions
|
|
@ -103,6 +103,23 @@ generated wire vectors. Those later workflows must preserve the same explicit
|
|||
trust tuple and Authority v1 semantics; they must not introduce a compatibility
|
||||
route for the removed static format.
|
||||
|
||||
The verifier also accepts the canonical `.sscb` on-disk bundle. JSONL is a
|
||||
human-facing record interchange and does not preserve standalone head claims or
|
||||
anchor receipts. Convert between them with:
|
||||
|
||||
```sh
|
||||
geth keychain bundle-create --in chain.jsonl --out chain.sscb
|
||||
geth keychain bundle-extract --in chain.sscb --out chain.jsonl
|
||||
```
|
||||
|
||||
The canonical bundle keeps disclosures separate from signed record objects and
|
||||
sorts every object class deterministically. Adding a disclosure changes the
|
||||
bundle hash but not the chain head. The same file is the simple static HTTP
|
||||
distribution artifact at
|
||||
`/.well-known/sshsigchain/v1/<chain-id>/chain.sscb`. Distribution is untrusted:
|
||||
the configured root, authority replay, anchor policy, locally accepted head,
|
||||
and fork checks still decide acceptance.
|
||||
|
||||
## Local commands
|
||||
|
||||
Bootstrap an owner node:
|
||||
|
|
|
|||
Loading…
Reference in a new issue