Project

General

Profile

Feature #12268

Feature #12035: Donation campaign 2017

Make it so most Bitcoin donations arrive directly on RiseupLabs' Coinbase account

Added by intrigeri 10 months ago. Updated 28 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Fundraising
Target version:
Start date:
02/27/2017
Due date:
% Done:

10%

QA Check:
Feature Branch:
Type of work:
Website
Blueprint:
Starter:
Affected tool:

Description

This will simplify things both for our accounting team and for our fiscal sponsor (RiseupLabs). Ideally we would point most visitors to RiseupLabs' Coinbase address, and a small fraction of them to our own Bitcoin address, so that we keep some Bitcoin under our own control and can use them directly without converting to a fiat currency first.

Implementation options:

  • High-tech: a little bit of JavaScript (very similar to the code that picks a random mirror for downloads) should do the job.
    • pros: do the work once and forget it; the ratio can easily be adjusted dynamically
    • cons: some initial dev work (probably 20-40 SLOC, let's say 2 hours of work including debugging + review & merge)
    • intrigeri could do it (or find someone else to do it) at some point in 2017, if we decide this is the best option
  • Low-tech: point to our own Bitcoin address most of the year, and point to RiseupLabs' one during our yearly donation campaign.
    • pros: very little work
    • cons: we need to keep track of this forever, to avoid forgetting to switch to the other address when relevant
    • intrigeri is not excited at the idea of tracking all this, but volunteers anyway to create 3 sub-tickets of the 2017 donation campaign: switching to RiseupLabs' address, switching back, and creating the same tickets for 2018

History

#1 Updated by intrigeri 10 months ago

  • Status changed from Confirmed to In Progress
  • Assignee changed from intrigeri to sajolida
  • % Done changed from 0 to 10
  • QA Check set to Info Needed

Which one do you prefer? Is the effort to write, debug, review, merge, and maintain a tiny bit of trivial JS worth it in your opinion?

#3 Updated by intrigeri 10 months ago

  • Parent task set to #12035

#4 Updated by anonym 9 months ago

  • Target version changed from Tails_2.11 to Tails_2.12

#5 Updated by sajolida 8 months ago

  • Target version changed from Tails_2.12 to Tails_3.0

#6 Updated by sajolida 7 months ago

My next step would be to explain this to Ulrike and hopefully transfer this to her :)

#7 Updated by sajolida 7 months ago

  • Target version changed from Tails_3.0 to Tails_3.1

I'll see her next time around 3.1.

#8 Updated by sajolida 3 months ago

  • Target version changed from Tails_3.1 to Tails_3.2

#9 Updated by sajolida 3 months ago

  • Assignee changed from sajolida to u
  • Target version changed from Tails_3.2 to Tails_3.3
  • QA Check deleted (Info Needed)

I'll let Ulrike handle this as part of this year's campaign.

Ulrike: is our plan pretty much clear from this ticket?

#10 Updated by u 2 months ago

The plan is clear, but I have to say I'm not sure about the usefulness of this.
During the donation campaign we should ideally point everybody to Riseup's account in order to better track the money we received, no?

#11 Updated by intrigeri 2 months ago

The plan is clear,

Good :)

but I have to say I'm not sure about the usefulness of this.

Any of the two proposed options will avoid repeating (most of) the boring work that I did last year to sell the BTC we've received during the donation campaign. I don't wish anyone to do the same. Last year we had no choice so I did it, but this year we can anticipate and avoid putting ourselves in a painful situation, thanks to this ticket :)

Given the low-tech option described here is super cheap, its cost/benefit seems extremely favorable to me.

The cost/benefit of the high-tech option is less clear-cut. Its main benefit is: it allows us to keep quite some BTC without selling them, which we need for $reasons, and I don't know if we receive enough during the rest of the year (outside of the donation campaign) to cover our needs. I could do the maths if needed; it may very well be that this ("high-tech") option saves us quite some money down the road, and makes life simpler for a number of Tails people. I can elaborate (elsewhere) if needed :)

During the donation campaign we should ideally point everybody to Riseup's account in order to better track the money we received, no?

I think it doesn't matter much: the money received by both bitcoin addresses can be retrieved from blockchain explorers, so the difference between "everything in the same place" vs. "cleverly split into two places" is one addition.

#12 Updated by intrigeri 2 months ago

Ouch: https://bitcoin.org/en/alert/2017-10-09-segwit2x-safety. Now I think this doesn't change anything here: even if BTC donations sent to RiseupLab's Coinbase account are converted to whatever altcoin, we don't care much as the goal is to have RiseupLabs sell them as soon as possible. But we should first check what RiseupLabs' plans are given these news.

#14 Updated by u about 2 months ago

Sent email, waiting for reply.

#15 Updated by anonym 28 days ago

  • Target version changed from Tails_3.3 to Tails_3.5

Also available in: Atom PDF