1 | -----BEGIN PGP SIGNED MESSAGE----- |
---|
2 | Hash: SHA256 |
---|
3 | |
---|
4 | ========= |
---|
5 | Donations |
---|
6 | ========= |
---|
7 | |
---|
8 | Donations to the Tahoe-LAFS project are welcome, and can be made to the |
---|
9 | following Bitcoin address: |
---|
10 | |
---|
11 | 1PxiFvW1jyLM5T6Q1YhpkCLxUh3Fw8saF3 |
---|
12 | |
---|
13 | The funds currently available to the project are visible through the |
---|
14 | blockchain explorer: |
---|
15 | |
---|
16 | https://blockchain.info/address/1PxiFvW1jyLM5T6Q1YhpkCLxUh3Fw8saF3 |
---|
17 | |
---|
18 | Governance |
---|
19 | ========== |
---|
20 | |
---|
21 | The Tahoe-LAFS Software Foundation manages these funds. Our intention is |
---|
22 | to use them for operational expenses (website hosting, test |
---|
23 | infrastructure, EC2 instance rental, and SSL certificates). Future uses |
---|
24 | might include developer summit expenses, bug bounties, contract services |
---|
25 | (e.g. graphic design for the web site, professional security review of |
---|
26 | codebases, development of features outside the core competencies of the |
---|
27 | main developers), and student sponsorships. |
---|
28 | |
---|
29 | The Foundation currently consists of secorp (Peter Secor), warner (Brian |
---|
30 | Warner), and zooko (Zooko Wilcox). |
---|
31 | |
---|
32 | Transparent Accounting |
---|
33 | ====================== |
---|
34 | |
---|
35 | Our current plan is to leave all funds in the main `1Pxi` key until they |
---|
36 | are spent. For each declared budget item, we will allocate a new public |
---|
37 | key, and transfer funds to that specific key before distributing them to |
---|
38 | the ultimate recipient. All expenditures can thus be tracked on the |
---|
39 | blockchain. |
---|
40 | |
---|
41 | Some day, we might choose to move the funds into a more sophisticated |
---|
42 | type of key (e.g. a 2-of-3 multisig address). If/when that happens, we |
---|
43 | will publish the new donation address, and transfer all funds to it. We |
---|
44 | will continue the plan of keeping all funds in the (new) primary |
---|
45 | donation address until they are spent. |
---|
46 | |
---|
47 | Expenditure Addresses |
---|
48 | ===================== |
---|
49 | |
---|
50 | This lists the public key used for each declared budget item. The individual |
---|
51 | payments will be recorded in a separate file (see `docs/expenses.rst`), which |
---|
52 | is not signed. All transactions from the main `1Pxi` key should be to some |
---|
53 | key on this list. |
---|
54 | |
---|
55 | * Initial testing (warner) |
---|
56 | 1387fFG7Jg1iwCzfmQ34FwUva7RnC6ZHYG |
---|
57 | one-time 0.01 BTC deposit+withdrawal |
---|
58 | |
---|
59 | * tahoe-lafs.org DNS registration (paid by warner) |
---|
60 | 1552pt6wpudVCRcJaU14T7tAk8grpUza4D |
---|
61 | ~$15/yr for DNS |
---|
62 | |
---|
63 | * tahoe-lafs.org SSL certificates (paid by warner) |
---|
64 | $0-$50/yr, ending 2015 (when we switched to LetsEncrypt) |
---|
65 | 1EkT8yLvQhnjnLpJ6bNFCfAHJrM9yDjsqa |
---|
66 | |
---|
67 | * website/dev-server hosting (on Linode, paid by secorp) |
---|
68 | ~$20-$25/mo, 2007-present |
---|
69 | 1MSWNt1R1fohYxgaMV7gJSWbYjkGbXzKWu (<= may-2016) |
---|
70 | 1NHgVsq1nAU9x1Bb8Rs5K3SNtzEH95C5kU (>= jun-2016) |
---|
71 | |
---|
72 | * 2016 Tahoe Summit expenses: venue rental, team dinners (paid by warner) |
---|
73 | ~$1020 |
---|
74 | 1DskmM8uCvmvTKjPbeDgfmVsGifZCmxouG |
---|
75 | |
---|
76 | * Aspiration contract |
---|
77 | $300k-$350k (first phase, 2019) |
---|
78 | $800k (second phase, 2020) |
---|
79 | 1gDXYQNH4kCJ8Dk7kgiztfjNUaA1KJcHv |
---|
80 | |
---|
81 | * OpenCollective development work (2023) |
---|
82 | ~$260k |
---|
83 | 1KZYr8UU2XjuEdSPzn2pF8eRPZZvffByDf |
---|
84 | |
---|
85 | |
---|
86 | Historical Donation Addresses |
---|
87 | ============================= |
---|
88 | |
---|
89 | The Tahoe project has had a couple of different donation addresses over |
---|
90 | the years, managed by different people. All of these funds have been (or |
---|
91 | will be) transferred to the current primary donation address (`1Pxi`). |
---|
92 | |
---|
93 | * 13GrdS9aLXoEbcptBLQi7ffTsVsPR7ubWE (21-Aug-2010 - 23-Aug-2010) |
---|
94 | Managed by secorp, total receipts: 17 BTC |
---|
95 | * 19jzBxijUeLvcMVpUYXcRr5kGG3ThWgx4P (23-Aug-2010 - 29-Jan-2013) |
---|
96 | Managed by secorp, total receipts: 358.520276 BTC |
---|
97 | * 14WTbezUqWSD3gLhmXjHD66jVg7CwqkgMc (24-May-2013 - 21-Mar-2016) |
---|
98 | Managed by luckyredhot, total receipts: 3.97784278 BTC |
---|
99 | stored in 19jXek4HRL54JrEwNPyEzitPnkew8XPkd8 |
---|
100 | * 1PxiFvW1jyLM5T6Q1YhpkCLxUh3Fw8saF3 (21-Mar-2016 - present) |
---|
101 | Managed by warner, backups with others |
---|
102 | |
---|
103 | Validation |
---|
104 | ========== |
---|
105 | |
---|
106 | This document is signed by the Tahoe-LAFS Release-Signing Key (GPG keyid |
---|
107 | 2048R/68666A7A, fingerprint E34E 62D0 6D0E 69CF CA41 79FF BDE0 D31D 6866 |
---|
108 | 6A7A). It is also committed to the Tahoe source tree |
---|
109 | (https://github.com/tahoe-lafs/tahoe-lafs.git) as `docs/donations.rst`. |
---|
110 | Both actions require access to secrets held closely by Tahoe developers. |
---|
111 | |
---|
112 | signed: Brian Warner, 25-Oct-2023 |
---|
113 | |
---|
114 | |
---|
115 | -----BEGIN PGP SIGNATURE----- |
---|
116 | |
---|
117 | iQEzBAEBCAAdFiEE405i0G0Oac/KQXn/veDTHWhmanoFAmU5YZMACgkQveDTHWhm |
---|
118 | anqt+ggAo2kulNmjrWA5VhqE8i6ckkxQMRVY4y0LAfiI0ho/505ZBZvpoh/Ze31x |
---|
119 | ZJj4DczHmZM+m3L+fZyubT4ldagYEojtwkYmxHAQz2DIV4PrdjsUQWyvkNcTBZWu |
---|
120 | y5mR5ATk3EYRa19xGEosWK1OzW2kgRbpAbznuWsdxxw9vNENBrolGRsyJqRQHCiV |
---|
121 | /4UkrGiOegaJSFMKy2dCyDF3ExD6wT9+fdqC5xDJZjhD+SUDJnD4oWLYLroj//v1 |
---|
122 | sy4J+/ElNU9oaC0jDb9fx1ECk+u6B+YiaYlW/MrZNqzKCM/76yZ8sA2+ynsOHGtL |
---|
123 | bPFpLJjX6gBwHkMqvkWhsJEojxkFVQ== |
---|
124 | =gxlb |
---|
125 | -----END PGP SIGNATURE----- |
---|