Topic: ETH price soaring. Are you going to move some BTC into ETH? - page 29. (Read 198796 times)

I think the last week or two is proof that ETH has a pretty solid foothold right now.

Having an extended DDOS attack which resulted in (yet another) fork,
and the release of a competitor (Zcash) causing total chaos for the markets,
I was actually surprised the price of Ethereum didn't lose more.


News like this could also be a positive sign that the sky isn't falling for Vitalik Buterin and friends.
http://www.coindesk.com/microsoft-launching-new-ethereum-blockchain-product/
Article about Microsoft using Ethereum in some projects.

You said it seemed it wouldn't go below $10 a page back, so I wouldn't start crowing too loudly. 

Lol I'm beginning to believe my own shit in this thread, I feel like nostradamus.

Bitcoin is up and ETH is down. That's what happen all the time, the trend is always like that.

I may jump fast once the price of bitcoin starts to fall, but for now, I have to enjoy the big price of bitcoin and watch closely the price of ETH. I believe if I will jump now, it will already guarantee a profit but I want more so I need to be a little patient.

It can go sub 0.01 but I'm also hesitant to expect a big drop in terms of fiat, the maximum I can see it fall is $7-8 and that's not a given, clear support is at $10 for now and I don't think it will break unless there are some very bad news.

On the other hand, any kind of good news would create a small rally (it has been very quiet after devcon2 and with plenty of bad news concerning the constant attacks).

My investment on Ethereum is in fiat right now so I'm not concerned at all, I'm not day trading this anymore since it's not very logical. We'll see how it goes in an year or so.

Bitcoin pump will end soon, yes that's right, this is just a pump based on lighting network, segwit and yuan losing power. It will come back down to low 600s soon.

My instincts are telling me sub 0.01, but I'm hesitant to listen closely to them given the number of unexpected rallies (and whales) this thing has.

It has consumed its potential in my opinion.  It has been pump hard, dump hard then pump hard again.  This price is purely manipulation, the way i see it.  So no for me.  I won't be moving my bitcoin just to buy this token.  There is far more important investment out there than buying into this purely manipulated market. ( not saying they can hardfork ETH anytime they want)

The Ethereum price broke below 0.014 bitcoin earlier. But the dollar price is still above $10.0 now.

Broke below support with long term indicators, such as the 200-day SMA, trending down. I'd have thought whale-tard would have stepped in, but he seems to be conspicuously absent.

The ETH is not hurt by the bitcoin. It is hurt by the ZCash. More funds will be diverted into the ZCash in the short term.

i wonder how much BTC is hurting ETH? I thought after the hard fork  that everyone would switch, I was totally surprised on what happened afterwards. It almost makes me wonder which one to keep. But, I think ETH will stay on top, but it would help if ETC would go away, but probably won't happen soon.

If the hard fork second time is successful, then the Ethereum price could rise from the current low levels.

https://www.reddit.com/r/ethereum/comments/58i8e0/update_on_hf_2_and_client_optimizations/?st=iuqn0x15&sh=4621f3c6

Update on HF 2 and client optimizations

Geth developers are working on an optimization that will store a direct on-disk table representing account storage, allowing accounts to be accessed in O(1) leveldb reads instead of O(log(n)) leveldb reads as is the case now. Preliminary tests suggest a 5x speedup in processing account reads if this is done. This is a fairly large change to the client (not quite but almost as complex as journaling) so don't expect it out tomorrow, but it will make a large difference.
Simpler optimizations on the in-memory trie cache are achieving ~30% speedups.
We're looking at simple forms of state tree pruning to allow nodes to reduce their storage size without having to delete the DB and fast sync from scratch. This should increase processing time indirectly.
The main debate in the hard fork discussions is whether to implement EIP 158 with section 2 or with (1c) (there is little value in doing both). The two carry different risks; section 2 is more complex from an in-EVM consensus standpoint, whereas (1c) requires more substantial re-architectures in other areas of geth to implement, as iterating through all accounts is not a use case that needed to be supported in all nodes before.
We are considering adding replay protection, likely either EIP 155 or a simpler trick involving using the upper bits of the tx nonce as a chain ID, but nothing is yet finalized.

I agree with that. The Ethereum is still quite young. But it has very good community support at the moment.

ETH was actually going places before the attacks! Notwithstanding it did not lose all its shine and on the flip side, all these attacks can end up bringing to the fore the doggedness of the coin and people would count that as plus. ETH has been one coin that puts bitcoin on its toes and thus creating keen competition, which presents opportunities for profit making for the traders that are looking at the right pictures.

I actually do not hold bitcoins for the future but i am just dancing with the current trend of ETH, it is very predictable and if you will play with it you acn easily make money even in a short period of time.

ethereum has been hacked so many times and failed now its just another useless altcoin ... one guy just keeps insanely buying it up instead of letting it crap its pants and find its real value ... w/e if he wants to lose his bitcoin fortune.

that is right. If the Ethereum is attacked when its market cap is just $1 billion, the loss will be smaller.

It is better for the Etheruem or the bitcoin to be attacked when it is still young. The related loss will be limited.

The ETH is quite good. It is going to fork again.

https://www.reddit.com/r/ethereum/comments/58i8e0/update_on_hf_2_and_client_optimizations/?st=iulbbti4&sh=44772d5b

Geth developers are working on an optimization that will store a direct on-disk table representing account storage, allowing accounts to be accessed in O(1) leveldb reads instead of O(log(n)) leveldb reads as is the case now. Preliminary tests suggest a 5x speedup in processing account reads if this is done. This is a fairly large change to the client (not quite but almost as complex as journaling) so don't expect it out tomorrow, but it will make a large difference.
Simpler optimizations on the in-memory trie cache are achieving ~30% speedups.
We're looking at simple forms of state tree pruning to allow nodes to reduce their storage size without having to delete the DB and fast sync from scratch. This should increase processing time indirectly.
The main debate in the hard fork discussions is whether to implement EIP 158 with section 2 or with (1c) (there is little value in doing both). The two carry different risks; section 2 is more complex from an in-EVM consensus standpoint, whereas (1c) requires more substantial re-architectures in other areas of geth to implement, as iterating through all accounts is not a use case that needed to be supported in all nodes before.
We are considering adding replay protection, likely either EIP 155 or a simpler trick involving using the upper bits of the tx nonce as a chain ID, but nothing is yet finalized.