News for hackers. Stuff that matters.
Re:Why aren’t distributed systems engineers working on block... by aphextron on Tuesday August 01, 2017 @11:57AM (#14902095)
>The blockchain community is immature and historically unwelcoming.

>It feels like a get rich quick scheme - https://twitter.com/naval/status/878018839044161536

This is what it comes down to IMO. Anything cryptocurrency related is just surrounded by a cloud of shady characters and scammers, even though the tech is legit. You just can't trust anyone, nor their intentions. Living your life and working in a constant state of paranoia like that is awful.

Re:Why aren’t distributed systems engineers working on block... by KirinDave on Tuesday August 01, 2017 @01:43PM (#14903319)
It's also surrounded by a ton of cargo cultism, poorly considered engineering, people who don't understand the math but claim to be gurus, and strange parasitic political views.

It's a frustrating community to engage with because it has redefined a lot of longstanding terms to (in my opinion) make itself look better and smarter. It also is a constant roiling tempest of non-self-reliant-but-fantastically-dedicated-to-anarcho-capitalists-type folks, which can be terribly tedious to deal with.

For example, ask a btc engineer if they have byzantine fault tolerance. Then ask anyone else. Ask them if they have eventual consistency. Then ask anyone else.

Re:Why aren’t distributed systems engineers working on block... by stcredzero on Tuesday August 01, 2017 @03:13PM (#14904290)
It's also surrounded by a ton of cargo cultism, poorly considered engineering, people who don't understand the math but claim to be gurus, and strange parasitic political views.

So it's just your typical programming sub-field? (Alan Kay would say: "Field.")

Re:Why aren’t distributed systems engineers working on block... by KirinDave on Tuesday August 01, 2017 @03:15PM (#14904309)
Pessimistically yes, but in my opinion its problems are magnified.

In part because bitcoin is a technology that so many people ascribe political superpowers to. This brings in a lot of people that normally don't push deeply into a high-complexity tech field.

Re:Why aren’t distributed systems engineers working on block... by stcredzero on Tuesday August 01, 2017 @10:09PM (#14907340)
Some would say that the "wisdom of the crowd" and startups are things that so many people ascribed special superpowers to, it brought in a lot of people that normally wouldn't push deeply into a high-complexity tech field.
Re:Why aren’t distributed systems engineers working on block... by KirinDave on Tuesday August 01, 2017 @10:36PM (#14907493)
That's cool, but how is it relevant?
Re:Why aren’t distributed systems engineers working on block... by stcredzero on Wednesday August 02, 2017 @11:07AM (#14911125)
It's relevant, in that the HN crowd should be reminded to be self skeptical about their own groupthink. (I know I'm preaching to the choir here.)
Re:Why aren’t distributed systems engineers working on block... by matt_wulfeck on Tuesday August 01, 2017 @12:37PM (#14902577)
Even if the tech is "legit" it's encredibly inefficient. We're spewing off tons of CO2 just to verify the block chain, but we have plenty of technologies that can do the same with a minuscule amount of energy.

The problem is that they want a system that's trustless and that's simply not what most engineers care about. We want a system that's fast and efficient.

Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @12:39PM (#14902610)
There are solutions to that though, like Proof of Stake. If distributed systems really cared about that, then that's exactly why they ought to be working on blockchains, to make them more efficient.
Re:Why aren’t distributed systems engineers working on block... by CobrastanJorji on Tuesday August 01, 2017 @12:46PM (#14902699)
So, your argument is: "you say our thing sucks at X, but if you really think so, why aren't you trying to fix it?" Filling in the variables differently, we could construct an argument like "If civil engineers really cared about structural stability, then that's exactly why they ought to be working on my bridge made out of playing cards."

It's not their job to fix someone else's bad idea.

Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @01:06PM (#14902905)
Cryptocurrencies aren't going away. Which means that if your primary motivation to not work on cryptocurrency is that it wastes energy, then there's a whole lot of room for you to be making it better, and that is a stupid motivation. I'm not saying that they are obligated to work on it because it wastes energy. But the comment I was responding to implied that distributed systems engineers didn't want to work on blockchains because they are wasteful - which is clearly illogical. That'd be like Elon Musk not working on electric cars because they're inefficient. Or Solar cells. Etc, etc..
Re:Why aren’t distributed systems engineers working on block... by jethro_tell on Tuesday August 01, 2017 @02:23PM (#14903747)
No that's not illogical, Why would I work to bend something like block chain, that was designed to be inefficent, to my will when I can just start from scratch using projects that were designed to be efficient first? That's very logical, the kind of decision that an engineer that's getting paid the make the best distributed system for the least money would make.
Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @02:30PM (#14903822)
It's not designed to be inefficient. It's designed to solve the distributed consensus problem in an adversarial environment. There are other now proposed mechanisms of doing that (e.g. PoS) that are quite efficient. Working on those would be extremely beneficial to the cause of environmental efficiency.
Re:Why aren’t distributed systems engineers working on block... by jethro_tell on Tuesday August 01, 2017 @03:02PM (#14904177)
Evironmental efficiently solving a problem I don't have is still inefficient. I still can't think of a mojor user for proof of work in a destributed system. I have trouble thinking of a distributed system that someone would pay for to not be centrally trusted, usually by the benefactor of employment? We always hear what a great solution blockchain is. Even if that's true, I never hear the actual problem it solves. Sure, say distributed ledger, and proof of work but those are solutions of sorts.

Name a problem that would best be solved with blockchain.

Re:Why aren’t distributed systems engineers working on block... by ExactoKnight on Tuesday August 01, 2017 @07:49PM (#14906589)
The block chain offers the following unique benefits for asset transfer:

- Assets move directly between entities — transfer and settlement are one-and-the-same — eliminating counterparty risk (https://en.wikipedia.org/wiki/Credit_risk#Counterparty_risk)

- Assets move instantly, and settlement time is ~10 minutes (settlement can also be instant if the parties trust the other won’t “double spend”)

- The transfer mechanism is public infrastructure and is always improving — everyone has a shared incentive to make it better, similar to Internet protocols like email and http

- Assets and end-user data are privately controlled, and strong security for assets can be achieved by using multiple signing keys across several parties

- Policy rules about the movement of assets can be enforced programmatically — whether those are “terms and conditions” or regulatory requirements

- Assets are fungible and play nice together — e.g., you can use reward points to buy mobile minutes

- A single transaction can include multiple entities and assets, on both sides of the transaction — e.g., you could execute a merger of two companies in a single transaction, with the inputs to the transaction being all stockholders across all share classes for both companies, and the outputs being all the newco shares going to all the new stockholders (again, no escrow service needed)

- Every transaction is added to an immutable record which, while anonymous, can be used to construct a perfect audit trail of an asset’s movement when combined with the private data held by the entities using the system — this defends against fraud, and also gives issuers transparency into asset movements

- It’s easy to integrate new parties

- Like the Internet itself, it’s a global system

Worth a read: https://blog.chain.com/wall-street-meet-block-chain-b2747909...

Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @03:42PM (#14904572)
> Name a problem that would best be solved with blockchain.

Money. E.g. Bitcoin.

Re:Why aren’t distributed systems engineers working on block... by dogecoinbase on Tuesday August 01, 2017 @04:33PM (#14905037)
Bitcoin as money has all the worst properties of both credit cards (traceable, non-anonymous) and cash (irreversible, theft-prone).
Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @05:12PM (#14905390)
It isn't intrinsically theft prone, the UI around using it is just not up to snuff yet. Credit cards, on the other hand, are intrinsically theft prone. They are a pull architecture. Every time you use your credit card, the store takes money from you. This is patently absurd, and the only reasonable definition of 'theft prone'. Bitcoin is a push architecture. You can never take my bitcoin, I can only send you bitcoin. Further, irreversibility is definitely what you want in the underlying protocol. It's fine if people want to implement escrowing and chargebacks via intermediaries on top of Bitcoin, and I would encourage that. But at a fundamental level, a payment system should be irreversible, immutable, uncensorable and push-based. Which is exactly what Bitcoin is.
Re:Why aren’t distributed systems engineers working on block... by empthought on Wednesday August 02, 2017 @01:26AM (#14908145)
> Every time you use your credit card, the store takes money from you.

No, precisely no credit cards work that way. That's why they're called credit cards.

Re:Why aren’t distributed systems engineers working on block... by darawk on Wednesday August 02, 2017 @03:59AM (#14908736)
The money is taken from the credit card company, then. The architecture is still pull. You're splitting hairs.
Re:Why aren’t distributed systems engineers working on block... by empthought on Wednesday August 02, 2017 @08:03PM (#14915837)
That's not splitting hairs; that's literally the point of credit cards. It is entirely "push" from my perspective, modulo the minimum monthly payment and tolerance for paying interest and bad credit.

If I buy something with a credit card for $2k and have $2k in my bank account, the $2k is still there until I pay the credit card company. It could take years or be paid off immediately.

It's not a "pull" at all.

Re:Why aren’t distributed systems engineers working on block... by darawk on Wednesday August 02, 2017 @09:06PM (#14916147)
It is a pull. You bear the costs of fraud whether you notice them or not. The fact that the credit card company hides those costs from you doesn't change the fact that their architecture is broken, and that you are still paying for it by virtue of the fees they charge merchants, which create higher sticker prices for you. Costs like that don't simply disappear into the ether - you, the consumer, pays them.
Re:Why aren’t distributed systems engineers working on block... by vageli on Thursday August 03, 2017 @01:35PM (#14921732)
Every consumer who doesn't use credit cards also bears the fees since it is rare to find a merchant that offers a "cash discount".
Re:Why aren’t distributed systems engineers working on block... by darawk on Thursday August 03, 2017 @04:12PM (#14923357)
Ya, also true, and good point.
Re:Why aren’t distributed systems engineers working on block... by empthought on Thursday August 03, 2017 @06:23AM (#14918349)
Precisely none of that is "Every time you use your credit card, the store takes money from you."
Re:Why aren’t distributed systems engineers working on block... by darawk on Thursday August 03, 2017 @12:46PM (#14921170)
It's a pull architecture. Pull architecture is wrong, push architecture is right.
Re:Why aren’t distributed systems engineers working on block... by KingMob on Tuesday August 01, 2017 @04:23PM (#14904943)
Any time you require 1) a distributed database 2) in the face of adversarial participants, which truthfully, is less common than the blockchain obsessives would think.

A centralized organization (.com or .gov) that can achieve consensus amongst participants can do just fine with Postgres and a REST API.

Adversarial participants are common, but typically that's solved with a third-party overseer that administers the system. Finding use cases that demand decentralization are harder.

Bitcoin was created to remove central banks/govts from the money creation process, but in most cases, if you don't trust the central authority, you just don't participate. With cash, you can't easily get around dealing with the govt.

Re:Why aren’t distributed systems engineers working on block... by njarboe on Wednesday August 02, 2017 @01:26AM (#14908146)
When cash was gold and/or silver the central authority might do some minting of coin but you did not need to trust them with a ledger or not to print huge amounts of paper currency. Gold and silver were currency for thousands of years. Soon all the people who lived under that system will be dead. It will be interesting what the system of global fiat will bring in the future.
Re:Why aren’t distributed systems engineers working on block... by davidgerard on Tuesday August 01, 2017 @05:01PM (#14905263)
> There are other now proposed mechanisms of doing that (e.g. PoS) that are quite efficient.

Well, no they aren't, because they're proposals.

Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @05:09PM (#14905352)
No they're not. They're implemented in many altcoins. And to say that 'proposals' are not efficient because they haven't been implemented is both semantically wrong, and an incredibly stupid point even if it weren't.
Re:Why aren’t distributed systems engineers working on block... by dboreham on Tuesday August 01, 2017 @01:13PM (#14902985)
But the entire point is that it wastes energy. That's why it works. It isn't like a car that can be made more efficient and therefore better. The central premise is that we're going to waste energy to do something that can be done in other ways without wasting energy.
Re:Why aren’t distributed systems engineers working on block... by nullstyle on Tuesday August 01, 2017 @01:42PM (#14903305)
No, wasting energy is not why blockchain works. proof of work is just one way a blockchain can work. There are alternatives:

https://www.stellar.org/developers/guides/concepts/scp.html

disclosure: I work at stellar

Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @02:53PM (#14904064)
The entire point is that it wastes something. Not specifically energy. The idea is that there is a sunk, unrecoverable cost associated with mining. That cost may be able to take other forms, though. In the case of proof-of-stake, that cost is the time-value of money.
Re:Why aren’t distributed systems engineers working on block... by KirinDave on Tuesday August 01, 2017 @02:02PM (#14903517)
In part because this is trodden ground for distributed systems engineers and we know that, on balance, the correct solutions all involve massive centralization.

You don't want that. So we're at a bit of an impasse.

Distributed systems these days mostly argue that you do your trusting up front, outside of the protocol itself. You then validate that the actors share the secrets you all agreed upon, and then optimize the agreement process. Only the most robust systems actually consider "active" dissent; most distributed systems engineers consider this a special case that is most often focused on the idea of "incorrectness" as opposed to "maliciousness."

You can see elements of these assumptions in more modern data structures used for eventual consistency, like CRDTs. CRDTs are amazing and fast and often abstract-able to a trivial programming model. Anyone can use them, but they have to be monotonic, so we can't ever forget bad input, just try and cancel it out.

Re:Why aren’t distributed systems engineers working on block... by Magnap on Wednesday August 02, 2017 @11:09AM (#14911142)
In some cases you can forget bad input, though, can't you? It's a rather wasteful example, but if (like you say, having established trust beforehand) every element of a grow-only set is a signed message, you can reject any messages that don't validate against their signature when merging. On one hand, this breaks idempotence. On the other, if we regard that set as a subset of the set of validly signed messages, it could not have been there in the first place, so to speak, so I wouldn't immediately think it breaks any guarantees. As far as I can tell, any properly functioning machine will only ever see correct state this way, unless it receives some state and doesn't merge it with anything, for example when initially starting to participate. However, that's easily fixed by always having some state, for example by starting with the empty set in this case.
Re:Why aren’t distributed systems engineers working on block... by KirinDave on Wednesday August 02, 2017 @02:12PM (#14913153)
> you can reject any messages that don't validate against their signature when merging.

That's not really what I meant by "bad". I meant bad as in intent, not structural and immediately verifiable message integrity.

If all entities in the coalescing set can independently verify that a message does not meet its signature requirements, it will be rejected and idempotence is maintained.

If ONE member is somehow deceived about key validity it'll propagate the message into every other member's state, eventually.

Re:Why aren’t distributed systems engineers working on block... by Taek on Tuesday August 01, 2017 @12:45PM (#14902687)
Most of the bitcoin researchers have thoroughly convinced themselves that Proof of Stake is not achievable with acceptable levels of security, and for good reason. The reason you don't see more active research on Proof-of-Stake is that it is thought to only lead to dead ends.
Re:Why aren’t distributed systems engineers working on block... by fredcy on Tuesday August 01, 2017 @04:30PM (#14905001)
Tezos will use Proof of Stake. They have a development version working now and there is good reason to expect a production version within a year.
Re:Why aren’t distributed systems engineers working on block... by billmalarky on Tuesday August 01, 2017 @12:49PM (#14902725)
The Ethereum team is serious about proof of stake.
Re:Why aren’t distributed systems engineers working on block... by indigochill on Tuesday August 01, 2017 @01:17PM (#14903027)
Ethereum has not shown a particularly strong track record when it comes to security, so I think the comment stands until they address that or get replaced by the next hotness.
Re:Why aren’t distributed systems engineers working on block... by tekromancr on Tuesday August 01, 2017 @02:02PM (#14903514)
I think that statement is a little disingenuous. There haven't been any attacks that target Etherium proper, only bugs in smart contracts riding on top of Eth.
Re:Why aren’t distributed systems engineers working on block... by davidgerard on Tuesday August 01, 2017 @05:05PM (#14905308)
> I think that statement is a little disingenuous. There haven't been any attacks that target Etherium proper, only bugs in smart contracts riding on top of Eth.

This is a bit No True Scotsman. It's like "secured by math!" about Bitcoin - the ecosystem is rife with fraud and error.

So too with Ethereum. Given that smart contract functionality is literally Ethereum's unique selling point, you can't claim that is somehow not something that can be discussed as a problem with Ethereum. They broke the immutability guarantee for one bad smart contract, after all.

You really can't say "Ethereum is completely secure!! Except for everything that people actually use it for" without being more than a little disingenuous yourself.

Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @06:59PM (#14906275)
It is, thus far, completely secure. The fact that SQL injection bugs exist does not negate the security of HTTP. The fact that stack overflow bugs exist does not make x86 insecure. The primitives you are provided are secure - how you use them may not be.

Now you may legitimately argue that Ethereum is poorly designed to encourage secure contract authorship. And I would agree with you in many respects. But that is a distinct concern from the security of Ethereum itself. Conflating the two is at best confusing and at worst maliciously spurious.

Re:Why aren’t distributed systems engineers working on block... by indigochill on Tuesday August 01, 2017 @04:09PM (#14904810)
I don't mean that I have concerns about Ethereum itself, just the fact that it's currently too easy to write insecure contracts. And there has been some low-hanging fruit in remedying that, such as the whole "functions are public unless otherwise specified" thing.
Re:Why aren’t distributed systems engineers working on block... by jethro_tell on Tuesday August 01, 2017 @02:25PM (#14903763)
Only a 31MM dollar bug, nothing to see here, we're secure.

WAT?

Re:Why aren’t distributed systems engineers working on block... by tekromancr on Tuesday August 01, 2017 @02:39PM (#14903916)
Again, the bug was in the application layer, not the protocol layer. That's like saying that HTTPS is broken because you can do SQLi against someone's poorly coded website.
Re:Why aren’t distributed systems engineers working on block... by patmcguire on Tuesday August 01, 2017 @03:01PM (#14904165)
I believe it's not core Ethereum that has issues, it's buggy smart contracts. They don't make it particularly difficult to write insecure contracts, though.
Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @02:32PM (#14903839)
Ethereum actually has a better security track record than Bitcoin does [1]. It's the contracts on top of Ethereum that are the problem. Calling those incidents Ethereum security problems is like calling a Windows 0day an Intel security problem.

1. https://en.bitcoin.it/wiki/Value_overflow_incident

Re:Why aren’t distributed systems engineers working on block... by crummel on Wednesday August 02, 2017 @05:23PM (#14914790)
If Ethereum is forking because of contract problems, then an Ethereum contract problem is an Ethereum problem.
Re:Why aren’t distributed systems engineers working on block... by ntrepid8 on Tuesday August 01, 2017 @12:46PM (#14902688)
Doesn't blockchain verification depend on a certain amount of inefficiency? Isn't that what makes forgery difficult?
Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @01:09PM (#14902941)
That's a bit of a mistake. It doesn't rely on inefficiency it relies on economic costs. At the moment, hashing is a form of economic sunk cost. If you invest in hashpower, you can't split it without reducing your probability of success. It's an unforgable economic burden. Proof of stake architectures attempt to do the same thing with the currency of the network itself. There are lots of arguments about whether or not this is truly secure - but anyone on here telling you they know it's not is pretty much an idiot. There are tons of proof of stake coins operating successfully right now. There are no known attacks on these coins that allow you to do anything untoward (if there were, they'd be exploited on one of the many existing PoS coins).
Re:Why aren’t distributed systems engineers working on block... by akvadrako on Tuesday August 01, 2017 @12:54PM (#14902785)
That correct and why PoS probably will not be secure anytime soon.
Re:Why aren’t distributed systems engineers working on block... by redy on Tuesday August 01, 2017 @01:51PM (#14903401)
No serious blockchain relies on proof-of-work. Bitcoin (being forked now) doesn't and ethereum (already forked twice) definitely doesn't.

Blockchains are a social construct and what ultimately protects them are the participants. Exactly like actual currencies they are subject to market forces; people either believe in and want the currency or they don't. It's this confidence that gives the currency strength.

More simply:

"On medium to long time scales, humans are quite good at consensus. Even if an adversary had access to unlimited hashing power, and came out with a 51% attack of any major blockchain that reverted even the last month of history, convincing the community that this chain is legitimate is much harder than just outrunning the main chain’s hashpower. They would need to subvert block explorers, every trusted member in the community, the New York Times, archive.org, and many other sources on the internet; all in all, convincing the world that the new attack chain is the one that came first in the information technology-dense 21st century is about as hard as convincing the world that the US moon landings never happened. These social considerations are what ultimately protect any blockchain in the long term, regardless of whether or not the blockchain’s community admits it (note that Bitcoin Core does admit this primacy of the social layer)." [1]

[1] https://medium.com/@VitalikButerin/a-proof-of-stake-design-p...

The subtlety here is making the distinction between confidence and resistance to attack. They're not the same thing at all. And what's interesting here is that, going off the model of real currencies, one could assume market forces will prevail here. Developed nations let their currencies float precisely because on the whole they're confident that the market will ultimately punish any malicious attacker who attempts to destroy the currency by selling large amounts of it.

Re:Why aren’t distributed systems engineers working on block... by EnFinlay on Tuesday August 01, 2017 @12:44PM (#14902672)
Just because people care about efficiency doesn't mean they ought to work on something that lacks it.
Re:Why aren’t distributed systems engineers working on block... by darawk on Tuesday August 01, 2017 @02:55PM (#14904088)
I think that's exactly what it means. If you want to help the environment right now, what field should you be in? Energy generation, storage, or consumption.
Re:Why aren’t distributed systems engineers working on block... by wmf on Tuesday August 01, 2017 @02:42PM (#14903947)
There's a lot of work on non-mining private blockchains that you're ignoring.
Re:Why aren’t distributed systems engineers working on block... by ghostbrainalpha on Tuesday August 01, 2017 @01:19PM (#14903049)
Forgive me if I'm wrong, but isn't this why LiteCoin was created by a Google Engineer?

Does it solve the problem? Or did it just make a step in the right direction?

Re:Why aren’t distributed systems engineers working on block... by bb88 on Tuesday August 01, 2017 @01:36PM (#14903245)
LiteCoin's proof of work is memory hard so it's harder to create an asic.

A hard proof of work algorithm is required for decentralized coin chains to work. Otherwise it would be easy to create a denial of service attack by rogue agents filling up your blockchain with worthless blocks.

Re:Why aren’t distributed systems engineers working on block... by KirinDave on Tuesday August 01, 2017 @01:47PM (#14903363)
It's worth noting that the qualification should be "easier." But the POW is only one side of the DoS problem bitcoin's model can be forced to experience.

By carefully attacking the network links between miners, someone can significantly extend the amount of time that an attack can take place in. These attacks are expensive, but orthogonal to any PoW algorithm.

Then the problem transforms into: "can I trigger enough small pluralities of miners to split and form opposing but equally long viewpoints?" The only resolution to such a scenairo is to discard most of the divergent blockchains arbitrarily by human consensus.

Re:Why aren’t distributed systems engineers working on block... by tinco on Tuesday August 01, 2017 @01:33PM (#14903208)
No Litecoin is not significantly different from Bitcoin in that regard.
Re:Why aren’t distributed systems engineers working on block... by ty_a on Tuesday August 01, 2017 @01:53PM (#14903414)
Most mining is hydro powered.
Re:Why aren’t distributed systems engineers working on block... by davidgerard on Tuesday August 01, 2017 @05:09PM (#14905351)
Actually, Bitmain's building with 75% of mining capacity appears to run on wind and solar.

https://bitcoinmagazine.com/articles/bitmain-reveals-plans-f...

(was planned then, I believe it's in service now)

Re:Why aren’t distributed systems engineers working on block... by KirinDave on Tuesday August 01, 2017 @01:56PM (#14903438)
Please cite your sources.

Beyond this: https://www.coindesk.com/carbon-footprint-bitcoin/

Which is sort of unvalidated and points to one or two actors in the space suggesting that they want to move to non-fossil fuels and one that miiiiight be.

Re:Why aren’t distributed systems engineers working on block... by Obi_Juan_Kenobi on Tuesday August 01, 2017 @03:38PM (#14904543)
Not the parent commentor, but this is certainly true to some degree. To what extent is very hard to say, but China has built several large hydroelectric projects in remote areas where electricity is very inexpensive. Many miners have taken advantage of this.

http://technode.com/2017/02/27/bitcoin-mining-sichuan-cheap-... https://www.washingtonpost.com/world/asia_pacific/in-chinas-...

Of course, there is also cheap coal power in China, so the environmental impact may be very significant.

Going forward, I anticipate the rise of solar mining in some favorable areas. Possibly geothermal as well. Since Bitcoin mining can be done anywhere with decent internet access, it seems natural that it should gravitate toward renewables over time. Fossil fuels continue to get more expensive, while renewables get cheaper. Of course, building e.g. solar panels isn't without environmental impact, either.

Re:Why aren’t distributed systems engineers working on block... by Taek on Tuesday August 01, 2017 @01:04PM (#14902885)
> The blockchain community is immature and historically unwelcoming.

I can't disagree too much about the immaturity, but you don't see too much more of that in the deeper technical circles than you might see on the Linux mailing list. Room for improvement? Plenty. But it's also not grossly out of line as long as you are in the right places.

The 'unwelcoming' bit though is more justified. Blockchain design is like cryptography - security is very important, and one tiny mistake means that your design is completely unviable. And if that tiny mistake occurred early in your design process, it may be too deep to be easily routed around.

Designing secure blockchains is very hard. As a result, the first year or so you try to improve on blockchain systems you usually end up with a bunch of broken stuff that nobody appreciates at all. The same is true if you are trying to make a better hashing algorithm, or doing quantum resistant cryptography. Except with blockchains people haven't learned to expect it to be this difficult to innovate yet, so it feels a lot more hostile.

That will fix with time. As more things blow up in production, people are realizing more and more that blockchains are tricky, and that good designs take a lot of expertise, a lot of collaboration, and are very rare. That will make it seem less unwelcoming when your intro to blockchains is 'well, this thing you are proposing doesn't work for at least 10 reasons, and here they are...'

Re:Why aren’t distributed systems engineers working on block... by random3 on Tuesday August 01, 2017 @01:05PM (#14902892)
Anything that's related to profits and democratized will attract all kinds of characters. Democratization lowers the barrier and profits provide the incentive. The choice to corner cryptocurrencies and choose to see the shady characters in this combination is an artificial one based on what you can and choose to "see". The same shady characters are in finance, fund raising, and perhaps around your desk. They may be less obvious or you may be more tolerant towards the corporate backstabber, but they're still there.
Re:Why aren’t distributed systems engineers working on block... by nihonde on Tuesday August 01, 2017 @12:28PM (#14902458)
I guess it's not surprising that untrustworthy people would flock to technologies that eliminate the need for trust.
Re:Why aren’t distributed systems engineers working on block... by rpod on Tuesday August 01, 2017 @12:34PM (#14902537)
It's not necessarily the people who can benefit from a trustless network that cloud the ecosystem, it's shady people who want in on the hype solely to make money and apply blockchain to every conceivable use case just for the sake of applying blockchain. It's the kind of people who are an expert on fintech, blockchain, AI/machine learning and IoT all at the same time and seem to use the terms interchangeably.
Re:Why aren’t distributed systems engineers working on block... by duxup on Tuesday August 01, 2017 @12:48PM (#14902722)
Anonymous and irreversible transactions help too.
Re:Why aren’t distributed systems engineers working on block... by shepardrtc on Tuesday August 01, 2017 @12:44PM (#14902664)
That's not true for all companies. Take Ripple or Coinbase, for example. Both have worked from the beginning to be legit. Ripple's various technologies (including their currency) are being adopted by banks across the world. And Coinbase has worked with the Feds from the beginning to make sure they were complying with regulations. Granted there are a lot of bad actors in crypto, but there are good ones, too.
Re:Why aren’t distributed systems engineers working on block... by edge17 on Tuesday August 01, 2017 @02:19PM (#14903705)
I've spent a decent amount of time understanding blockchain at this point. Am I wrong in saying that it's really just a data structure for solving a problem (like a tree or array), but a lot of the hype seems to be people trying to find commercial applications to use the specific data structure? I mean, no one says 'lets go find a good use for an array,' you sort of pick the array after you have an idea
Re:Why aren’t distributed systems engineers working on block... by jtmarmon on Tuesday August 01, 2017 @02:37PM (#14903889)
It's an approach to solving a problem that allows problems to be solved in totally new ways. I think it's understandable to be on a search for opportunities to apply it.

The problem it seems to me is that, although the idea of trustless systems seem really cool and applicable to a lot of domains, it turns out that there are actually way fewer useful applications than people originally thought. But no one is letting go, and a lot of people are wrongly convincing themselves and others that most systems are better off trustless.

Re:Why aren’t distributed systems engineers working on block... by tylersmith on Tuesday August 01, 2017 @03:41PM (#14904566)
Yes the blockchain is just a data structure. A fancy tree. The more interesting part of cryptocurrencies are the dynamic membership multiparty signature schemes they implement, but those don't make for as nice of soundbites.
Re:Why aren’t distributed systems engineers working on block... by fokinsean on Tuesday August 01, 2017 @01:47PM (#14903360)
> You just can't trust anyone

Isn't that one of the reasons blockchain came to existence?

I know you aren't using that in the same context, it just sounded funny in my head :)

Re:Why aren’t distributed systems engineers working on block... by problems on Tuesday August 01, 2017 @12:55PM (#14902805)
The tech is legit for its application - but for many other purposes its very much not. It's being thrown around as a buzzword.
Re:Why aren’t distributed systems engineers working on block... by jliptzin on Tuesday August 01, 2017 @02:04PM (#14903531)
This is true of any new burgeoning technology. Were you around for the Internet boom in the 90s?
Re:Why aren’t distributed systems engineers working on block... by jethro_tell on Tuesday August 01, 2017 @02:40PM (#14903922)
I keep hearing this is like the internet from 30 years ago. Thirty years ago, there was no good way to do ecommerce or send an email. Today, there is a good way to pay for things and do all financial transactions in a simple low hastle way. The internet was sending instant, asyncronious communication vs letters (async) or phone (instant). Bitcoin is creating phone calls and post mail in the email age and using a metal envelope as an upgrade.

Yeah I sent my first emails to a system that connected to neighboring systems via modem at a pre determined time to ftp mail bundles around.

Re:Why aren’t distributed systems engineers working on block... by jliptzin on Tuesday August 01, 2017 @05:36PM (#14905614)
I was talking about how scam artists flocked to the internet with pyramid schemes, chain emails, get rich quick schemes, etc. All that stuff is still here, but it's drowned out by people doing actual normal business now.