Earlier quoted context omitted.
> A key difference is most of the new techs like Internet, email, Paypal, and so on improved on what people already had in a way that delivered obvious value. I'd argue that for most people the value was only obvious afterwards. To put email in perspective, early adopters had to choose between what they already knew and all the hurdles involved in connecting to the internet and using the new technology. There was als…
The thing I was getting at is, if you had a computer and Internet, then email would be a free, fast alternative to traditional mail. That has obvious benefit. Whereas, these currencies are volatile, slower, often dont allow charge backs, use more energy, and accepted at fewer places. Worse in every way to checking accounts and credit cards. Esp if we have multiple cards or accounts to reduce risk of single institutio…
We can confirm that there was a successful 51% attack on Ethereum Classic
171–180 of 289 posts
Re: We can confirm that there was a successful 51% attack on Ethereum Classic
#172Earlier quoted context omitted.
> A key difference is most of the new techs like Internet, email, Paypal, and so on improved on what people already had in a way that delivered obvious value. I'd argue that for most people the value was only obvious afterwards. To put email in perspective, early adopters had to choose between what they already knew and all the hurdles involved in connecting to the internet and using the new technology. There was als…
The thing I was getting at is, if you had a computer and Internet, then email would be a free, fast alternative to traditional mail. That has obvious benefit. Whereas, these currencies are volatile, slower, often dont allow charge backs, use more energy, and accepted at fewer places. Worse in every way to checking accounts and credit cards. Esp if we have multiple cards or accounts to reduce risk of single institutio…
Quite a few Venezuelans would beg to differ about that.
Re: We can confirm that there was a successful 51% attack on Ethereum Classic
#173Earlier quoted context omitted.
Yet another reason why Proof of Stake is destined to outcompete Proof of Work. ;)
Proof of Stake is a perpetual motion machine. You can't safely tie consensus to something (stake) which is determined by consensus. That's circular reasoning and ungrounded.
Re: We can confirm that there was a successful 51% attack on Ethereum Classic
#174Earlier quoted context omitted.
How is the 51% attack detected?
It's really obvious once the new chain is broadcasted. "Honest" miners switch over to mine on the deepest chain as soon as they become aware of it. It's very rare to even see a 2-block conflict. When you see a large N-block conflict then it's obvious there's a 51% attack going on.
Re: We can confirm that there was a successful 51% attack on Ethereum Classic
#175Earlier quoted context omitted.
If a 51% attack is mounted by adding hash power, wouldn’t the existing miners on the target coin also start shutting down[1] because the competition is higher, reinforcing the strength of the attackers? [1] or migrate from to another coin, such as the coin that the attackers left to fill their void?
51% attackers mine in secret. Basically, you spend your coins today, while controlling a 51% share. When everyone else's 49% hash-power creates 98 blocks, your 51% share will create 102 blocks. But secretly. That's the key. Now that your chain is +4 ahead (or wait even longer and become +10 ahead), you can spend your coins on the public chain. Then, you publish your 102 alternative blocks (which barely adds any hash…
Re: We can confirm that there was a successful 51% attack on Ethereum Classic
#176BTC is hard to attack and not because it's got a ton of hashpower but because it's hard to get paid in any other crypto (if/when payout for asking a successful attack on BTC might be more than USD 10 mil).
Re: We can confirm that there was a successful 51% attack on Ethereum Classic
#177Earlier quoted context omitted.
The six-blocks-in-a-row problem seems less of an impedence to me - because the "legitimate" blocks are still available to the malicious actor. Therefore, if our malicious miner identifies that they have had poor luck and begun to fall behind the "legitimate" chain by a block or two they can start the make-a-longer-competing-chain process over again from the legitimate head with -as far as I can see- no downsides exce…
They still have to get out ahead by six blocks, however. This drops to zero every time they start over, so it doesn't change the basic calculus.
The chain starts at block 1000, and you make a spend that will be included at block 1001 on the public chain. At the same time, you start mining your private chain from block 1000 (and you don't include that transaction in it). Now, the exchange you're using requires 6 blocks of confirmation, so you need to wait until block 1006 on the public chain before you can actually take delivery. Now that you've done that, you can publish your private chain at block 1007 (or 1008, etc) and since it's the longest chain, it'll be accepted by the public.
You didn't have to get 6 blocks before the public chain got 1 - you only needed to get 1 more block than the public chain, at some point after the public chain has mined 6 more blocks.
1000 - 1001 - 1002 - 1003 - 1004 - 1005 - 1006 1008 Public Chain
\ 1001 - 1002 - 1003 - 1004 - 1005 - 1006 - 1007 / Private ChainRe: We can confirm that there was a successful 51% attack on Ethereum Classic
#178Earlier quoted context omitted.
51% attackers mine in secret. Basically, you spend your coins today, while controlling a 51% share. When everyone else's 49% hash-power creates 98 blocks, your 51% share will create 102 blocks. But secretly. That's the key. Now that your chain is +4 ahead (or wait even longer and become +10 ahead), you can spend your coins on the public chain. Then, you publish your 102 alternative blocks (which barely adds any hash…
If only we had a currency that was immune to 51% attacks because a government was willing to use force to preserve its value, and therefore doesn't need a massive use of energy for its proof of work.
The only problem here is that PoW only knows one cost: hashing, and due to macro shifts in mining hardware this can sometimes go down a lot more than the value of a coin (which makes the cost of this attack worth it).
As soon as you start introducing measures to subvert this attack you are subverting either decentralization or stability. If you for example program clients to not accept reorgs deeper than 10 blocks (for example) you simply introduce new attack vectors that can split the network (into following different chains - which is even scarier than 51% attacks).
If every x blocks you snapshot the chain and force everyone to follow that snapshot you just centralized the chain, etc.
Re: We can confirm that there was a successful 51% attack on Ethereum Classic
#179Earlier quoted context omitted.
Would you mind elaborating on this for someone unfamiliar?
Imagine all the Bitcoin miners out there right now using their ASICs to do extremely efficient hashing in the hopes of generating a block reward. Let's didactically suppose there are 100 such miners total. Now imagine Dinkycoin comes along and releases their cryptocurrency that uses the same hashing mechanism for the block reward. Initially they have the block difficulty level pretty low as there aren't that many peo…
> Once the Bitcoin miner has a competing branch with greater total difficulty than the rest of the network, the network must accept that branch as the winner.
These statements directly contradict each other. The very, very obvious solution is to say that, if 20 confirmations validate that a transaction happened, then validated transactions can't be rolled back. (They're validated!) Once block 26 comes online, block 6 is a permanent feature of the blockchain. That's the only possible meaning of "accepting that a transaction went through". And, note, that is the definition being used now to label this an "attack" rather than "huh, look what happened".
Re: We can confirm that there was a successful 51% attack on Ethereum Classic
#180Earlier quoted context omitted.
I'm trying to understand what "cashing out" would look like in an attack like this. One option would be to send coins to an exchange as you mentioned, and I presume cash them out before publishing your longer chain. However, after the attack wouldn't it be easy to compare both chains and see which coins were double spent? Wouldn't you obviously be the perpetrator, having both double spent, as well as having cashed ou…
It absolutely would be easy to compare both chains and see exactly which coins were double spent, and you'd obviously be the perpetrator. Not that I advocate it, but if you wanted to carry out an attack, you'd likely target an exchange that didn't require verification, and you might exchange and withdraw under another coin (ex: trade ETC for ETH). Then spend and/or clean your ill-gotten gains.