Tails

#1 Updated by intrigeri 2017-11-07 14:20:04

• related to Feature #13656: Upgrade bitcoind on bitcoin.lizard added

#2 Updated by intrigeri 2017-11-07 14:41:08

• Description updated
• Status changed from Confirmed to In Progress
• Assignee deleted (intrigeri)
• % Done changed from 0 to 10
• QA Check set to Info Needed

So, my current understanding is:

• receiving whatever kind of BTC we get during the fork is not a problem on our side: in any case it seems we’ll need to split our coins between the 2 cryptocurrencies once the dust has settled, and whichever blockchain donors use will record the transactions we’ve received;
• sending BTC may be a problem for donors: depending on their wallet/client, they might not be spending the currency they expect to; I think most Bitcoin users should be well aware of the upcoming hard fork as the Bitcoin galaxy has been buzzing about it for weeks, so I guess most of them will do as recommended, i.e. avoid doing any transaction shortly after the fork.

So the question is: do we want to be extra nice to clueless Bitcoin users by not advertising Bitcoin donations temporarily? We might lose some donations if we do that (I bet those people won’t come back a week later to donate); but if we don’t do it some people might be angry at us once they realize what they did.

I don’t know what’s best. I’m tempted to do nothing at all, or to “just” add a warning message on the donate page during the fork, pointing to some relevant doc. u, what do you think?

#3 Updated by Anonymous 2017-11-07 22:29:15

• Assignee set to intrigeri

I like the idea to just add a small warning message during the fork. Can you propose a text & link or should I research this?

#4 Updated by intrigeri 2017-11-08 10:06:45

• QA Check changed from Info Needed to Dev Needed

> I like the idea to just add a small warning message during the fork. Can you propose a text & link or should I research this?

I’ll try to come up with something in the next few days.

#6 Updated by intrigeri 2017-11-08 15:49:32

• Subject changed from Check what to do wrt. SegWit2x hard fork vs. our fundraising campaign to Warn about the SegWit2x hard fork on our donate page
• Type of work changed from Research to Website

#7 Updated by intrigeri 2017-11-08 15:51:22

• Feature Branch set to web/14928-warn-about-SegWit2x

#8 Updated by intrigeri 2017-11-08 16:20:08

• Assignee deleted (intrigeri)
• % Done changed from 10 to 50
• QA Check changed from Dev Needed to Ready for QA

Please review and merge before, but as close as possible to, the fork (see the link to the countdown in the description). If that’s too stressful just merge at any time before the fork: I’ve used phrasing that can work now already.

Once this is done don’t close this ticket: we’ll need to adjust the phrasing after the fork (to remove “on November 16 or later”). And then we’ll need a ticket for removing this note once it’s not useful anymore (or just repurpose this one, your call).

#9 Updated by Anonymous 2017-11-09 11:04:34

• QA Check changed from Ready for QA to Pass

I’ll merge this on november 15th.

#10 Updated by Anonymous 2017-11-09 11:05:03

• Priority changed from High to Urgent

Increasing priority so that this item will poop out on my todo list.

#11 Updated by intrigeri 2017-11-09 13:38:10

• Status changed from In Progress to Rejected
• Assignee deleted ()
• % Done changed from 50 to 100

The SegWit2x hard fork was called off. Not sure about Brexit yet, I’ll check.