Topic: [RE-ANN] GrowthCoin PoW/PoS - 100% per year - Version 1.3.0.1 - page 41. (Read 66388 times)

updated OP with development support address.  This address would be used to support server costs and bounties.

https://bitcointalksearch.org/topic/m.7158566

If you want to support GRW, this is where you should send some coins

UPDATE: I did get a stake with the latest build. it took just under 9 days.

On a side note, it always took around midway to max stake weight to get a valid PoS block with GRW. So I'd say you should have yours in around 2 days from now.

I guess you are right. I get stuck generating PoS blocks, and maybe I am too impatient to allow them to reorganize. The problem is that sometimes I lost the connection (have 0 connected nodes) and I keep generating PoS blocks. I will try to wait a little longer and see what happens.

This is new, I haven't got stuck on a fork since adding the checkpointing node.

Have you tried just to let your client do it's thing? When generating PoS blocks, they still have to be accepted by the network, so what you refer to as a fork might just be that those blocks were not all confirmed and a better block was accepted instead of yours.  If you let the client go, it should reorganize by itself and clean get back on the right fork.

repairwallet won't get you back on the correct fork. All it does is repair your wallet by removing orphans and fixing mismatched coins (transactions no accepted by the network but marked as spent in your wallet) so this steps has no influence over you getting back on the right fork.

The connection timeout issue is something I haven't had time to dig deeper in. but likely not an issue for what you are describing.  And reserve balance is only used to mark a certain amount has not available for minting.

So I really suspect that what you refer to as forking is just orphaned blocks and should normally be fixed by itself. The other thing that might be happening, is that if you generate PoS block BEFORE being fully synced to the network, you might indeed get stuck on a fork.  I'll try to get that fixed for the next release. the quick fix for that is to start your client with -reservebalance=99999999

I had to lanch the program with reservebalance=987654321, attending it synch and then make a reservebalance false on console..
It generates lot of POS blocks, but no one are accepted by network so far.

I have successfully staked with the lastest build of the daemon.

But I'm continously forking. I have to stop the daemon, restart with -reservebalance=999999, repairwallet to remove orphans and return to the correct fork and then restart the daemon. Sometimes I cannot connect to any peer since they close the connections: they say closed socket or connection timeout.

No, I always used the Qt GUI for PoS and the daemon for PoW. But I don't see why it shouldn't work either way

Have you also had success staking with the daemon rather than the Qt gui?

No I haven't yet staked with the latest build, but I wouldn't be worried yet.
It seems to take around 8 days of age to get stakes with GRW.  I have a few mature blocks myself of about 8 days, I'll let you know if/when I get mine

Unick have you been successfully staking with the current version of the repo?  I built the daemon a few days ago and have coins that are about 7 days old or so and haven't staked yet.  Does this seem normal for GRW?

Here is my address: http://grw.blockx.info/get/address/GdrRRgpDkhtxMcJFa8uor6wihn5TcnJkp1

excellent!

Difficulty did rise but MH/s has fallen to about 650 MH/s

this is because difficulty is adjusting when a lot of PoS blocks are found on the network. It tries to keep inflation as low as possible.

So far things are looking pretty good

Difficulty is now at 15.31216744!

Things are looking good



823 MH/s. This is the most hashing power I've seen since the resurrection of Growth!

Excellent news for the network

You could try to start the client with the -rescan switch.

If that doesn't do it. delete blkindex.dat and peers.dat and try again

Yes I did. Should I delete everything in my APPDATA/Roaming folder? Except my wallet.dat of course 

517286 is a 10 days old block, most likely you ended up on a fork. did you try to restart your client ?

I seem to be unable to sync. Is anyone else stuck on block 517286?

Many, some of them has no activity since 2013.

I wonder too. You seem to have often corrupted index. If you can provide more info as what step to reproduce the error, that would be helpful