[ANN][LEAF] LEAFCOIN - Android wallet launched

[mcg]

would you be able to push a network message to all wallets ?

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.

[C3ALL]

Cant roll out another update before people have even done this one.  It will just get confusing with the number of updates being pushed out, some exchanges may even get sick of all the updates and drop the coin.

There will be a period of time when the diff swings slow the coin for a while, but long term it will resolve the issues.  So, people taking the short term view may get burned, people taking the long term view may see rewards.  Thats my opinion, but just as long as there remains enough support to pull this through the next high diff after the next multipool jump in.

People can see when gravity is coming, so as long as there are enough people keeping a bit of hash rate pointed at the coin, all will work out eventually.  Pushing out too many updates has just as much pottential to kill a coin as the multipools.

[stevenb]

would you be able to push a network message to all wallets ?

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

but we will wait to see what happens in 3 hours.

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

agreed?

and i will look into the network push message.

Totally agree, let's wait for next diff and decide Dev. But please implement before block 18240 (next re-target at 18000 and 18240).

[C3ALL]

Totally agree, let's wait for next diff and decide Dev. But please implement before block 18240 (next re-target at 18000 and 18240).

Even if middlecoin doesnt join in, the other locusts will.  As soon as we hit block 18,000 when the multipools join back in, it could hit 18,240 within 40 minutes.   Last time the multipools joined in at a low diff (and it wasnt even this low) there was a block every 10 seconds.  This time it could be even quicker.   No way at all to get an update out before 18240 it would fork for sure.

[mcg]

would you be able to push a network message to all wallets ?

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

but we will wait to see what happens in 3 hours.

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

agreed?

and i will look into the network push message.

Totally agree, let's wait for next diff and decide Dev. But please implement before block 18240 (next re-target at 18000 and 18240).

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

[luke997]

would you be able to push a network message to all wallets ?

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

but we will wait to see what happens in 3 hours.

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

agreed?

and i will look into the network push message.

Totally agree, let's wait for next diff and decide Dev. But please implement before block 18240 (next re-target at 18000 and 18240).

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.

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.

i dont think we should do that.

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

Totally agree, let's wait for next diff and decide Dev. But please implement before block 18240 (next re-target at 18000 and 18240).

Even if middlecoin doesnt join in, the other locusts will.  As soon as we hit block 18,000 when the multipools join back in, it could hit 18,240 within 40 minutes.   Last time the multipools joined in at a low diff (and it wasnt even this low) there was a block every 10 seconds.  This time it could be even quicker.   No way at all to get an update out before 18240 it would fork for sure.

If you take the average 600 MGhash until the next gravity well is done, you get ~ 18 days until we reach the block 21203 - and the swing might (and probably willl) get worse.

How about block 18720?

That gives ~3 days  of 1 slow block and 2 faster blocks, so could be min 2.5 days (if hash jumps - which I doubt) or 3.5 if it slows slightly.

[mcg]

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

[mcg]

Cant roll out another update before people have even done this one.  It will just get confusing with the number of updates being pushed out, some exchanges may even get sick of all the updates and drop the coin.

There will be a period of time when the diff swings slow the coin for a while, but long term it will resolve the issues.  So, people taking the short term view may get burned, people taking the long term view may see rewards.  Thats my opinion, but just as long as there remains enough support to pull this through the next high diff after the next multipool jump in.

People can see when gravity is coming, so as long as there are enough people keeping a bit of hash rate pointed at the coin, all will work out eventually.  Pushing out too many updates has just as much pottential to kill a coin as the multipools.

i agree with this as well.

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

if there is no other way.

[whoiis]

we don't need more hash once retarget takes place
we need it once gravity has taken effect

[mcg]

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.

[whoiis]

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.

better reward ppl that are hammering through those last 10 shitty blocks

[luke997]

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.

That's brilliant idea, this I think is the way if we go with gravity 3 after next easy set of blocks.

So I see it that way:

1) Check the diff swing on the next set of blocks

2) If swings, rollout quickest gravity 3 update

3) Encourage upgrade by giveaway

4) Announce giveaway on 1/2 pools for people who mine the last hard block before gravity.

[damnation]

On a side note.. check out the time taken to find one block.
17980    109 left    anonymous    07/02 10:07:53        
17979    108 left    *********   07/02 08:43:13

though the average runs to about 15-20 minutes a block..

[mcg]

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.

That's brilliant idea, this I think is the way if we go with gravity 3 after next easy set of blocks.

So I see it that way:

1) Check the diff swing on the next set of blocks

2) If swings, rollout quickest gravity 3 update

3) Encourage upgrade by giveaway

4) Announce giveaway on 1/2 pools for people who mine the last hard block before gravity.

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.

[terracide]

Never rush these things... a fork will really do much more damage to the coin then an extra few days.

[mcg]

Never rush these things... a fork will really do much more damage to the coin then an extra few days.

agree, thats why we set the block to 21203.

[luke997]

Never rush these things... a fork will really do much more damage to the coin then an extra few days.

We'll see the diff after the easy block, calculate to take the weekend into account - as the dev rightly noticed - so that the update lands monday/tuesday ?

I'm in it for the long haul anyway, Leaf a has a bright future.

[mcg]

Never rush these things... a fork will really do much more damage to the coin then an extra few days.

We'll see the diff after the easy block, calculate to take the weekend into account - as the dev rightly noticed - so that the update lands monday/tuesday ?

I'm in it for the long haul anyway, Leaf a has a bright future.

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,...

[ancientnoob]

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.

That's brilliant idea, this I think is the way if we go with gravity 3 after next easy set of blocks.

So I see it that way:

1) Check the diff swing on the next set of blocks

2) If swings, rollout quickest gravity 3 update

3) Encourage upgrade by giveaway

4) Announce giveaway on 1/2 pools for people who mine the last hard block before gravity.

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.

I just started learning about this stuff.........actually most of what I've learned has been through reading this. Figured out the impostors and ones that are just looking to make some cash. I've also seen tremendous support and a dev team that is in it for the right reasons.

I've been mining this from day one, I think I have my rig tuned (crossing fingers that it doesn't turn off on me again), and I've pointed my small little 3mhs at MajorMiner trying to do my part getting past the 51% attacks and now the cow wars.

I've done this on nothing but the faith I've gained by being a part of this community, I believe in leaf and what can be.
Patience is a virtue and IMHO we should practice it to protect this coin. I know there's a fine line of dedicated support and a wilting away. Please whatever you all do when giving so freely of your advice, think of the larger picture.

Just hearing about "forking" scares me and I'm not sure what it really is. I'll learn but right now I don't know and "mcg" seems to understand that can be the death of this thing.

..........."mcg", "aaron_m", "sakkosekk", "virtualdn","Pattes" (the cheerleader), and many others have been a calm during the trials and tribulations of this new start-up. People have worked soooooooooo hard to make this happen and work through the glitches.

Please don't do something that would bring harm to a good thing because of negativity on others part (greed and impatience come to mind).

I've been here from the start and it was blind luck. I'll be here while they get this fixed too, supporting in my small way. Most of all I want to thank all of you for giving me and education. I still don't know much, but I know a lot more than I did a few weeks ago.................it's from you all, both positive and negative, that I've learned.

Thanks for letting me ramble................hope it helps someone sort through it all.

[terracide]

@ancientnoob....  devs are really skilled of this coin. Nothing to worry about. The "Cheerleaders" are good too i guess