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

[The_Prof]

Yeah, the network is constantly forking.  Reminds me of litedoge, which had the same issue when it reached the stage of smoothly, slowly decreasing block rewards.  It's broken code that originated in spreadcoin I believe.

I'm not a competent coder by any means, but I'd take a look at litedoge if I were the NTRN devs.  I'd bet whatever fix they implemented would be the solution here.

OK, so after many resyncs the problem I found is the nodes. Don't add them into the config. That list of nodes to use is causing a problem. Rather remove the config and let the wallet find it's own nodes and update.
My wallet has been online for 2 hours without a hassle and settles on 4 active connections. So lets try this list:

1. Lock the wallet
2. Delete all except wallet.dat - Make sure that is the only file in the folder. NO CONFIGS
3. Open QT and let the blockchain sync completely
4. Unlock wallet after 15 mins - check it is matching the block explorer during this time.


Edit:
At present I am trying a config with the following to see if it helps.

rpcuser=username
rpcpassword=passowrd
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1

I cannot say yet if it will make a difference as I have not staked a block since I have done this.

[fil0]

Earlier, I wrote that the wallet is operating normally with a warning sign on the wrong chain of blocks. But then the blocks in the wallets and the site began to differ. In this situation, you just need to remove all but wallet.dat and restart the wallet.

Video repair wallet http://youtu.be/4iLgPLlG0Ww

[Whitesox]

Earlier, I wrote that the wallet is operating normally with a warning sign on the wrong chain of blocks. But then the blocks in the wallets and the site began to differ. In this situation, you just need to remove all but wallet.dat and restart the wallet.

Video repair wallet http://youtu.be/4iLgPLlG0Ww

Earlier, I wrote that I was in synch and staking... and in accordance with block explorer...

Now, again, I write the same... Don't know why you keep giving info that might only be related to you, as general rule of thumb...

I'm in synch with the block explorer, I'm staking and I've got the error mentioned above...

Please DEVS (not anyone else), look into it and let's get it all moving smoothly...

Thanks!!

[The_Prof]

Earlier, I wrote that the wallet is operating normally with a warning sign on the wrong chain of blocks. But then the blocks in the wallets and the site began to differ. In this situation, you just need to remove all but wallet.dat and restart the wallet.

Video repair wallet http://youtu.be/4iLgPLlG0Ww

Yes we can all read. The point is trying to work a way to not have to re-download the blockchain 3 times a day or more.

[SockPuppetAccount]

I've done all of this stuff guys.  It still forks constantly.  Someone who is more knowledgeable than me, please look into litedoge and what they did.  This is EXACTLY the same problem in EXACTLY the same situation.

[CoHPa3yMa]

Problems have arisen with the wallet two days ago, threaten the future of the coin. We need a new Wallet, not screenshots roadmap.

[BTC-BTC-BTC]

I deleted everything and re-downloaded blockchain four times and still not working. New wallet is needed it.

[fil0]

I have re-downloaded four times and still not working. New wallet is needed it.

Have you removed all but the wallet.dat  from the catalog  AppData\Roaming\Neutron or catalog dir(if you use this https://yadi.sk/d/QCTF88uQgMjr6 ) before launch a wallet?
It does not work like? Do not synchronized, it stops at some block? Or wallet is synchronized to the wrong chain of blocks other than this http://neutron.blockview.space/?
What exactly does not work?

[SockPuppetAccount]

I have re-downloaded four times and still not working. New wallet is needed it.

Have you removed all but the wallet.dat  from the catalog  AppData\Roaming\Neutron or catalog dir(if you use this https://yadi.sk/d/QCTF88uQgMjr6 ) before launch a wallet?

YES!!!!  WE ARE NOT COMPLETE IMBECILES!!  SOMETHING ELSE IS WRONG!!

What exactly does not work?

We get synced up for a small period of time, and then we fork.

[Qbanow]

After you synchronized everything you have to run a repairwallet command.

[BTC-BTC-BTC]

I have re-downloaded four times and still not working. New wallet is needed it.

Have you removed all but the wallet.dat  from the catalog  AppData\Roaming\Neutron or catalog dir(if you use this https://yadi.sk/d/QCTF88uQgMjr6 ) before launch a wallet?

YES!!!!  WE ARE NOT COMPLETE IMBECILES!!  SOMETHING ELSE IS WRONG!!

What exactly does not work?

We get synced up for a small period of time, and then we fork.

The first time i deleted everything I got synced up and mined 11 blocks on 5/1 then forked again. The last three time didn't get synced up like 50 blocks off the latest block on the explorer. Anyway I am not going to try anymore until some is new.

Thanks,

[fil0]

I have re-downloaded four times and still not working. New wallet is needed it.

Have you removed all but the wallet.dat  from the catalog  AppData\Roaming\Neutron or catalog dir(if you use this https://yadi.sk/d/QCTF88uQgMjr6 ) before launch a wallet?

YES!!!!  WE ARE NOT COMPLETE IMBECILES!!  SOMETHING ELSE IS WRONG!!

What exactly does not work?

We get synced up for a small period of time, and then we fork.

The first time i deleted everything I got synced up and mined 11 blocks on 5/1 then forked again. The last three time didn't get synced up like 50 blocks off the latest block on the explorer. Anyway I am not going to try anymore until some is new.

Thanks,

Strangely, my wallet once went on the wrong chain of which I have recorded a video repair wallet.
After that, he was 4 hours it works fine and I have 12 connections.
I think you need to wait a dev, he must help solve the problem. He wrote that we will be able to download the first update afternoon.

[VirtualCloudMining]

Yeah, the network is constantly forking.  Reminds me of litedoge, which had the same issue when it reached the stage of smoothly, slowly decreasing block rewards.  It's broken code that originated in spreadcoin I believe.

I'm not a competent coder by any means, but I'd take a look at litedoge if I were the NTRN devs.  I'd bet whatever fix they implemented would be the solution here.

OK, so after many resyncs the problem I found is the nodes. Don't add them into the config. That list of nodes to use is causing a problem. Rather remove the config and let the wallet find it's own nodes and update.
My wallet has been online for 2 hours without a hassle and settles on 4 active connections. So lets try this list:

1. Lock the wallet
2. Delete all except wallet.dat - Make sure that is the only file in the folder. NO CONFIGS
3. Open QT and let the blockchain sync completely
4. Unlock wallet after 15 mins - check it is matching the block explorer during this time.


Edit:
At present I am trying a config with the following to see if it helps.

rpcuser=username
rpcpassword=passowrd
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1

I cannot say yet if it will make a difference as I have not staked a block since I have done this.

After deletning the old blockchain from the data directory and removing "addnodes" from the "conf"-file the staking have worked flawlessly for over seven hours.
It seems you should not have nodes from the first page of this thread in the "conf"-file.

[GreenDefender]

@ dev. Where can i find actual right block number ? (Got this WARNING at my wallet)

[fil0]

@ dev. Where can i find actual right block number ? (Got this WARNING at my wallet)

Use this http://neutron.blockview.space/chains

[GreenDefender]

@ dev. Where can i find actual right block number ? (Got this WARNING at my wallet)

Use this http://neutron.blockview.space/chains

thx a lot http://neutron.blockview.space/ has same block number like my wallet. Network weight is only 17612 !?

[fil0]

I updated the archive to the 16414 block. The quickest way to return to the correct chain of blocks:
1) Download synchronized wallet https://yadi.sk/d/QCTF88uQgMjr6
2) Copy your wallet.dat in  "dir"
3) Run the run.bat

[glen123]

@All :

Calm down and wait for revamped wallet .
Dev will soon release it.

[Whitesox]

Just for general info, and I'm not 100% I'm NOT forked, but still in synch with block explorer @16465 and network weight is 13350 and staking.

Waiting for Dev's news...

[The_Prof]

Yeah, the network is constantly forking.  Reminds me of litedoge, which had the same issue when it reached the stage of smoothly, slowly decreasing block rewards.  It's broken code that originated in spreadcoin I believe.

I'm not a competent coder by any means, but I'd take a look at litedoge if I were the NTRN devs.  I'd bet whatever fix they implemented would be the solution here.

OK, so after many resyncs the problem I found is the nodes. Don't add them into the config. That list of nodes to use is causing a problem. Rather remove the config and let the wallet find it's own nodes and update.
My wallet has been online for 2 hours without a hassle and settles on 4 active connections. So lets try this list:

1. Lock the wallet
2. Delete all except wallet.dat - Make sure that is the only file in the folder. NO CONFIGS
3. Open QT and let the blockchain sync completely
4. Unlock wallet after 15 mins - check it is matching the block explorer during this time.


Edit:
At present I am trying a config with the following to see if it helps.

rpcuser=username
rpcpassword=passowrd
rpcallowip=127.0.0.1
listen=1
server=1
daemon=1

I cannot say yet if it will make a difference as I have not staked a block since I have done this.

After deletning the old blockchain from the data directory and removing "addnodes" from the "conf"-file the staking have worked flawlessly for over seven hours.
It seems you should not have nodes from the first page of this thread in the "conf"-file.

It screwed up for me as well. 7 Hours is almost bang on the money. Get a few stake blocks perfectly then it screws out. It was the best make shift I could offer. I will keep on this route so I can stake at least otherwise it's pointless having the wallet online. My view is it's due to other people still holding onto the nodes with the config. The moment the route is clear it might help.

Till then...