Skip to content

Commit

Permalink
More precise wording in SumDB claimant model (#2928)
Browse files Browse the repository at this point in the history
The old statement could be read to be making a promise about future states, which is not needed and brings in questions about falsifiability.
  • Loading branch information
mhutchinson authored Mar 7, 2023
1 parent c9a26cb commit 9a741e7
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/claimantmodel/Logs.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,4 +87,4 @@ The signature on each individual Statement<sup>DOMAIN</sup> can be omitted if bo
* Claimant<sup>DOMAIN</sup> and Claimant<sup>LOG</sup> are the same actor; and
* Every actor that is Believer<sup>DOMAIN</sup> is also Believer<sup>LOG</sup>

The signature on the Checkpoint effectively transitively signs each of the Claims within the log. This is what the [GoLang SumDB](https://blog.golang.org/module-mirror-launch) does. The Claim here is “*I, ${SumDB}, will return only $hash as the checksum for $module at $version*”. This is falsifiable; correct behaviour can be verified by confirming that no two entries in the log have the same module & version, but different checksums.
The signature on the Checkpoint effectively transitively signs each of the Claims within the log. This is what the [Go SumDB](https://blog.golang.org/module-mirror-launch) does. The Claim here is “*I, ${SumDB}, commit to $hash as the checksum for $module at $version*”. This is falsifiable; correct behaviour can be verified by confirming that no two entries committed to by the log have the same module & version, but different checksums.

0 comments on commit 9a741e7

Please sign in to comment.