Live data from Hacker News

Bitcoin – Potential Network Disruption on July 31st

bitcoin.org

201–210 of 381 posts

Re: Bitcoin – Potential Network Disruption on July 31st

#201
post #179

Earlier quoted context omitted.

I didn't really find any proper reason as to how it is being pumped. Just about ETC misleading people into buying it. Any links? >There's no real technological innovation or developer interest in ETC. I mean, ETC guys can just push all of the new developments in ETH to their code. The codebase is the same. There probably won't be any original developments in ETC, but they don't really need much to stay on par with ET…

Barry Silbert/Coindesk are quite pro-ETC and anti-ETH, just to name two examples. Here's an intro (google around for more): https://www.reddit.com/r/ethtrader/comments/6d62td/the_story... https://medium.com/@charlescmackay/barry-silbert-and-the-cos... Not saying ETH is perfect, far from it, but ETC is a pumped up scam for sure. They're using "Ethereum" in the name to fool newbies, likely propping up the price at curr…

Let me get this out of the way: While I admire the contributions by the Ethereum Foundation and wish them all the best, I think the hard fork shouldn't have been done. I think letting the money get away would show that they actually mean the 'code is law' statement that was thrown around (Note that I have till date never owned ETH or ETC and probably won't in the near future)

Now that that's out the way, let me say the cognitive dissonance in that post is palpable. Words are conveniently placed so spin the situation into something else.

r/Bitcoin is shown to be the culprit here, just because they are the ones with the most subs and poking fun at ETH. The reality was every other altcoin community was doing the exact same thing. I was watching everything closely when as it unfolded. I can link you posts from other subreddits if you want.

>The Ethereum community stuck together, worked together, and fought back. Successfully

This is false. Quite a few of the ETH community fought for not forking. No one wants to lose money, so who wouldn't want to fork. Many vocal people invested quite a bit of their funds so it is completely understandable.

The irony here is, even the 'rogue hackers' were probably part of the ETH community. Who else would know the codebase so well? The phrase 'stuck together' is false.

>Barry Silberts co-owned exchange "Poloniex" raced to be the first exchange to start trading the coin of this old chain (ETC)

Looks like something a smart person would do. I would also capitalize on trades that people will make with ETC. You've immediately got twice the volume therefore double the fees that can be collected. This is clearly a good business decision. Doing that before other exchanges means more fees collected!

>ETC is an Attack against Ethereum

That's a bold claim. I don't see any 'attack'. Any person with half a brain can see which one is the original ETH. It is a fork, so calling it an attack is dramatic.

>It's a technological attack, and a monetary scam

Big words. I don't see any technology being used to attack ETH. Just people mining the coin they support.

>If you have bought, or holding, or still planning to buy ETC, be ready to get hit by some nasty surprises down the road ( on those days - and I can already foresee a few - I will be linking everyone back to this thread right here, as a reminder).

Now who sounds like they are spreading FUD?

-------------------

While Poloniex was made out to be the perpetrator, it has only 5% of the 24hr transaction volume. So pointing fingers at the Poloniex person was baseless and foolish.

I believe in a bright future for ETH and will probably get into it, but falsifying events is a great way to show others that the community can't self-police and is an echo chamber.

Re: Bitcoin – Potential Network Disruption on July 31st

#202

All this "unconsensus" is weird to me given that PoW was created to fix just that. I don't understand how can any other group of people decide what should happen other than the miners. After all, anybody can be a miner. Anything other than that just doesn't make it decentralized anymore. If you trust the developers, exchanges or even users to make decisions, then why not just make a BitcoinSQL where the servers are c…

PoW does not "fix" consensus. It orders transactions. That is the only thing it can do, but it is an important thing as the well defined ordering of transactions globally is the only thing that can prevent double spending. Miners are paid to do this.

How the software functions is the subject of the old-fashioned open source project. This is also the weak spot. If you want to increase the number of available Bitcoins, your first step is to convince all developers on the project.

Re: Bitcoin – Potential Network Disruption on July 31st

#203
post #173

Earlier quoted context omitted.

I am rather stunned that the entire global bitcoin network, with its colossal combined computing power, and staggering electricity consumption, is only capable of sustaining 7 tps. The level of inefficiency here is mind-boggling. Surely this must be one of the least efficient, least environmentally-friendly computing ventures ever?

This is only layer1 (like IP in the networking world). Wait until layer2 comes (Lightning Network, TumbleBit), then we will reach the scalability levels we need for the entire planet to use the same blockchain.

Err, each layer on top of IP slows down traffic, not speeds it up. The extra overhead and retransmits result in less useful data being transferred with each packet.

Perhaps not the best example to use.

Re: Bitcoin – Potential Network Disruption on July 31st

#204
post #78

Earlier quoted context omitted.

> However, any changes require consensus from the miners who create Bitcoins and process transactions, and because it's not in their best incentive to do anything to reduce those transaction fees, no change has received majority consensus. This is an unfortunate misunderstanding on the part of the miners, and the math is really simple: imagine a network on top of Bitcoin, e.g. lightning.network, which can process 10…

I think what the miners are afraid of, is that the power of the bitcoin network, leaves their hands and fall into the hands of second layer operators. At the same time, a higher blockchain size would make it less profitable for small miners, to mine bitcoin. Bitfury recently released an analysis, that predicts that 95% of current miners, would find mining to be unprofitable at blocksize of 8MB. This would further cen…

> Bitfury recently released an analysis, that predicts that 95% of current miners, would find mining to be unprofitable at blocksize of 8MB.

I don't understand this. Due to what would 95% of current miners find mining unprofitable at 8MB blocks?

Re: Bitcoin – Potential Network Disruption on July 31st

#205

All this "unconsensus" is weird to me given that PoW was created to fix just that. I don't understand how can any other group of people decide what should happen other than the miners. After all, anybody can be a miner. Anything other than that just doesn't make it decentralized anymore. If you trust the developers, exchanges or even users to make decisions, then why not just make a BitcoinSQL where the servers are c…

One of the things that was confusing to me is the U in UASF. It's not a user actived soft fork, its certain miners vs other miners.

Understanding a UASF requires understanding where hashrate comes from. Bitcoin is very clever in that hashrate costs money, and not just a little money, it costs a lot of money.

Which chain has more work is approximately saying 'which chain destroyed the most value in electricity'. The proof of work powering bitcoin costs hundreds of millions of dollars per year.

Nobody burns hundreds of millions per year for free. They do it because you receive Bitcoins as payment, and then you can go sell those Bitcoins to pay your electricity and hardware bills.

That means you have to be able to find someone willing to buy them. A UASF is a bunch of users saying 'we'll never buy your coins unless you follow our fork'. If only a few users say this, it's no big deal, and the miners can decide to listen to them, or they can decide not to bother.

But if 2/3rds of the userbase all agree to enforce the UASF, the miners suddenly are going to have a lot of trouble selling their non-UASF coins. Enough trouble that they probably can't pay their electricity bills. Even worse for the miners, the UASF chain has a high block reward, so they know that if they do mine the UASF chain, they actually will be able to pay their bills. And if a competing miner does it, that competing miner will have much higher margins, higher profits, and will be able to out-invest you when it comes to buying more hashrate.

Scariest of all, if the UASF chain ends up with more work than the non-UASF chain, the non-UASF chain gets completely obliterated, and its full transaction history is reversed, and all the blocks you mined as a miner are destroyed. So even if the UASF doesn't seem to have majority support, it's really bad for you as a miner and as a user if it ever eventually does gain majority support. So when the UASF has a lot of traction, really the safest move is to join the UASF, because at least then your coins aren't at risk of being eliminated entirely.

Re: Bitcoin – Potential Network Disruption on July 31st

#206
post #53

Well, that's a remarkably uninformative announcement. Here's an attempt at a neutral tl;dr from a Bitcoin amateur. Bitcoin is currently suffering from significant scaling problems, which lead to high transaction fees. Numerous proposals to fix the scaling issue have been proposed, the two main camps being "increase the block size" and "muddle through by discarding less useful data" (aka Segregated Witness/SegWit). Ho…

It is probably not possible to solve the scaling problems on-chain - a secure decentralized consensus on a global scale cannot be fast. Currently the bitcoin protocol processes about 7 transactions per second. Doubling the speed by doubling blocks will not make it much closer to the 50K transactions per second of a system like VISA. But it is probably possible to scale the transaction system off-chain - with https://…

I have been being told all along that the 7TPS limit is just an artificially-imposed limit and it's only there because the devs don't actually know what would happen if they (say) doubled it... was this a lie?

Re: Bitcoin – Potential Network Disruption on July 31st

#207
post #168

Earlier quoted context omitted.

Why do you think that being the exchange used for cashing out is a bad position to be for an exchange? My understanding is, exchanges earn money on commissions, so the more volume they get, the better, and cashing out sure is some volume. Those speculators who buy BTC on the wrong chain -- sure, they will take a hit on that. But the exchange itself will still get their commission just fine. Am I missing something her…

You are actually right. It is not the exchange that would be affected, provided they haven't taken positions in their own markets. Exchanges should make it pretty clear on which chain they will be operating, still. I don't think trying to process transactions on both chains would be the right move.

[deleted]

Re: Bitcoin – Potential Network Disruption on July 31st

#208
post #59

Well, that's a remarkably uninformative announcement. Here's an attempt at a neutral tl;dr from a Bitcoin amateur. Bitcoin is currently suffering from significant scaling problems, which lead to high transaction fees. Numerous proposals to fix the scaling issue have been proposed, the two main camps being "increase the block size" and "muddle through by discarding less useful data" (aka Segregated Witness/SegWit). Ho…

A neutral response would probably not use the phrasing 'muddle through' with regards to the solution endorsed by most of the technical experts in the Bitcoin space. ---- Right now there are 3 implementations of Bitcoin in the wild, and each of the 3 will react differently to different network events. The network is essentially splitting apart, with each fragment driven by a different faction. If you don't know what t…

> sell all of your coins on the forks that you disagree with

How would you do this in practice? Most exchanges probably won't code in the ability to sell on multiple chains.

Re: Bitcoin – Potential Network Disruption on July 31st

#209
post #168

Earlier quoted context omitted.

Why do you think that being the exchange used for cashing out is a bad position to be for an exchange? My understanding is, exchanges earn money on commissions, so the more volume they get, the better, and cashing out sure is some volume. Those speculators who buy BTC on the wrong chain -- sure, they will take a hit on that. But the exchange itself will still get their commission just fine. Am I missing something her…

You are actually right. It is not the exchange that would be affected, provided they haven't taken positions in their own markets. Exchanges should make it pretty clear on which chain they will be operating, still. I don't think trying to process transactions on both chains would be the right move.

> I don't think trying to process transactions on both chains would be the right move.

Why is that? Wouldn't this be the most profitable approach for an exchange?

Re: Bitcoin – Potential Network Disruption on July 31st

#210

All this "unconsensus" is weird to me given that PoW was created to fix just that. I don't understand how can any other group of people decide what should happen other than the miners. After all, anybody can be a miner. Anything other than that just doesn't make it decentralized anymore. If you trust the developers, exchanges or even users to make decisions, then why not just make a BitcoinSQL where the servers are c…

> I don't understand how can any other group of people decide what should happen other than the miners.

You are missing one of the key economic components of Bitcoin. Mining costs a lot of money. Nobody mines for free or at a loss, because 'at a loss' means to the tune of hundreds of millions of dollars.

Miners unquestionably mine the chain that has the highest block reward. Historically, hashrate has always been a function of $hardware_efficiency * $block_reward. If the block reward goes down, hashrate goes down (except where hardware efficiency is increasing fast enough to compensate). This is a lot more visible in the altcoin world, where miners can easily jump from coin to coin, and do as the coins fluctuate in value.

So what determines the price of the coin? Well, supply and demand. If people don't like your fork, there will be low demand, and your fork will have a low coin price. This will result in low hashrate, because miners aren't going to be willing (or even capable) of mining your fork at a loss.

Consensus ends up being fundamentally driven by the economics, and the economics follow the userbase.

Post reply on HN