Topic: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion - page 16568. (Read 26623480 times)
August 20, 2017, 07:21:23 PM
Some stop orders got rekt on Finex. Now we're back to parity with Stamp
August 20, 2017, 07:16:45 PM
Did you feel that small ripple that just resonated through time and space ?
That was me just submitting all my docs to Kraken for Tier 3 and Tier 4.
If you're holding BCH, I would recommend dumping before Wednesday.
That was me just submitting all my docs to Kraken for Tier 3 and Tier 4.
If you're holding BCH, I would recommend dumping before Wednesday.
Just quoting...
August 20, 2017, 06:49:58 PM
If a majority of those 90%+ hashrate signaling for Segwit2X
Only 16% do this.
16%, it's 1 pool ... not hard to identify, for sure.
August 20, 2017, 06:48:30 PM
Reddit gold
Quote
No one expected it to be perfect the moment it launches. I half expected a real community though, that will atleast create 1 frontpage post with the risks of the current situation. Instead you have 90% anticore propaganda and circlejerking. You know it's AstroTurfing when it looks so different from what r/Bitcoin looked during the times of ghash.io having 51% hash. The community was outraged. It is a real risk, the biggest that a blockchain based currency can face.
https://www.reddit.com/r/btc/comments/6ux2xt/antpool_jihan_thank_you/ 
August 20, 2017, 06:38:40 PM
But everything has limits....
so, you want dump 70 000 000 000 USD ?
good luck to find asset to dissipate this in 1 week ... or month ... or year.
and, Bitcoin, it's a network ... not only "money".
You can't kill a network. You can't kill a P2P network ... at all.120 000 personal computers are used to maintain this network "online".
Problem is: If a majority of those 90%+ hashrate signaling for Segwit2X doesn't chiken out.... Better CORE start coding a new difficulty adjustment algo for Bitcoin to survive or a PoW change. WHich is ironic because both of those alternatives are way more disruptive than a simple 2x block size increase.
...even more so as a block size increase is baked in - its just a matter of when (and how)
I cannot wait for the whole situation to be in the rear view one way or another tbh
That will be a good day for us ALL.
August 20, 2017, 06:30:38 PM
But everything has limits....
so, you want dump 70 000 000 000 USD ?
good luck to find asset to dissipate this in 1 week ... or month ... or year.
and, Bitcoin, it's a network ... not only "money".
You can't kill a network. You can't kill a P2P network ... at all.120 000 personal computers are used to maintain this network "online".
Problem is: If a majority of those 90%+ hashrate signaling for Segwit2X doesn't chiken out.... Better CORE start coding a new difficulty adjustment algo for Bitcoin to survive or a PoW change. WHich is ironic because both of those alternatives are way more disruptive than a simple 2x block size increase.
August 20, 2017, 06:22:48 PM
But everything has limits....
so, you want dump 70 000 000 000 USD ?
good luck to find asset to dissipate this in 1 week ... or month ... or year.
and, Bitcoin, it's a network ... not only "money".
You can't kill a network. You can't kill a P2P network ... at all.120 000 personal computers are used to maintain this network "online".
August 20, 2017, 05:26:44 PM
They don't need to run btc1. It's just a simple patch to core code.
They don't need to keep signaling anymore. If they keep doing it, it needs to be interpreted as their intention to follow on with the agreement. In this case with the 2x part of it.
It's not because they "signaled" it... it is because the keep signaling it now.
What other interpretation would be possible for their signaling now?
Trying to play chicken with the Core team to get them to agree to Segwit2x agreement even if no one from the Core team was there to be party to the agreement. I think the big blockers will be the ones to pull off to the side come early November.
Well, CORE should not try to play chiking with 90%+ of the hasrate. If they do, maybe this time it won't end good.
P.S.: And I am pro-CORE. But everything has limits....
August 20, 2017, 05:18:36 PM
They don't need to run btc1. It's just a simple patch to core code.
They don't need to keep signaling anymore. If they keep doing it, it needs to be interpreted as their intention to follow on with the agreement. In this case with the 2x part of it.
It's not because they "signaled" it... it is because the keep signaling it now.
What other interpretation would be possible for their signaling now?
Trying to play chicken with the Core team to get them to agree to Segwit2x agreement even if no one from the Core team was there to be party to the agreement. I think the big blockers will be the ones to pull off to the side come early November.
August 20, 2017, 05:15:54 PM
Any ideas how to best prepare for the next fork (which will probably be our own)?
Pls don't say Litecoin.
Pls don't say Litecoin.
Just move your coins to addresses where you control the private keys and hope it gets sorted out. If neither Core nor btc1 are going to do adequate replay protection, it might get really messy. However, BU has been around for quite some time, and someone could have attempted a hard fork with that software, but no one did. Let's hope that no one will dare execute btc1 hard fork, and we will just have to deal with the scaling squabble for many months, if not years to come.
BU was most of the time below 40% hashrate. Segwit2x is over 90%.
Just because they signaled it doesn't mean they are actually going to run the software when the time comes to pick sidea. I don't even believe many were running btc1 to enforce BIP91. Everyone just went along. Thank goodness.
If we get through this smoothly without a fork, then MOON™ is on. Am I right in assuming Core are going to reject 2X, so will there be ragequit and fork?
August 20, 2017, 05:15:01 PM
Sage advice, as always
August 20, 2017, 05:11:08 PM
Any ideas how to best prepare for the next fork (which will probably be our own)?
Pls don't say Litecoin.
hodlPls don't say Litecoin.
August 20, 2017, 05:09:44 PM
Any ideas how to best prepare for the next fork (which will probably be our own)?
Pls don't say Litecoin.
Pls don't say Litecoin.
Just move your coins to addresses where you control the private keys and hope it gets sorted out. If neither Core nor btc1 are going to do adequate replay protection, it might get really messy. However, BU has been around for quite some time, and someone could have attempted a hard fork with that software, but no one did. Let's hope that no one will dare execute btc1 hard fork, and we will just have to deal with the scaling squabble for many months, if not years to come.
BU was most of the time below 40% hashrate. Segwit2x is over 90%.
Just because they signaled it doesn't mean they are actually going to run the software when the time comes to pick sidea. I don't even believe many were running btc1 to enforce BIP91. Everyone just went along. Thank goodness.
They don't need to run btc1. It's just a simple patch to core code.
They don't need to keep signaling anymore. If they keep doing it, it needs to be interpreted as their intention to follow on with the agreement. In this case with the 2x part of it.
It's not because they "signaled" it... it is because the keep signaling it now.
What other interpretation would be possible for their signaling now?
August 20, 2017, 05:06:43 PM
Any ideas how to best prepare for the next fork (which will probably be our own)?
Pls don't say Litecoin.
Pls don't say Litecoin.
Just move your coins to addresses where you control the private keys and hope it gets sorted out. If neither Core nor btc1 are going to do adequate replay protection, it might get really messy. However, BU has been around for quite some time, and someone could have attempted a hard fork with that software, but no one did. Let's hope that no one will dare execute btc1 hard fork, and we will just have to deal with the scaling squabble for many months, if not years to come.
BU was most of the time below 40% hashrate. Segwit2x is over 90%.
Just because they signaled it doesn't mean they are actually going to run the software when the time comes to pick sidea. I don't even believe many were running btc1 to enforce BIP91. Everyone just went along. Thank goodness.
August 20, 2017, 05:02:46 PM
Pls don't say Litecoin.
I won't because if I do the censor will delete my post, but it looks like a good hedge.
But I am confident that the BitChes will lose soon their war and BTC will moon again.
August 20, 2017, 05:01:36 PM
Any ideas how to best prepare for the next fork (which will probably be our own)?
Pls don't say Litecoin.
Pls don't say Litecoin.
Just move your coins to addresses where you control the private keys and hope it gets sorted out. If neither Core nor btc1 are going to do adequate replay protection, it might get really messy. However, BU has been around for quite some time, and someone could have attempted a hard fork with that software, but no one did. Let's hope that no one will dare execute btc1 hard fork, and we will just have to deal with the scaling squabble for many months, if not years to come.
BU was most of the time below 40% hashrate. Segwit2x is over 90%.
Also BCH is a completely new altcoin. It even has modification in the difficulty adjustment algo, which has allowed it survive. With current diff algo the minoritary Bitcoin chain would really struggle to survive if a HF happens because of Segwit2x discrepancies.
August 20, 2017, 05:00:21 PM
Any ideas how to best prepare for the next fork (which will probably be our own)?
Pls don't say Litecoin.
Pls don't say Litecoin.
Ok, Won't say it.
August 20, 2017, 04:58:34 PM
Isn't Segwit already priced in?
BCH sliding way lower would be better news for BTC price...
BCH sliding way lower would be better news for BTC price...
Mostly priced in but.... There's always doubt: An implementation failure that triggers on activation, a coordinated hashrate attack, etc etc...
So it still have some upside potential if everything goes OK (as expected). Also BCH should go down and flow into BTC.
August 20, 2017, 04:57:35 PM
Any ideas how to best prepare for the next fork (which will probably be our own)?
Pls don't say Litecoin.
Pls don't say Litecoin.
Just move your coins to addresses where you control the private keys and hope it gets sorted out. If neither Core nor btc1 are going to do adequate replay protection, it might get really messy. However, BU has been around for quite some time, and someone could have attempted a hard fork with that software, but no one did. Let's hope that no one will dare execute btc1 hard fork, and we will just have to deal with the scaling squabble for many months, if not years to come.
August 20, 2017, 04:47:49 PM
Any ideas how to best prepare for the next fork (which will probably be our own)?
Pls don't say Litecoin.
Pls don't say Litecoin.
Jump to: