we will re-evaluate tomorrow.... 40% has upgraded.

we cannot push another update round really

hashcows was very cooperative.

apparently there is another multipool

or...  huge hashers

that was the intention yes

but it is only 5ghash/21 they would have pointed.

so i think this thing works and i am going to continue cooperation.

well there are the multipools...

thats why i wanted to wait guys... i can sustain this, i think, for max 48-72 hours.

sometimes pushing out more updates is not the solution.

soon there... lets c if the deals we made actually do something.

all large players have been upgraded... non update would mean you get an update message @ 21203.. and your wallet wont function anymore.

its just beneficial to yourself to update.

and to spare this thread of the "support" questions.

we have announced it through all channels.

little more we can do.

the old wallets will have problems since getnextworkrequired is not in line with the situation of the large players ( exchanges, seednodes, pools and multipools )

ppl upgrade... it still stuck @ +- 30%

do the gravity 2 fix.

lands on tuesday is my preference.....

also i created a program to check wallet version of ip.

i will extend the update ( if we do it ) to include the version in the irc name as well.

that as backup... if the primary method doesnt work.

so now i am going to continue foundation...

i will be here again in a few,...

agree, thats why we set the block to 21203.

only one problem remains: the weekend.

we dont want the exchanges to be detached.

aka to fork.

so blocknumber needs to absolutely right this time.

if we update we will do a special kind of giveaway.

i can see what ip is at what version.

so by upgrading i can reward ppl.

just give ip, i check on version.. if right version -> payment.

lot of work. but will work.

will make a quick program for this.

i agree with this as well.

i have the option to hold middlecoin completely off for 1  day.

if there is no other way.

i have noted that blocknumber down.....

block options are

19763
19238
18758

the blocks are located in slow periods... @ about half the retargetspan

lets first see what happens in 3 hours.

thanks

i looked into the upgrade message.  its only shown when an invalid chain is found ( invalid proof of work )

printf("InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.\n");

so its kinda automatic @ block 21203... i couldnt find a way to push a message out. only thing i can do is provide future support on this. but then again... another update would be needed ( but that doesnt affect clients on current grav-2 version.. its just a program update.. no proofofwork/diff update ).

setting it at 18240 is WAY too risky... we have a very good chance of a fork. thats more ugly then just wait for kgw to kick in.

everyone has to update.. setting it at that block... would give them merely a day.

also take the weekend into account.

i dont think we should do that.

we have chosen block 21203 for a reason... allowing 7-10 days to upgrade.

if we make a change... it would have to be at least block 20k

havent done it before... need to look.

so i will put the foundation on hold and do once more an update

give me a blocknumber

we will wait to see what happens in 3 hours ( pool agreement ).

if its not satisfying.. we will push out one more time.

agreed?

and i will look into the network push message.

so do another update round? ppl dont upgrade.... we have to give time for them to update. Also i want to see what happens now...

cryptsy down again...