[ANN][NTRN] Neutron - New Nucleus wallets released! - Next developments soon!

[kondiomir]

Just reloaded blockchain and synced clean.

If you want guys, I can upload blockchain somewhere...

[TeamNeutron]

Hey guys, here is our developmental update for today.

We have created a fully revamped wallet, with a nice interface. Windows and Mac wallets available for download from the OP. Warning: Do not click wallet download links commented here.

NOTICE: We are still working on a permanent fix for the forks. Please bear with us, we should have another update for you soon.

[digitalgrow]

sweet wallet Dev 

[fonzerrellie]

nice to see some progress by devs, keep it up

[Whitesox]

Just to confirm... The "revamped" link downloads a qt-old wallet, not as such the win logo.

Can someone confirm wich is the correct pls??

TIA

[fil0]

Just to confirm... The "revamped" link downloads a qt-old wallet, not as such the win logo.

Can someone confirm wich is the correct pls??

TIA

New wallet at this link
Windows wallet (Revamped) https://mega.co.nz/#!4wRAzBbZ!K-19wK-aImCWX8jbIBCcPGszTChcj7yL3e6rfbjm12M


New wallet synchronized and working well.

[Whitesox]

Anyone else is getting the same "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers." message on the new "revamped" wallet??

Synced and apparently staking. As problems show after a stake, will wait until then, unless instructed otherwise by devs.

TIA

[The_Prof]

Anyone else is getting the same "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers." message on the new "revamped" wallet??

Synced and apparently staking. As problems show after a stake, will wait until then, unless instructed otherwise by devs.

TIA

Page 29 has the answers you seek.

[CraveIt]

Just to confirm... The "revamped" link downloads a qt-old wallet, not as such the win logo.

Can someone confirm wich is the correct pls??

TIA

New wallet at this link
Windows wallet (Revamped) https://mega.co.nz/#!4wRAzBbZ!K-19wK-aImCWX8jbIBCcPGszTChcj7yL3e6rfbjm12M


New wallet synchronized and working well.

Downloaded the wallet and file is called "Neutron-qt-win-old" why not give us the new wallet? the text is almost impossible to read on the left   

[BigDaddySherman]

Downloaded the wallet and file is called "Neutron-qt-win-old" why not give us the new wallet? the text is almost impossible to read on the left   

this IS the new one no matter the name, but yes, some text labels are hardly readable

Several of us told the dev that this was going to be a problem and suggested he flip the background image. I am just as baffled as you guys.

[Whitesox]

Another update for general info.

After installing the new wallet, although having the checkpoint "issue", I stoke two blocks. As I could see I was "slightly" behind the blockchain, I decided to re start the wallet, and see what happened.

Up to now, it would have run out of synch upon restart, and I'd loose the staked blocks...

Well, the good news is that after restart of the wallet, it run out of synch, staked blocks/coins remain there, but I keep about 40 block BEHIND the blockchain...

Anyone else can back this "experience"?

TIA

[fil0]

Another update for general info.

After installing the new wallet, although having the checkpoint "issue", I stoke two blocks. As I could see I was "slightly" behind the blockchain, I decided to re start the wallet, and see what happened.

Up to now, it would have run out of synch upon restart, and I'd loose the staked blocks...

Well, the good news is that after restart of the wallet, it run out of synch, staked blocks/coins remain there, but I keep about 40 block BEHIND the blockchain...

Anyone else can back this "experience"?

TIA

Yes, I had the same thing earlier, but after removal of all files and restart it normally synchronized wallet and continues stake.
I have now started three wallet on three different computers. One of them is the inscription on the wrong chain of blocks, but they are on the correct chain blocks and are working properly.

[VirtualCloudMining]

To developers

Do you have a higher version for the new wallet and check that nodes have the new wallet?

[CraveIt]

Another update for general info.

After installing the new wallet, although having the checkpoint "issue", I stoke two blocks. As I could see I was "slightly" behind the blockchain, I decided to re start the wallet, and see what happened.

Up to now, it would have run out of synch upon restart, and I'd loose the staked blocks...

Well, the good news is that after restart of the wallet, it run out of synch, staked blocks/coins remain there, but I keep about 40 block BEHIND the blockchain...

Anyone else can back this "experience"?

TIA

yes I am always between 20-30 blocks behind being truly in sync with the chain  I am not sure if this is affecting my staking or not

[BigDaddySherman]

Another update for general info.

After installing the new wallet, although having the checkpoint "issue", I stoke two blocks. As I could see I was "slightly" behind the blockchain, I decided to re start the wallet, and see what happened.

Up to now, it would have run out of synch upon restart, and I'd loose the staked blocks...

Well, the good news is that after restart of the wallet, it run out of synch, staked blocks/coins remain there, but I keep about 40 block BEHIND the blockchain...

Anyone else can back this "experience"?

TIA

yes I am always between 20-30 blocks behind being truly in sync with the chain  I am not sure if this is affecting my staking or not

I'm around 40 ahead of the block explorer - with a net weight of over 80,000 all signs point to the block explorer being on the wrong fork.

[Whitesox]

Another update for general info.

After installing the new wallet, although having the checkpoint "issue", I stoke two blocks. As I could see I was "slightly" behind the blockchain, I decided to re start the wallet, and see what happened.

Up to now, it would have run out of synch upon restart, and I'd loose the staked blocks...

Well, the good news is that after restart of the wallet, it run out of synch, staked blocks/coins remain there, but I keep about 40 block BEHIND the blockchain...

Anyone else can back this "experience"?

TIA

yes I am always between 20-30 blocks behind being truly in sync with the chain  I am not sure if this is affecting my staking or not

I'm around 40 ahead of the block explorer - with a net weight of over 80,000 all signs point to the block explorer being on the wrong fork.

Well, that's a BIG assumption @BigDaddySherman LOL 

[CraveIt]

Another update for general info.

After installing the new wallet, although having the checkpoint "issue", I stoke two blocks. As I could see I was "slightly" behind the blockchain, I decided to re start the wallet, and see what happened.

Up to now, it would have run out of synch upon restart, and I'd loose the staked blocks...

Well, the good news is that after restart of the wallet, it run out of synch, staked blocks/coins remain there, but I keep about 40 block BEHIND the blockchain...

Anyone else can back this "experience"?

TIA

yes I am always between 20-30 blocks behind being truly in sync with the chain  I am not sure if this is affecting my staking or not

I'm around 40 ahead of the block explorer - with a net weight of over 80,000 all signs point to the block explorer being on the wrong fork.

The fork I am on has a network weight of 23926 with the newest wallet released (the green one)

[Whitesox]

as i supposed, for me stake = fork, not always the first but after 3-4 it's doomed.
imho the pos block should be totally rewritten, with more common rules

Yeah, same here... and at all this, we're not counting the blocks lost and the time lost also... thnxs that in the first high valued blocks, this "did not happen"...

It has been mentioned also, to have some words with the lDoge devs as they have been trough "almost" same problems and now are safe and sound...

Devs, any news??? Been a while without any...

[VirtualCloudMining]

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=<ip address>".
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.

[fil0]

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=<ip address>".
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

I confirm that the problem peers.dat of contact with bad nodes, so be sure to remove peers.dat before start wallet. The above-described method of working, I'll use it. Hopefully the developer will soon solve this problem in a new wallet.