[taler-anastasis] branch master updated: text

[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 2cec6c7  text
2cec6c7 is described below

commit 2cec6c714ee8d0cbaaac895ee423c7d4841e6605
Author: Christian Grothoff <address@hidden>
AuthorDate: Mon Jan 27 11:43:47 2020 +0100

    text
---
 doc/ledger.txt | 23 ++++++++++++++---------
 1 file changed, 14 insertions(+), 9 deletions(-)

diff --git a/doc/ledger.txt b/doc/ledger.txt
index 119c256..ecd532d 100644
--- a/doc/ledger.txt
+++ b/doc/ledger.txt
@@ -59,7 +59,7 @@ Our approach is to split the information needed to recover 
the data
 across multiple independent operators. These providers will then use
 orthogonal authentication techniques to enable users to recover their
 key material. For authentication, we will plug into existing services
-for to send SMS or snail mail, or perform video identification.  The
+to send SMS or snail mail, or perform video identification. Our
 protocol is designed to minimize information disclosure, ensuring that
 operators learn as little information as necessary.
 
@@ -76,11 +76,9 @@ Description of research component (500 characters)
 Secret splitting is a well-known technique for distributing
 trust. Given that the user is fully trusted, the Anastasis scenario is
 actually a simple form of secret splitting, as no distributed key
-generation is required. However, at the same time Anastasis would
-likely be one of the first secret splitting services to be offered to
-end-users.  While the protocol offers privacy-by-design, it requires
-private inputs in the user interface. Thus the UX is the real research
-challenge.
+generation is required. However, Anastasis would likely be the first
+secret splitting services to be offered to end-users. Thus ease of
+use and low operating costs are the real research challenges.
 
 Technology description: (500 characters)
 -- how does it work, architecture
@@ -136,8 +134,15 @@ provider to be included in their product offering. In 
particular, we
 have an agreement with Taler Systems SA, which will integrate our
 protocol with their software and additionally pay us to operate an
 Anastasis server for Taler users. Similar discussions are ongoing with
-other companies. At a later stage, the service will operate on
-payments from its users.
+other organizations, in particular pretty Easy privacy SA and the Web3
+foundation. The initial software development will focus on offering a
+fully automated service, where authentication procedures such as
+sending SMS or snail mail are outsourced to specialized service
+providers. The objective is to be able to operate the service at
+minimum cost to attain profitability as soon as possible.  At a later
+stage, the service will operate on payments from its users. Given the
+nature of the Web service, it should technically be able to scale to
+billions of users.
 
 
 Business model (500 c)
@@ -231,7 +236,7 @@ How will we use LEDGER grant and services (500 c):
 LEDGER funding will largely be used to pay for the initial development
 cost. Here a core objective is to achieve an integration with existing
 cloud services for authentication that enables Anastasis to operate
-fully automatically, with video identification being outsourced to
+fully automatically, with authentication operations being outsourced to
 existing service providers. The LEDGER consortium may also help us
 find contacts with other businesses that would benefit from
 integrating key recovery with their product offerings.

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