diff options
-rw-r--r-- | images/life-safer.jpg | bin | 0 -> 803370 bytes | |||
-rw-r--r-- | images/life-safer.medium.jpg | bin | 0 -> 305571 bytes | |||
-rw-r--r-- | 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 differnew file mode 100644 index 00000000..0105be65 --- /dev/null +++ b/images/life-safer.jpg diff --git a/images/life-safer.medium.jpg b/images/life-safer.medium.jpg Binary files differnew file mode 100644 index 00000000..a5ff9314 --- /dev/null +++ b/images/life-safer.medium.jpg diff --git a/principles.html.j2 b/principles.html.j2 index 55e49568..0c8c7d86 100644 --- 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> |