commit 0c166c7824a666dfa147bf44182bfaef78c09d98 parent 625cd044f277e6a48f0063c0c80fbec19228754b Author: Christian Grothoff <christian@grothoff.org> Date: Thu, 27 Jun 2019 16:22:27 +0200 img Diffstat:
| A | images/life-safer.jpg | | | 0 | |
| A | images/life-safer.medium.jpg | | | 0 | |
| M | principles.html.j2 | | | 11 | ++++++----- |
3 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/images/life-safer.jpg b/images/life-safer.jpg Binary files differ. diff --git a/images/life-safer.medium.jpg b/images/life-safer.medium.jpg Binary files differ. diff --git a/principles.html.j2 b/principles.html.j2 @@ -134,14 +134,15 @@ Approaches such as proof-of-work are ruled out by this requirement. Efficiency i </div> <div class="row"> <div class="col-lg-6"> - <!-- IMAGE. --> + <p><img style="width:40vw" src="../images/life-safer.medium.png" alt="Life Safers"></a></p> </div> <div class="col-lg-6"> - <h2>8. Avoid single points of failure</a></h2> + <h2>8. Fault-tolerant design</a></h2> <p> -While the design we present later is rather centralized, avoiding single -points of failure is still a goal. This manifests in architectural choices such -as the isolation of certain components, and auditing procedures. + Taler should tolerate failure of individual components and systems, + including malicious operators compromising core secrets. + This manifests in architectural choices such + as the isolation of certain components, and auditing procedures. </p> </div> </div>
