~snip~
Finally, a visualization of Bitcoin scaling format. Ive been searching for this thing since i do have a hard time on understanding these flows and now im clearly seeing the possible things might happen ahead. Regarding on approval and rejections and now im quiet excited on the upcoming event would happen on bitcoin history. 
Topic: Bitcoin Scaling Flowchart - page 2. (Read 1467 times)
i don't understand 2 things about this chart.
1. if bitcoin ABC is the Bitmain's UAHF stuff, then it is supposed to exist in case of UASF succeeds. means the line should be after UASF > YES not the NO part.
and also NO part should not lead to "Bitcoin Splits". it is a lot more complicated than that.
UASF: successful with a high hashrate: no Split: Bitmain forks : 2 chain 1 with SegWit and high support and 1 shit
UASF: successful with a small hashrate: split: Bitmain forks : 3 chains all 3 messy until 2 of them die!
2. 2 MB hardfork has been my trouble from the beginning. i don't get the timing. the first thing they said was 6 months after the activation of SegWit, then i saw a 3 month deadline and yesterday i saw JGarzik pointing out that it depends on how SegWit is activated:
fast activation > a shorter time for the HF!!!
slower activation > 3 months
so i don't know what is what anymore
it's just all a mess...
1. if bitcoin ABC is the Bitmain's UAHF stuff, then it is supposed to exist in case of UASF succeeds. means the line should be after UASF > YES not the NO part.
and also NO part should not lead to "Bitcoin Splits". it is a lot more complicated than that.
UASF: successful with a high hashrate: no Split: Bitmain forks : 2 chain 1 with SegWit and high support and 1 shit
UASF: successful with a small hashrate: split: Bitmain forks : 3 chains all 3 messy until 2 of them die!
2. 2 MB hardfork has been my trouble from the beginning. i don't get the timing. the first thing they said was 6 months after the activation of SegWit, then i saw a 3 month deadline and yesterday i saw JGarzik pointing out that it depends on how SegWit is activated:
fast activation > a shorter time for the HF!!!
slower activation > 3 months
so i don't know what is what anymore
it's just all a mess...
Soft fork impossible:
Just send RAW not segwit transaction in block N+1 from B->C.
New segwit software (of miners) will accept it, BITCOIN of 2014 (CLASSIC) will reject.
It can do anyone who own BTC to pay transactions fee.
In block N have segwit transaction from A->B .
In block N+1 have normal transaction from B->C .
Block N+1 rejected by BITCOIN of 2014 (CLASSIC) because B have zero balance.
Wouldn't that then make SegWit a hard fork if clients do not accept it? Are you referring to miners or regular wallet users in this example?In block N+1 have normal transaction from B->C .
Block N+1 rejected by BITCOIN of 2014 (CLASSIC) because B have zero balance.
New segwit software (of miners) will accept it, BITCOIN of 2014 (CLASSIC) will reject.
It can do anyone who own BTC to pay transactions fee.
...
That's a helpful timeline, thanks for posting it.
So, the endgame is finally underway, the final innings. The fact that BTC has bounced up over $2300 gives me some tiny comfort that this will work out OK.
I have read that the SegWit2x has not been thoroughly evaluated however. If the implementation goes poorly or there are knotty problems, this could go on and on. Which would be BAD for BTC price. A lot of money could be lost, some would be mine...
That's a helpful timeline, thanks for posting it.
So, the endgame is finally underway, the final innings. The fact that BTC has bounced up over $2300 gives me some tiny comfort that this will work out OK.
I have read that the SegWit2x has not been thoroughly evaluated however. If the implementation goes poorly or there are knotty problems, this could go on and on. Which would be BAD for BTC price. A lot of money could be lost, some would be mine...
Helpful for visualising what can happen when.
Jump to: