[taler-anastasis] branch master updated: nana suggestion

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository anastasis.

The following commit(s) were added to refs/heads/master by this push:
     new ffd2133  nana suggestion
ffd2133 is described below

commit ffd2133341d7cf4415df13c9df88e0931705dd71
Author: Christian Grothoff <address@hidden>
AuthorDate: Mon Jan 27 19:47:42 2020 +0100

    nana suggestion
---
 doc/ledger.txt | 20 +++++++++-----------
 1 file changed, 9 insertions(+), 11 deletions(-)

diff --git a/doc/ledger.txt b/doc/ledger.txt
index 9e609d0..976064d 100644
--- a/doc/ledger.txt
+++ b/doc/ledger.txt
@@ -51,7 +51,7 @@ Challenge and Product / Service (1000 characters)
 -- Problem product addresses, how we overcome, Value-add
  -- core innovation
 
-NANA: more on the problem first? 
+NANA: more on the problem first?
 
 Anastasis enables ordinary users to remain in control of their data --
 including ensuring their data remains available to them --, even if
@@ -110,16 +110,14 @@ example:  
https://twitter.com/VitalikButerin/status/1219059083451326464
 
 How will your product improve citizen's control over their data: (500 
characters)
 
-NANA: this is a bit repetitive, maybe more on the use-cases here?
-
-Having core secrets is crucial for all scenarios where citizens are
-their own data controllers. While being one's own data controller is
-the best-case scenario for privacy, the availability of the core
-secret then becomes a crucial data security issue. Anastasis permits
-users to split the core secret across any number of semi-trusted
-providers. Users decide which combination of authentications and
-providers is required to recover the core secret, and the policy
-itself remains private.
+With core secrets users can be full control of all data encrypted with
+the core secret. As usually privacy and availability are desired, the
+secrecy and availability of the core secret is crucial. Anastasis
+splits the core secret across any number of semi-trusted
+providers. Users decide on the combination of authentication methods
+and providers. The policy itself remains private: The user stays
+private by design, and trade-offs between availability and
+confidentiality are minimized.
 
 
 IMPACT

-- 
To stop receiving notification emails like this one, please contact
address@hidden.