Sure, everyone's risk tolerance (and willingness to go through the hassle) is different. I only wanted to explain the possibility, not trying to persuade anyone :)

Also, for some people, it might be too much of a hassle now, but convenient at the next time when they would move their coins anyway, e.g. for a key rotation (provided that the blake2b price has not completely collapsed by then).

Haha, I think posts specifically about dumping shitcoins should be allowed :)

Good point, I should have mentioned that as another good option. Might be a nice motivation for people to start coinjoining.

Why the name "eCash", when there are already two unrelated projects with that name (Chaumian eCash and the XEC chain)?

Thanks!

July 16.

After Albert's first sentence, it has to be July or August (since in May or June, there are days 18/19 that occur only once, in which case Bernard would know the date immediately).

Bernhard also infers from the same logic that it has to be July or August. Further, the day cannot be 14, since then Bernhard still wouldn't know in the second step (cannot decide between July 14 or August 14), but he claims to know.

That leaves July 16, August 15 or August 17. Albert, following up to here, then claims to know the date. If it were August, there would still be two choices and Albert wouldn't know. So it has to be July 16.

Disclaimer: I think I've seen a similar puzzle before, but I had to think about it again.

Same behavior here. Occasionally, a small payment still goes through, but most often it's the "no route" error.

Not really worried about my sats (in the worst case, I can still close the channel), but it's still annoying.

What is your usual dev setup for coding and debugging? Do you use any IDEs?

Let's call the guys A, B, C and D, with A to take first.

If N = 1, A loses immediately (he has to be rude)
If N = 2,3 or 4, he will take N-1 and B loses.
If N = 5,6 or 7, A will take 3, B will take N-4 and C loses.
If N = 8,9 or 10, A and B will each take 3, C will take N-7 and D loses.

If N = 11, A will lose whatever he does (after his turn, it's the same situation as for N = 8,9 or 10, with the players shifted by one).
If N = 12,13 or 14, A takes 1,2 and 3, respectively, so that 11 dumplings are left and B will lose. (If he takes too many, e.g. N=12 and he takes 2, it will again be the situation above with A in the losing seat.)
If N = 15,16 or 17, A will take 3 and B will act as above, so in the end C loses.
If N = 18,19 or 20, A and B take 3, C takes 1,2 or 3 respectively and D loses.

If N = 21, it's the same situation as for N = 11 again, A loses whatever he does.

And so on. In summary, the current business man:

• loses anyway if N = 1 mod 10
• should take 1 if N = 2 mod 10
• should take 2 if N = 3 mod 10
• should take 3 otherwise.

I'm still using ElectrumX. Works well for my purposes, I see no reason to switch.

Alright, sent you 1M sats :)

No need to send anything back, I don't really need those testnet coins anymore.

If you need more testnet coins to open channels, I can send you some.

Not much correlation here. I've become quite stoic about the bitcoin price.

Not sure yet if I will make it today, a bit busy this weekend. Maybe I'll manage to join part of the tournament. If not, have fun and I'll hopefully join the next one!

Thanks! Yes, I've been lurking from time to time so far, but finally decided to sign-up :)

Interested to join. I'm a reasonably strong chess player, but still well blow master level (this is my lichess profile).

Though I personally don't like correspondence games, mostly because it's too easy to cheat there (using an engine). Would be happy to play any real-time (e.g. blitz or rapid) time control.