aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-08-15 16:28:45 +0200
committerRasmus Dahlberg <rasmus.dahlberg@kau.se>2021-08-15 16:28:45 +0200
commit42572f01c6d9f144529af192801b701488e5b4cf (patch)
tree7bea05288343e3606f51498e182b0c3479ada97a /README.md
parent3940ddec4512f7198c905a771d3515ca48683db2 (diff)
refactored landing page based on feedback from ln5
Diffstat (limited to 'README.md')
-rw-r--r--README.md14
1 files changed, 8 insertions, 6 deletions
diff --git a/README.md b/README.md
index ea31aec..19ce691 100644
--- a/README.md
+++ b/README.md
@@ -1,18 +1,20 @@
# The Sigsum Project
Sigsum is a free and open source project that brings transparency logging to
-**sig**ned check**sum**s. Logging _sigsums_ and not a concreter type like
+**sig**ned check**sum**s. Logging _sigsums_ and not a more concrete type like
_certificates_ keep the overall design simple and generally useful.
-&#10004; Minimalistic design that simplifies log operations and usage </br>
-&#10004; Centralised log operations but distributed trust assumptions </br>
-&#10004; Discoverability of claims for the data of your choice</br>
+&#10004; Minimalistic design that simplifies log operations and usage\
+&#10004; Centralised log operations but distributed trust assumptions\
+&#10004; Discoverability of statements for the data of your choice
-In other words, what you claim about your data is up to you. Examples could be
+A minimal statement encodes the following claim: the data has cryptographic hash
+X. You can add additional meaning to each statement. For example, you may use
+a sigsum log to claim that
_everyone gets the same news articles_,
_software package X builds reproducibly_, or
_a list of key-value pairs is maintained with policy Y_.
-Sigsum logging makes it reasonable to believe these claims by adding enough
+Sigsum logging makes it reasonable to believe your claims by adding enough
discoverability to verify them.
## Join the conversation