looking for owners of these ips, pm if owner

195.154.178.118:22813
5.53.195.10:22813
65.111.164.219:22813
162.243.98.174:22813
115.29.148.13:22813
115.28.138.147:22813
103.21.143.11:22813
37.187.56.220:22813

can everyone who has an open port 22813, pm me... so who is a node on the net for leafcoin.

should be +/- 8 nodes.

4 i already know.

that is the idea yes.

this coin is very new.

fixes are implemented almost immediately

( but we need time for everyone to update.. we scheduled for 10-14 days. if we would hit, for whatever reason, 60secs again.. we at least have 7 days... ).

we will try to keep up the good work

fri,sat, sun... we will be developing the platform.

we cannot push another update now....

i asked certain ppl how long they would take.... recommend.

10 days.

also we need everyone to update to prevent a fork.

cryptsy is possible the slowest factor in this update.

so this is why we extended the time.

if you read back you see that i offered to update in 3 days.

ppl said it was to short and we could have risk of fork when too short.

i have messaged the mac osx compiler.

if its not done in a few days, i will do it myself.

note that for the next week you will not have a problem using the old wallet.

cheers.

yes but thats why the multipools keep dropping in...

i need everyone to update the software.

see op post for details.

some of you have received a private pm.

most of these are pool owners, game implementors and so on.

ok.. thats it. back to coinmarket.io

40 days is very exagerated.... top 14 days.

upgrade your windows wallets pls.

gravity update is being pushed out.

@block 29300 it will come into effect

that would allow more then enough time to update.

@ 1 minute blocks this would mean 8 days for everyone to update.

i will be rebuilding the binaries.

source is already on github

when binaries have been built it will be announced through all channels.

agree... think it will be between 7 and 10 days.

i know... we cant push it out today and have the fix running tomorrow. that is asking for trouble.

yes update is really needed.

and its ready.

we need to prevent fork... thats why we havent pushed out yet.

we have calculated when the diff is low and when high ( one targetspan multipools on, one targetspan off ( high diff ), etc )... and taken into account 4 days ( its not exact, more or less )...
we need cryptsy to update the wallet. Sometimes they respond quickly, sometimes they dont... i have announced it to them and asked them how long it would take for them, in working days, to update.

When we have received the response we will recalculate the block number for fix.

If we do it too soon... everyone needs to be in a hurry and things can go terribly wrong ( fork ).

23640 is between 3 and 4 days.

I am awaiting their answer... i contacted them in 3 ways.

oke will do... hope to have answer soon

i am currently contacting them... i can extend it to 27960... agreed?

yes its getting very annoying... soon it is over.

update going to be pushed out soon now... standby.

we will apply these changes @ block number 23640

did you confirm email? and yes, sending to cryptsy is slow atm

just to answer this... we need to give clients time to update...

small update times can cause a fork... we need cryptsy to update.. that might not go as fast as we wish.

so vote smart

also take the upcoming weekend into account