principles.html.j2 (10058B)
1 {% extends "common/base.j2" %} 2 {% block subtitle %}{{ _("Principles")}}{% endblock subtitle %} 3 {% block body_content %} 4 <main id="maincontent"> 5 <style> 6 h2 { 7 margin-top: 1em; 8 } 9 </style> 10 11 <div class="container"> 12 <div class="row"> 13 <div class="col"> 14 <h1>{{ _("GNU Taler: Design Principles") }}</h1> 15 </div> 16 </div> 17 <p> 18 {% trans %} 19 When designing GNU Taler, we had the following design principles in mind: 20 {% endtrans %} 21 </p> 22 <div class="row"> 23 <div class="col-lg-12"> 24 <h2>{{ _("1. Free/Libre Software") }}</h2> 25 <a href="https://www.gnu.org/graphics/freedom.html"> 26 <img style="width:20vw;float:right" src="{{ url_static('images/1-libre.png') }}" alt="{{ _("... in the area of computing, freedom means not using proprietary software") }}"> 27 </a> 28 <p> 29 {% trans %} 30 GNU Taler must be <a href="https://www.gnu.org/philosophy/free-sw.html">Free/Libre Software</a>. 31 For merchants, Free/Libre Software prevents vendor lock-in, meaning 32 merchants can easily choose another service provider to process 33 their payments. 34 For countries, Free/Libre 35 software means GNU Taler can not compromise sovereignty by imposing 36 restrictions or requirements. And for exchange operators, transparency is crucial to satisfy 37 <a href="https://en.wikipedia.org/wiki/Kerckhoffs's_principle">Kerckhoffs's principle</a> 38 and to establish public confidence. 39 {% endtrans %} 40 </p> 41 <p> 42 {% trans %} 43 Customers benefit from Free/Libre Software because anyone is free to modify the wallet software to support additional platforms. 44 The source code must be available and make it easy to verify that user-hostile features such as tracking or telemetry are absent. 45 {% endtrans %} 46 </p> 47 </div> 48 </div> 49 <div class="row"> 50 <div class="col-lg-12"> 51 <h2 id="privacy">{{ _("2. Protect the privacy of buyers") }}</h2> 52 <!-- From https://www.pixabay.com/ --> 53 <img style="width:20vw;float:left;padding:15px" src="{{ url_static('images/2-buyer-privacy.png') }}" alt="{{_("You deserve some privacy")}}"> 54 <p> 55 {% trans %} 56 Privacy is most meaningful when it is guaranteed via technical measures, as opposed to mere 57 policies. Without a technical layer providing privacy-by-default, financial transactions 58 reveal unnecessary levels of personal or private data. This would be especially true 59 when making micropayments for online publications. Thus, GNU Taler must protect 60 the privacy of buyers to avoid facilitating totalitarian control over the population. 61 {% endtrans %} 62 63 {% trans %} 64 Limited private data, such as the shipping address for a physical 65 delivery, may need to be collected according to business needs 66 and protected according to local laws. In this case, GNU Taler must enable deletion 67 of such data as soon as it is no longer required. 68 {% endtrans %} 69 </p> 70 </div> 71 </div> 72 <div class="row"> 73 <div class="col-lg-12"> 74 <h2>{{ _("3. Auditability - enable the state to tax income and crack down on illegal business activities") }}</h2> 75 <!-- From https://www.pxhere.com/ --> 76 <img style="width:20vw;float:right;padding:15px" src="{{ url_static('images/3-taxable.png') }}" alt="{{_("Money laundering")}}"> 77 <p> 78 {% trans %} 79 As a payment system must comply with local laws in order to operate 80 legally, GNU Taler must be designed to comply with these 81 requirements. GNU Taler must provide an audit trail for investigators 82 operating under the law. 83 84 Furthermore, we consider levying of taxes as 85 beneficial to society, and fair taxation requires income transparency. 86 Thus, GNU Taler must enable authorities to track income. 87 {% endtrans %} 88 </p> 89 </div> 90 </div> 91 <div class="row"> 92 <div class="col-lg-12"> 93 <h2>{{ _("4. Prevent payment fraud") }}</h2> 94 <!-- From https://www.maxpixel.net/ --> 95 <img style="width:20vw;float:left;padding:15px" src="{{ url_static('images/4-fraud.png') }}" alt="{{_("Phishing attack")}}"> 96 <p> 97 {% trans %} 98 GNU Taler must mitigate the most common sources of payment fraud. 99 We must follow best practices in software design, 3rd party 100 design guidelines that prevent confusion and misleading user interfaces, 101 and must have others inspect our publicly available code. 102 103 Furthermore, GNU Taler must provide extensive cryptographic evidence for 104 all key processes to enable all parties to precisely attribute bad behavior. 105 {% endtrans %} 106 </p> 107 </div> 108 </div> 109 <div class="row"> 110 <div class="col-lg-12"> 111 <h2>{{ _("5. Collect the minimum information necessary") }}</h2> 112 <img style="width:20vw;float:right;padding:15px" src="{{ url_static('images/5-data-minimization.png') }}" alt="{{_("Privacy by design, privacy by default, General Data Protection Regulation (GDPR) compliant")}}"> 113 <p> 114 {% trans %} 115 The privacy of buyers is given particular priority as part of 116 <a href="#privacy">principle #2</a>. However, other parties - such as merchants - also 117 must have data protection. 118 119 Generally, GNU Taler must only collect the minimum information necessary: 120 Data that is not collected or is no longer stored cannot be compromised. 121 {% endtrans %} 122 </p> 123 </div> 124 </div> 125 <div class="row"> 126 <div class="col-lg-12"> 127 <h2>{{ _("6. Be usable") }}</h2> 128 <img style="width:20vw;float:left;padding:15px" src="{{ url_static('images/6-usable.png') }}" alt="{{_("Buy with one click. Easy for children.")}}"> 129 <p> 130 {% trans %} 131 GNU Taler must be usable for non-expert customers including 132 end-users of a GNU Taler wallet, merchants who wish to accept payments 133 using GNU Taler, and 3rd party application developers for e-commerce and 134 other platforms. 135 136 GNU Taler must follow best-practices usability guidelines and 137 incorporate feedback from experts and users. Free/Libre software also 138 requires Free/Libre documentation to allow for informed choices. 139 GNU Taler must provide well-documented Application Programming Interfaces (APIs) 140 to allow frictionless integrations between GNU Taler and other projects. 141 {% endtrans %} 142 </p> 143 </div> 144 </div> 145 <div class="row"> 146 <div class="col-lg-12"> 147 <h2>{{ _("7. Be efficient")}}</h2> 148 <img style="width:20vw;float:right;padding:15px" src="{{ url_static('images/7-efficient.png') }}" alt="{{_("Energy efficiency")}}"> 149 <p> 150 {% trans %} 151 GNU Taler must be designed to be efficient. 152 Quite simply, efficiency means fewer things to break, and it means more 153 transactions per second and lower environmental impact. Efficiency 154 is also critical for GNU Taler to be used for micropayments. 155 Therefore certain expensive primitives, such as proof-of-work, 156 must not be used by GNU Taler. 157 {% endtrans %} 158 </p> 159 </div> 160 </div> 161 <div class="row"> 162 <div class="col-lg-12"> 163 <h2>{{ _("8. Fault-tolerant design")}}</h2> 164 <img style="width:20vw;float:left;padding:15px" src="{{ url_static('images/8-fault-tolerant.png') }}" alt="{{_("Life Savers")}}"> 165 <p> 166 {% trans %} 167 Malicious operators, fat fingers, computer glitches, gremlins. Things 168 go wrong. 169 170 GNU Taler must be designed to tolerate failure of individual components and 171 systems. Where the system can continue running safely, it will continue 172 running safely. Where it must halt an operation, other operations 173 must not be needlessly pulled offline. Where systems fail, 174 they must fail gracefully. 175 176 GNU Taler must have a plan to recover from malicious operators 177 compromising core secrets. 178 {% endtrans %} 179 </p> 180 </div> 181 </div> 182 <div class="row"> 183 <div class="col-lg-12"> 184 <h2>{{ _("9. Foster competition")}}</h2> 185 <img style="width:20vw;float:right;padding:15px" src="{{ url_static('images/9-competition.png') }}" alt="{{_("A competitive market")}}"> 186 <p> 187 {% trans %} 188 It must be relatively easy for competitors to deploy interoperable alternatives. The 189 barriers for this in traditional financial systems are rather high and outside 190 of our control. However, GNU Taler must minimize the technical 191 burden for new competitors to enter the market. 192 193 GNU Taler must enable a diverse set of operators, breaking up the current 194 system where only a few global companies dominate the market. 195 196 An example of a design choice that supports this is to split the whole system into 197 smaller components that can be operated, developed and improved upon independently, 198 instead of having one completely monolithic system. 199 {% endtrans %} 200 </p> 201 </div> 202 </div> 203 </div> 204 </main> 205 206 207 {% endblock body_content %}