generated from complexitycollapse/default-template
-
Notifications
You must be signed in to change notification settings - Fork 0
Metaformat
complexitycollapse edited this page Nov 4, 2021
·
1 revision
Every Commonplace leaf has a leaf header, which is a JSON file documenting
- The Commonplace format version
- The public key of the user who signs the document
- The signature of the left content, unless the data is in-band, in which case the signature is omitted
- The type of the data contained in the leaf
The name of the leaf is the signature of the header (or of header+content when they are in-band). The signer is identified by the public key in the header.
Alternatives: the name could be a public key/name pair, and the server returns proof that the payload is correct (e.g. a signed binding of name and key to the hash of the data). This means that the name doesn't itself reference the header, just the content. This has major advantages, such as allowing the hash algorithm to be updated later.