This game awesome, surprisingly fun for how simple it is.
I mean no disrespect to Andreas, but this video is misleading, and I've had more than one conversation with users online that cite this video as proof that 'we could just fork off a 51% attacking miner!', which is false.
Andreas is right about the economic incentives, but from 1:20 onwards, what he talks about isn't correct wrt a majority attacker. Its unfortunate this video is apparently so popular.
The updated iOS shortcuts app lets you run shell scripts over SSH.
One very simple script later and I can copy a LN invoice on my phone (or laptop!), and then tap an icon on my phone's home screen (or lock screen!) to run the script and pay the invoice. A prompt tells me the invoice amount, and then asks if I want to confirm payment.
Once set up, this is an amazingly simple and easy UX! Even easier than unlocking your phone and opening a lightning wallet app, really. #bitcoin
*puts on tinfoil hat*
Maybe BCH miners invented this whole 'dev-tax' thing with no real plan to follow through on it. Once there has been enough outrage, the pro dev-tax side concedes, and then moving forward BCH users can claim 'decentralization!', because the miners failed to push out a contentious update.
I like how much it counters the usual chainalysis heuristics, but it is kind of expensive. I suppose the overpaid difference could be paid back over LN submarine swap though? Hm
I've seen apparent demonstrations of replacing the sticker on the back of a Casascius coin, but have there ever been reports of someone actually getting ripped off this way?
Seems even more relevant now, PSBTs would make this a lot simpler to implement.
1 #bitcoin block / 10 mins
1,440 mins / day
365 days / year
= 52,560 blocks / year
But by my math, the network is actually running ~1,680 blocks 'ahead of schedule' in 2019 (as expected, when hashpower is increasing over time). Thats about 11.667 days worth of blocks, which is ~3.2% more than expected.
Happy new years!
Newbie #bash question:
I'm trying to run a command located in /usr/local/bin/, via a shell script over ssh. But bash keeps giving a 'command not found' error.
If I modify the script to specify the command's full file path, it works just fine.
Why is this?
$PATH includes /usr/local/bin/. Why can't bash find it?
From birdsite: https://twitter.com/bittlecat/status/1207621591820951552
A #Bitcoin user attempted to withdraw BTC from BinanceSGD, but was blocked due to that user's participation in Wasabi coinjoins after a previous withdrawal.
If you think this breaks or somehow invalidates coinjoin, then I think you didn't understand the stakes to begin with: did we really expect KYC'd businesses to just ignore this? Of course they're going to fight back! This is why there are ideas like P2EP out there, the battle has only just begun.
One of the most potent points in this: its becoming difficult to reconcile the risks of these data collection systems against the benefits to the actual users.
So whats next? A culture of being okay with no assumed location-data privacy? Or a radical shift to something new?
You are the product.
Some related links, from a couple quick searches:
I've always thought it would be nice to have some hexadecimal dice to roll your own private keys, is there a reason I haven't ever seen this otherwise?
Encoding to WIF would make it less user-friendly of an option, but all else aside it seems like a verifiable way to supply user-generated entropy. Easier than flipping a coin a couple hundred times, at least..
Acting in unexpected ways can be an important technique for defeating chain analysis, so I think the naive assumption is that a fake coinjoin will be helpful.
There may be legitimate use-cases for a fake coinjoin, but considering the input aggregation, you'd have to be very careful to not do more damage than good. Post-mix UTXO management would become even more important than normal!
techno sapien demands techno sovereignty
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!