Author

Topic: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion - page 16272. (Read 26609319 times)

sr. member
Activity: 406
Merit: 361
Guys can we talk about little people instead of programming shit that none of us have any influence over anyway?
Any videos to share?  Tongue
legendary
Activity: 3374
Merit: 4738
diamond-handed zealot

I agree. I like current development team. I will not replace them. ... I only know that the next stage is Segwit 2x

it ain't happening man
legendary
Activity: 1624
Merit: 1130
Bitcoin FTW!
Seems resistance at $4400 is the only immediate thing on the horizon before we hit $5000. We've been bound to have a breakout soon either way with all the resistance and dumping we've been having in the past few days and weeks. $4300 may be possible tonight if we get a quick buy up of coins. Keep HODLing, friends. Smiley
sr. member
Activity: 420
Merit: 257
It's not 1MB to 2MB. It's more like ~4MB to ~8MB.

orly? What percentage of blocks since SegWit activation have been 4MB?

Quote
The developer(s?) on the 2x Team don't seem to be able to tell the keyboard from the screen.

You're gonna go with that? You realize jgarzik is the lead btc1 dev, right? He's contributed more to Bitcoin than have most core devs and most blockstream devs. Not to mention his huge contributions to Linux before Bitcoin even existed. Your contributions for comparison?

Quote
And the team don't seem to care much about censorship resistance, either.

Bald assertion lacking supporting evidence.

Quote
Node operators, besides trusting the 2x Team to do the right thing technically, must be WANTING to take that step. I, for one, am not.

You're free not to take that step. Careful you don't end up standing exposed in the vast minority. Cold out there.

Quote
But I see you're a legendary member, so you know all this. You trollin' me, man?

You trollin' me, man?

You two, cool down a bit, look up "Sarah Shahi", and look at 4200, and lean back, and it all becomes relativ, outta sudden!




legendary
Activity: 2268
Merit: 1278
Guys can we talk about little people instead of programming shit that none of us have any influence over anyway?
legendary
Activity: 3080
Merit: 1688
lose: unfind ... loose: untight
There was a list of tweets yesterday, with screen grabs from some of the most significant Bitcoin Core developers, where each one said they would refuse to work on 2x, they will probably quit Bitcoin altogether. (sorry I don't have the reference).

That belies a lack of belief in what they are doing. If they are so cock-sure that they are in the right, why would they not continue on developing their minority fork? After all, if they are right, the world will certainly catch up after some time.

In all my years of dev'ing, I have frequently run across situations where the devs though the users 'just didn't understand', while the users thought the devs 'just didn't understand'. Nearly universally, it has been the devs that were in the wrong. For in the end, it is the users that choose what they will accept.
legendary
Activity: 3080
Merit: 1688
lose: unfind ... loose: untight
It's not 1MB to 2MB. It's more like ~4MB to ~8MB.

orly? What percentage of blocks since SegWit activation have been 4MB?

Quote
The developer(s?) on the 2x Team don't seem to be able to tell the keyboard from the screen.

You're gonna go with that? You realize jgarzik is the lead btc1 dev, right? He's contributed more to Bitcoin than have most core devs and most blockstream devs. Not to mention his huge contributions to Linux before Bitcoin even existed. Your contributions for comparison?

Quote
And the team don't seem to care much about censorship resistance, either.

Bald assertion lacking supporting evidence.

Quote
Node operators, besides trusting the 2x Team to do the right thing technically, must be WANTING to take that step. I, for one, am not.

You're free not to take that step. Careful you don't end up standing exposed in the vast minority. Cold out there.

Quote
But I see you're a legendary member, so you know all this. You trollin' me, man?

You trollin' me, man?
legendary
Activity: 2268
Merit: 1278
So I met some little people today. Smaller than my 7 year old nephew, but otherwise fully adult. They were nice, had an hour long chat.
legendary
Activity: 2716
Merit: 13505
BTC + Crossfit, living life.
END list, good luck!

19/9 rayx12     Sad
24/9 kidbitter*  Sad
25/9 binaryreign* Sad
26/9 player99 Sad
27/9 xhomerx10 Sad
28/9 khufuking
29/9 jhayzxenon*
30/9 yermom
01/10 teamtarp*
02/10 bitchick *
03/10 ^BuTcH^
04/10 minermannc
05/10 punisher1314*
06/10 jimbo Toronto*
07/10 player514*
09/10 Oinas*
10/10 bikerlezno*     LAST WINNER
11/10 ted e. bare
12/10 harrymmmm*
13/10 cryptoqueeen*
14/10 bitcoinaire*
15/10 ludwigvon*
16/10 BitchicksHusband*
17/10 shroomskit_disgrace
18/10 dakustaking76
19/10 birobob*
20/10 leowonderful
21/10 paashaas
22/10 cmacwiz*
23/10 spaceman_spiff_original*
24/10 colonel panic
25/10 soullyG
26/10 weltmaster*
27/10 vroom
28/10 entons*
29/10 roombot*
30/10 notme*
31/10 twocorn
01/11 YamashitaRen
02/11 orpington
03/11 Haciendo*
04/11 lilloboy
05/11 jojo69*
06/11 d_eddie*
07/11 empowering*
08/11 northyplole*
09/11 podyx*
10/11 u9y42*
11/11 starving_marvin
12/11 sirazimuth*
13/11 dotto*
14/11 hazukison*
15/11 organic*
16/11 Heater*
17/11 foxygoxy*
18/11 600watt
19/11 arriemoller
20/11 drbrockcoin*
21/11 icygreen*
22/11 rakessh
23/11 erisdiscordia
24/11 oblox*
25/11 mfort312*
26/11 globbo*
27/11 lfc_bitcoin
28/11 conspirosphere.tk*
29/11 rjclarck2000
30/11 last of the v8s *
01/12 newworldcoiner*
02/12 souspeed*
03/12 jaapgvk
04/12 sgk*
05/12 fluidjax
07/12 free-bit.co.in
08/12 imbatman
09/12 yonton
10/12 fragout*
11/12 itod
12/12 lontonbit*
13/12 CistaCista
14/12 cAPSLOCK
15/12 philivey
16/12 marcus_of_augustus*
17/12 mattimann
18/12 coincube*
21/12 2dogs
24/12 bones261*
25/12 mndan
26/12 karatma1*
28/12 deathangel*
30/12 erre
31/12 elwar
01/01/2018 lewis pirenne*
02/01/2018 addressed*
03/01/2018 bathy
05/01/2018 bitcoin psycho
06/01/2018 chowhan
07/01/2018 fabiorem*
18/01/2018 raja_mbz*
22/01/2018 _javi_
26/01/2018 kurious*
28/01/2018 steelboy*
29/01/2018 alcohodl
01/02/2018 cristitcm
18/02/2018 in the silence
20/04/2018 fractal universe*
15/03/2018 Carl85
15/05/2018 oldtimegin*
15/06/2018 samson
16/08/2018 samarkand
legendary
Activity: 1414
Merit: 1000
I think Segwit2x has majority 90-95% of hashpower. It will be solved very quickly :-)

and 0% of full node to keep or accept the 2Mb Block size ...  Roll Eyes
Miners can not force node to "change" of software.

Why do you think, there will be not full nodes with Segwit2X ?  It is few lines of code to change limit from 1MB to 2 MB

  • It's not 1MB to 2MB. It's more like ~4MB to ~8MB.
  • You have to know WHICH lines of code need changing, and change them right. And figure out the technical consequences. The developer(s?) on the 2x Team don't seem to be able to tell the keyboard from the screen. And the team don't seem to care much about censorship resistance, either.
  • Node operators, besides trusting the 2x Team to do the right thing technically, must be WANTING to take that step. I, for one, am not.

But I see you're a legendary member, so you know all this. You trollin' me, man?

I'm not trolling you. I'm software developer with 20 years of experience. I'm writing code for the banks and I can guarantate you, I can add few lines of code and bitcoin core will be supporting Segwit2x within 1 hour.  


Oh my?  We got our answer.  This particular one has "experience," and that is what distinguishes this one from the other FUD spreading trolls.... hahahahaha... and probably this one has "real world" experience, not just that made up internet magic stuffs.    Roll Eyes Roll Eyes       Cheesy



What is your problem ?

I don't gots no problems.

Life is good.  We have a quasi-unexpected upwards price bump, and surely I consider our current $4200-ish price is still within a kind of consolidation range; however, it seems to be getting towards the top of such consolidation range (earlier, I had estimated such consolidation range to be approximately $3400 to $4300), and whoaza.. seemingly better than expected, and possibly could be a sign that we may be breaking to the upside, perhaps?

So yeah, some banker shill jobs, such as you, come in with a bit of desperation and spreading "simplified" nonsense "solutions" ...  So, that really is not a problem, because it is kind of expected, but I doubt that WO participants are going to let you just spew your nonsense without some kind of attempt to get to you to explain yourself... maybe to figure out if we just have a misunderstanding or maybe you are as retarded as your spouted ideas of simple solutions?  perhaps?




- Do you think I do not have 20 years experience in programing ?

Who knows and who cares, and is it relevant?  Why do you feel some need to assert that?  Probably you feel a need to spout your supposed credentials because you are trying to play off of the naive in your spouting out nonsensical ideas and you are asserting "credentials" because even you, in your nonsense, likely realize that your ideas, in themselves, are not going to be very convincing unless you spout out some supposed credentials.   Roll Eyes




 - Do you think I do not live in "real world " ?

You could be bot.     Tongue Tongue


Who is "we got your answer" -> it is "you" ?

I am merely referring to a common theme that you seem to have with your brethren trolls (get yourselves coordinated!  fuck!!!  you don't even know what your brethren trolls are doing?).  Anyhow, the common referred to theme is your supposed "experience" talking point.....   hhhahahahahahahaha  NOT 
I'm not a bot.
Take it as a fact.
legendary
Activity: 2688
Merit: 2470
$120000 in 2024 Confirmed
legendary
Activity: 3920
Merit: 11299
Self-Custody is a right. Say no to"Non-custodial"
I think Segwit2x has majority 90-95% of hashpower. It will be solved very quickly :-)

and 0% of full node to keep or accept the 2Mb Block size ...  Roll Eyes
Miners can not force node to "change" of software.

Why do you think, there will be not full nodes with Segwit2X ?  It is few lines of code to change limit from 1MB to 2 MB

  • It's not 1MB to 2MB. It's more like ~4MB to ~8MB.
  • You have to know WHICH lines of code need changing, and change them right. And figure out the technical consequences. The developer(s?) on the 2x Team don't seem to be able to tell the keyboard from the screen. And the team don't seem to care much about censorship resistance, either.
  • Node operators, besides trusting the 2x Team to do the right thing technically, must be WANTING to take that step. I, for one, am not.

But I see you're a legendary member, so you know all this. You trollin' me, man?

I'm not trolling you. I'm software developer with 20 years of experience. I'm writing code for the banks and I can guarantate you, I can add few lines of code and bitcoin core will be supporting Segwit2x within 1 hour.  


Oh my?  We got our answer.  This particular one has "experience," and that is what distinguishes this one from the other FUD spreading trolls.... hahahahaha... and probably this one has "real world" experience, not just that made up internet magic stuffs.    Roll Eyes Roll Eyes       Cheesy



What is your problem ?

I don't gots no problems.

Life is good.  We have a quasi-unexpected upwards price bump, and surely I consider our current $4200-ish price is still within a kind of consolidation range; however, it seems to be getting towards the top of such consolidation range (earlier, I had estimated such consolidation range to be approximately $3400 to $4300), and whoaza.. seemingly better than expected, and possibly could be a sign that we may be breaking to the upside, perhaps?

So yeah, some banker shill jobs, such as you, come in with a bit of desperation and spreading "simplified" nonsense "solutions" ...  So, that really is not a problem, because it is kind of expected, but I doubt that WO participants are going to let you just spew your nonsense without some kind of attempt to get to you to explain yourself... maybe to figure out if we just have a misunderstanding or maybe you are as retarded as your spouted ideas of simple solutions?  perhaps?




- Do you think I do not have 20 years experience in programing ?

Who knows and who cares, and is it relevant?  Why do you feel some need to assert that?  Probably you feel a need to spout your supposed credentials because you are trying to play off of the naive in your spouting out nonsensical ideas and you are asserting "credentials" because even you, in your nonsense, likely realize that your ideas, in themselves, are not going to be very convincing unless you spout out some supposed credentials.   Roll Eyes




 - Do you think I do not live in "real world " ?

You could be bot.     Tongue Tongue


Who is "we got your answer" -> it is "you" ?

I am merely referring to a common theme that you seem to have with your brethren trolls (get yourselves coordinated!  fuck!!!  you don't even know what your brethren trolls are doing?).  Anyhow, the common referred to theme is your supposed "experience" talking point.....   hhhahahahahahahaha  NOT 
legendary
Activity: 1414
Merit: 1000
I agree. I like current development team. I will not replace them. ... I only know that the next stage is Segwit 2x

There was a list of tweets yesterday, with screen grabs from some of the most significant Bitcoin Core developers, where each one said they would refuse to work on 2x, they will probably quit Bitcoin altogether. (sorry I don't have the reference).

I think, if SIDECHAINS is not working then we must increase block size limit. ... I'm big FAN of SIDECHAIN.
If sobedody do  not trust bitcion then he his free to dump them all.
legendary
Activity: 1414
Merit: 1000
I think Segwit2x has majority 90-95% of hashpower. It will be solved very quickly :-)

and 0% of full node to keep or accept the 2Mb Block size ...  Roll Eyes
Miners can not force node to "change" of software.

Why do you think, there will be not full nodes with Segwit2X ?  It is few lines of code to change limit from 1MB to 2 MB

  • It's not 1MB to 2MB. It's more like ~4MB to ~8MB.
  • You have to know WHICH lines of code need changing, and change them right. And figure out the technical consequences. The developer(s?) on the 2x Team don't seem to be able to tell the keyboard from the screen. And the team don't seem to care much about censorship resistance, either.
  • Node operators, besides trusting the 2x Team to do the right thing technically, must be WANTING to take that step. I, for one, am not.

But I see you're a legendary member, so you know all this. You trollin' me, man?

I'm not trolling you. I'm software developer with 20 years of experience. I'm writing code for the banks and I can guarantate you, I can add few lines of code and bitcoin core will be supporting Segwit2x within 1 hour.  

When I wrote "You have to know WHICH lines of code... bla bla...", I didn't mean YOU-Odalv. I meant YOU-developer-for-2x-Team (which I assume you aren't), and those developer(s?) (more than one? Really?) don't seem to be terribly skilled, according to the few who were able to peek into their github mess before they made it private. So nothing personal with you.

BTW, 20 years developing for banks doesn't necessarily mean anything. Many banks still have their old dinosaur system written in Cobol. No, not your banks. OK. From your words, I suppose you must use more recent programming languages, such as C++, so you are indeed able to tweak bitcoind, allright. Whatever.

However, Mr. Average Bitcoiner doesn't really agree much with the politics and rationale of the 2x fork. He's afraid of China. He's afraid of censorship from his own government. He's afraid he won't be able to run a node any longer because of bandwidth and memory requirements. He likes his SegWit, he waits for the Lightning Network to see what it can deliver.

But let us assume Mr. Average Bitcoiner agrees with 2x. He doesn't care about censorship or centralization. He hates SW. For some very good reason, he hopes LN fails miserably. Whatever. Do you think Mr. A.B. will be so eager to install node software signed by Odalv - even with all these slightly unlikely assumptions?


I'm not writing code for banks for 20 years. (I'm developer with 20 years of experience, ... now I'm witing code for banks)
I'm not bitcoin software developer nor 2x developer. I'm only telling you what is possible. ( I'm HODLER) :-)
full member
Activity: 154
Merit: 101
I think Segwit2x has majority 90-95% of hashpower. It will be solved very quickly :-)

and 0% of full node to keep or accept the 2Mb Block size ...  Roll Eyes
Miners can not force node to "change" of software.

Why do you think, there will be not full nodes with Segwit2X ?  It is few lines of code to change limit from 1MB to 2 MB

  • It's not 1MB to 2MB. It's more like ~4MB to ~8MB.
  • You have to know WHICH lines of code need changing, and change them right. And figure out the technical consequences. The developer(s?) on the 2x Team don't seem to be able to tell the keyboard from the screen. And the team don't seem to care much about censorship resistance, either.
  • Node operators, besides trusting the 2x Team to do the right thing technically, must be WANTING to take that step. I, for one, am not.

But I see you're a legendary member, so you know all this. You trollin' me, man?

I'm not trolling you. I'm software developer with 20 years of experience. I'm writing code for the banks and I can guarantate you, I can add few lines of code and bitcoin core will be supporting Segwit2x within 1 hour.  

When I wrote "You have to know WHICH lines of code... bla bla...", I didn't mean YOU-Odalv. I meant YOU-developer-for-2x-Team (which I assume you aren't), and those developer(s?) (more than one? Really?) don't seem to be terribly skilled, according to the few who were able to peek into their github mess before they made it private. So nothing personal with you.

BTW, 20 years developing for banks doesn't necessarily mean anything. Many banks still have their old dinosaur system written in Cobol. No, not your banks. OK. From your words, I suppose you must use more recent programming languages, such as C++, so you are indeed able to tweak bitcoind, allright. Whatever.

However, Mr. Average Bitcoiner doesn't really agree much with the politics and rationale of the 2x fork. He's afraid of China. He's afraid of censorship from his own government. He's afraid he won't be able to run a node any longer because of bandwidth and memory requirements. He likes his SegWit, he waits for the Lightning Network to see what it can deliver.

But let us assume Mr. Average Bitcoiner agrees with 2x. He doesn't care about censorship or centralization. He hates SW. For some very good reason, he hopes LN fails miserably. Whatever. Do you think Mr. A.B. will be so eager to install node software signed by Odalv - even with all these slightly unlikely assumptions?


Haven't looked at the SW2x code, but if Odalv was really working in a bank, he would know pushing code in a bank means n days development, UAT, business test, documentation, release management, business acceptance and blah blah. Defo not a 2hr work - I would say months - and from what I've read documentation and transparency are lacking a bit in the 2x code
hero member
Activity: 750
Merit: 601
I agree. I like current development team. I will not replace them. ... I only know that the next stage is Segwit 2x

There was a list of tweets yesterday, with screen grabs from some of the most significant Bitcoin Core developers, where each one said they would refuse to work on 2x, they will probably quit Bitcoin altogether. (sorry I don't have the reference).
legendary
Activity: 2520
Merit: 3038
I think Segwit2x has majority 90-95% of hashpower. It will be solved very quickly :-)

and 0% of full node to keep or accept the 2Mb Block size ...  Roll Eyes
Miners can not force node to "change" of software.

Why do you think, there will be not full nodes with Segwit2X ?  It is few lines of code to change limit from 1MB to 2 MB

  • It's not 1MB to 2MB. It's more like ~4MB to ~8MB.
  • You have to know WHICH lines of code need changing, and change them right. And figure out the technical consequences. The developer(s?) on the 2x Team don't seem to be able to tell the keyboard from the screen. And the team don't seem to care much about censorship resistance, either.
  • Node operators, besides trusting the 2x Team to do the right thing technically, must be WANTING to take that step. I, for one, am not.

But I see you're a legendary member, so you know all this. You trollin' me, man?

I'm not trolling you. I'm software developer with 20 years of experience. I'm writing code for the banks and I can guarantate you, I can add few lines of code and bitcoin core will be supporting Segwit2x within 1 hour.  

When I wrote "You have to know WHICH lines of code... bla bla...", I didn't mean YOU-Odalv. I meant YOU-developer-for-2x-Team (which I assume you aren't), and those developer(s?) (more than one? Really?) don't seem to be terribly skilled, according to the few who were able to peek into their github mess before they made it private. So nothing personal with you.

BTW, 20 years developing for banks doesn't necessarily mean anything. Many banks still have their old dinosaur system written in Cobol. No, not your banks. OK. From your words, I suppose you must use more recent programming languages, such as C++, so you are indeed able to tweak bitcoind, allright. Whatever.

However, Mr. Average Bitcoiner doesn't really agree much with the politics and rationale of the 2x fork. He's afraid of China. He's afraid of censorship from his own government. He's afraid he won't be able to run a node any longer because of bandwidth and memory requirements. He likes his SegWit, he waits for the Lightning Network to see what it can deliver.

But let us assume Mr. Average Bitcoiner agrees with 2x. He doesn't care about censorship or centralization. He hates SW. For some very good reason, he hopes LN fails miserably. Whatever. Do you think Mr. A.B. will be so eager to install node software signed by Odalv - even with all these slightly unlikely assumptions?
legendary
Activity: 1414
Merit: 1000
I think Segwit2x has majority 90-95% of hashpower. It will be solved very quickly :-)

and 0% of full node to keep or accept the 2Mb Block size ...  Roll Eyes
Miners can not force node to "change" of software.

Why do you think, there will be not full nodes with Segwit2X ?  It is few lines of code to change limit from 1MB to 2 MB

  • It's not 1MB to 2MB. It's more like ~4MB to ~8MB.
  • You have to know WHICH lines of code need changing, and change them right. And figure out the technical consequences. The developer(s?) on the 2x Team don't seem to be able to tell the keyboard from the screen. And the team don't seem to care much about censorship resistance, either.
  • Node operators, besides trusting the 2x Team to do the right thing technically, must be WANTING to take that step. I, for one, am not.

But I see you're a legendary member, so you know all this. You trollin' me, man?

I'm not trolling you. I'm software developer with 20 years of experience. I'm writing code for the banks and I can guarantate you, I can add few lines of code and bitcoin core will be supporting Segwit2x within 1 hour.  

This is not just about code change, the changes are reasonably trivial, and you are right 1 hour to change the code, a few hours to review and some time for others to check maybe a week or two, some testing on the test chain looking at propagation speed and other implications of the bigger blocks, maybe a month or two, a mechanism so everyone running a current bitcoin version can change their code to run bigger blocks, once enough people are signalling we can begin the change, a lock-in period,  etc... say a few more months at minimum.

If you want to do a hard fork safely and properly it isn't a 1 hour job!!!!

We don't currently need a block size increase.
And everyone knows we don't currently need a block size increase, this is a power grab, its about sacking the Core development team, and replacing it with.... with.... another ready to go team, but who they are is currently unknown.




I agree. I like current development team. I will not replace them. ... I only know that the next stage is Segwit 2x
legendary
Activity: 1414
Merit: 1000
I think Segwit2x has majority 90-95% of hashpower. It will be solved very quickly :-)

and 0% of full node to keep or accept the 2Mb Block size ...  Roll Eyes
Miners can not force node to "change" of software.

Why do you think, there will be not full nodes with Segwit2X ?  It is few lines of code to change limit from 1MB to 2 MB

  • It's not 1MB to 2MB. It's more like ~4MB to ~8MB.
  • You have to know WHICH lines of code need changing, and change them right. And figure out the technical consequences. The developer(s?) on the 2x Team don't seem to be able to tell the keyboard from the screen. And the team don't seem to care much about censorship resistance, either.
  • Node operators, besides trusting the 2x Team to do the right thing technically, must be WANTING to take that step. I, for one, am not.

But I see you're a legendary member, so you know all this. You trollin' me, man?

I'm not trolling you. I'm software developer with 20 years of experience. I'm writing code for the banks and I can guarantate you, I can add few lines of code and bitcoin core will be supporting Segwit2x within 1 hour.  


Oh my?  We got our answer.  This particular one has "experience," and that is what distinguishes this one from the other FUD spreading trolls.... hahahahaha... and probably this one has "real world" experience, not just that made up internet magic stuffs.    Roll Eyes Roll Eyes       Cheesy



What is your problem ?
 - Do you think I do not have 20 years experience in programing ?
 - Do you think I do not live in "real world " ?

Who is "we got your answer" -> it is "you" ?
hero member
Activity: 750
Merit: 601
I think Segwit2x has majority 90-95% of hashpower. It will be solved very quickly :-)

and 0% of full node to keep or accept the 2Mb Block size ...  Roll Eyes
Miners can not force node to "change" of software.

Why do you think, there will be not full nodes with Segwit2X ?  It is few lines of code to change limit from 1MB to 2 MB

  • It's not 1MB to 2MB. It's more like ~4MB to ~8MB.
  • You have to know WHICH lines of code need changing, and change them right. And figure out the technical consequences. The developer(s?) on the 2x Team don't seem to be able to tell the keyboard from the screen. And the team don't seem to care much about censorship resistance, either.
  • Node operators, besides trusting the 2x Team to do the right thing technically, must be WANTING to take that step. I, for one, am not.

But I see you're a legendary member, so you know all this. You trollin' me, man?

I'm not trolling you. I'm software developer with 20 years of experience. I'm writing code for the banks and I can guarantate you, I can add few lines of code and bitcoin core will be supporting Segwit2x within 1 hour.  

This is not just about code change, the changes are reasonably trivial, and you are right 1 hour to change the code, a few hours to review and some time for others to check maybe a week or two, some testing on the test chain looking at propagation speed and other implications of the bigger blocks, maybe a month or two, a mechanism so everyone running a current bitcoin version can change their code to run bigger blocks, once enough people are signalling we can begin the change, a lock-in period,  etc... say a few more months at minimum.

If you want to do a hard fork safely and properly it isn't a 1 hour job!!!!

We don't currently need a block size increase.
And everyone knows we don't currently need a block size increase, this is a power grab, its about sacking the Core development team, and replacing it with.... with.... another ready to go team, but who they are is currently unknown.


Jump to: