| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | = Bitcoins = |
| | 4 | |
| | 5 | Tachanka! accepts bitcoins donations..... |
| | 6 | |
| | 7 | |
| | 8 | notes from email: |
| | 9 | |
| | 10 | * clearly point out its limits in protecting the sending users' privacy, |
| | 11 | just because there is a somewhat common misconception that bitcoin was a |
| | 12 | fully anonymous way of payment, and also because knowing these limits |
| | 13 | makes it easier for donors to donate |
| | 14 | |
| | 15 | http://eprint.iacr.org/2012/584.pdf |
| | 16 | |
| | 17 | * state how bitcoin can be better than standard bank transfers (possibly |
| | 18 | less monitoring and possibly more anonymity) |
| | 19 | |
| | 20 | * prefer (and state that we prefer) face-to-face donations with neither |
| | 21 | paper nor electronic trail whenever comfortably possible |
| | 22 | |
| | 23 | * explain how bitcoins can be bought in a couple places in the world in |
| | 24 | a way which preserves the donors' privacy as much as possible (think |
| | 25 | ukash, paysafecard, pre-paid credit cards, other kinds of pre-paid |
| | 26 | systems and vouchers) and with minimum losses in fees (which usually go |
| | 27 | to entities we specifically do not want to support); we should probably |
| | 28 | concentrate on the richer countries there (since this is where we'd hope |
| | 29 | most donations to come from) |
| | 30 | |
| | 31 | * generate bitcoin addresses in a way which maximizes donor privacy |
| | 32 | (e.g. I'm not sure whether it makes a difference in terms of a third |
| | 33 | party to correlate whether you create 100 addresses at the same or |
| | 34 | whether you spread it out across some days with random intervals) |
| | 35 | |
| | 36 | |
| | 37 | |
| | 38 | |
| | 39 | |
| | 40 | |
| | 41 | Description. |
| | 42 | |
| | 43 | == Related pages == |
| | 44 | |
| | 45 | [[TitleIndex()]] |