It also looks like the backdoor may have a remote code execution vulnerability: https://twitter.com/petertoddbtc/status/857340167400587264
2,015 karma · joined September 27, 2009
It can be found on each of these URLs:
https://keys.openpgp.org/vks/v1/by-fingerprint/40455A814AA7D22B2636A03784EA82541F47C4A7
* https://keyserver.ubuntu.com/pks/lookup?search=40455A814AA7D22B2636A03784EA82541F47C4A7&fingerprint=on&op=index
https://github.com/haakonn.gpg (on my GitHub account)
https://www.reddit.com/r/KeybaseProofs/comments/1d68a9w/my_keybase_proof_reddithaakon_keybasehaakon/ (on my Reddit account)
It also looks like the backdoor may have a remote code execution vulnerability: https://twitter.com/petertoddbtc/status/857340167400587264
The segwit softfork may fix some things that make side chains more feasible, but that undersells it severely. It mainly solves a bug in bitcoin that prevents a good implementation of Lightning Network (which is not a side chain), and it also upgrades on-chain transaction capacity by doubling it, while solving another bug in Bitcoin (quadratic scaling of sigops) which make such a capacity increase safer.
More information here: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
> "The 21st century will not be dominated by America or China, Brazil or India, but by the city," writes Parag Khanna (1). The author of several books on global strategy, Khanna argues that (some) cities, as islands of good governance in an increasingly unstable world, will become the cornerstone of a new world order.
> That new world order won't be a "global village" of nation states, for globalisation is corroding national sovereignty. Rather, it will be a loose network of semi-independent city states, perhaps resembling the Hanseatic League and other medieval trading alliances.
* The malleability attack: a transaction relayer is able to change the hash of the transactions, thus confusing senders or receivers who rely on this hash to check if the transaction has confirmed. This creates a nuisance, but all money arrive where they are supposed to. This attack does not affect memory usage on nodes, and it's an old and well-known issue.
* A transaction spam attack (misleadingly called a "stress test") where a shady group called coinwallet.eu creates a large amount of big transactions. These mostly have appopriate fees so that regular users who want their transactions to confirm in a timely manner has to out-bid the spammer. All the unconfirmed transactions are stored in the memory of nodes, so this severely affects memory usage (currently about 1 GB on some nodes).
But if blocks are not consistently full and there's no significant backlog, there is room for cheap transactions. This has been the case up to now. If the block size limit were to be increased, the assumption goes, there would again be room for cheap transactions - until they fill up again.
In practice, we don't know if miners would actually include cheap transactions if it makes their blocks significantly bigger. Their incentives seem to be against it, since bigger blocks have higher orphan rates.
> The torrent contains a virus, it's best to let the authorities examine the evidence and stop seeding and spreading false info.
Yes, the hackers fabricated 400GB of lies and please don't look at them.
Gradberry is apologising on twitter now with the same bs: https://twitter.com/gradberry/with_replies ("we sent one email since your profile matched out job requirements, sorry about that!", "sorry man :( We did genuinely like your repo commits though.")
I hope this blows up in their faces. Spam is spam.
The current plan seems to be to start increasing the block size limit by 50% per year in order to allow higher transaction volume. Block size limit has always been a contentious issue.