Re: [ANN][NTRN] Neutron - Roadmaps fully released!

Quote from: unklo on May 03, 2015, 03:02:38 PM

Quote from: VirtualCloudMining on May 03, 2015, 02:57:23 PM

This works:

Exit neutron wallet program.
Delete everything in data directory (search for %appdata%) except wallet.dat and any "conf"-file.
I you have a "conf"-file edit and remove all "addnode=".
Start neutron wallet again but don't unlock it yet.
Let the wallet synch to the latest block.
Compare the block that the wallet have as the latest with the blockexplorer.
http://neutron.blockview.space/
Save everything in data directory to a new backup directory except wallet.dat, peers.dat and any "conf"-file.

Start staking with the wallet by unlocking it.
When the wallet for some reason isn't synchronised with the latest block according to the block explorer. Delete again in the data directory as stated and copy the data from the backup directory to your data directory which gives a fast synching to the latest block.

I wonder if the new wallet has a higher version number and if it checks that nodes have the new wallet.

it doesn't check obviously.

and a lil easier advice to everybody: always delete peers.dat after you close the wallet.

that way next launch you'll feed it from seednode and not some shitnodes

Actually it does check.

https://github.com/teamneutron/Neutron/blob/master/src/version.h#L39

The problem is that this dynamic staking code that came out of Tron is broken/not implemented correctly. I am surprised Tron has not started having issues yet.

Check it out:
https://github.com/teamneutron/Neutron/blob/master/src/main.cpp#L1036

Do you see the problem in that code? It is checking the block height against pindexBest, which is a pointer to the tip of the chain. But that varies as you sync. If you get a bunch of other block inventory for your node to check, its always going to be trying to assign a reward based on what it thinks the tip of the chain is, not the relative height of a particular block.