[NRS|NoirShares] POW ENDING at 50k | DACs | MANDATORY WALLET UPDATE 6/23/2014

[Kloks]

yes, blockchain reload with old Wallet

1. delete chain, NOT wallet.dat

or just starts the old wallet, then closing immediately.

and then start the new wallet, then runs, too!!

I can confirm thit method works on WinXP 32 bit.
Just exit from the old wallet before it connects to nodes, but after it created needed files in wallet directory.
Sync stucked on last day (about 900 blocks left), but after adding ypool to nodes, sync ended right. Command - addnode.

[fiatpete]

I see I’m not the only one confused by the update. I think I’m updated but help --> about still shows version v0.1.3.0-g99999-Barwiz and qt version 4.8.5.
When I start the gui it’s out of sync and doesn’t show any transactions after the 17th as confirmed so it looks like I've lost half my balance and there is no icon to show how many blocks are downloaded.  When it does sync up I get all the previously confirmed mining transactions confirmed again and the correct balance. The green tick in the bottom left corner to say the blockchain is upto date then appears.
Doing a getpeerinfo and a getinfo in the debug window seems to suggest that I’m updated but the version field in the new release wasn't updated.
getperinfo
"addr" : "x.x.x.x:8500",
"services" : "00000001",
"lastsend" : 1403687424,
"lastrecv" : 1403687259,
"conntime" : 1403687255,
"version" : 60006,
"subver" : "/NoirShares:1.9.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 47595,
"banscore" : 0
},
{
"addr" : "x.x.x.x:8500",
"services" : "00000000",
"lastsend" : 1403687451,
"lastrecv" : 0,
"conntime" : 1403687451,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
getinfo
version" : "v0.1.3.0-g99999-Barwizi",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : x,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 50190,
"moneysupply" : 2374121.37840700,
"connections" : 6,
"proxy" : "",
"ip" : "x.x.x.x",
"difficulty" : 0.00257270,
"testnet" : false,
"keypoololdest" : 1398943972,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"unlocked_until" : 0,
"errors" : "Info: Minting suspended due to locked wallet."

There were other peers with the same details as the first one, I’m guessing the second peer is using an old or corrupted wallet?
This also brings me a suggestion I've made for other coins. Could the client be made to do a simple check to see if any peers are reporting a higher version (subver?) number than its own? So if it does find a peer with a higher version it could prompt the user to check for an updated version of the client.
This would help make sure everyone knows about updated versions as one updated wallet would tell 8 peers which when updated would tell upto 8 other peers and so on...

[crz]

The problem witrh syncing is due to the nodes you are connecting to. This is because others have not updated and continue to use the old wallet which still tries to accept PoW block past the 50k mark.

Please try using the node i have told you since it is on the right version and is not having any sync issues.


As for the wallet crash, i need more details such as error messages, or can you post the last part of your debug.log?

Also, let it run a while, give it time to resolve, as you know there ave been thousands of nodes, so it has to work through them and find the active ones then sort through them to find the correct block number, mine took ~ ten minutes from scratch to sync.

I'm using the node list mario posted now. And already let it run 8 hours, still stuck.

Debug.log

Code:

ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake c8590dfd4d3649fb123a1ad163c120ad10cba9b9d3c1cf3ec7dcd85f3bd2df36, hashProof=5719286d7bdbed2691626cbc3028f4037e26a0329e674fd54ab1730870932507
WARNING: ProcessBlock(): check proof-of-stake failed for block 00031008f03cf6d1c97cbc1102bf316716f99319e8a68e115351bfa9d42c447a
received block 00025dfb06e94d956048
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 70f50cd7d64384e9eb3e48fdaf8d1a3f7928c39ef608c4143321d2099300de3a, hashProof=391072975ad2f4d3c6e8ce16918365a631cb5aa93bcf968b019b7ccc3941df29
WARNING: ProcessBlock(): check proof-of-stake failed for block 00025dfb06e94d956048722f2ee9f134777a7c2009802277bdfad088a3a73ea3
received block 0002d7cf811a5d545900
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 7f1923da6dc5c0d2c98085c4a45305740c7201562e5bbffa6296269aad0eb76d, hashProof=072d4825c8b955a254a616d0388fd5aa46b79d3e816d84937fc612956fb382c9
WARNING: ProcessBlock(): check proof-of-stake failed for block 0002d7cf811a5d545900699801c54c86cd7d245bb1332d0da9b50b56bdb9ea3e
Create Block, 47600
Create Block, 47600
CPUMiner : proof-of-stake block found f49ffcc2a88f9de7903c7cfd37d7983f66a04bbcc8e0a93cb350a53b2d5ea2c5
Create Block, 47600
Create Block, 47600
CPUMiner : proof-of-stake block found fb2f55f81082aa682b5e566bd31d7bab19f869c2e2a6295032cffb99be284142
Create Block, 47600
CPUMiner : proof-of-stake block found 7ad4db8389e25fc2fc3840e68ca5dc9b44e0f1c00cdb47412764cb3cb49bc68f
Create Block, 47600
Create Block, 47600
CPUMiner : proof-of-stake block found a106edd1354fa324c8104b896e6e55a8f46459ee00ea609ebc2fc13f197497da

Code:

CPUMiner : proof-of-stake block found e122a55b7efca4fd0145ce523bd59289ea2d6e990504c19f4148b7d9202cb31c
received block 000105de31a6fe811950
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 7344510ac0b7406b671514cc73a3fc70ec7aa6bdb88d4eeaf46515462534c37c, hashProof=5ceb42e3750e44cbac0e2a4e8af37e0d9fd842c753b78f6d7696161c68c04e0a
WARNING: ProcessBlock(): check proof-of-stake failed for block 000105de31a6fe811950802d56b933f9b9bb111347b0cb83934a828a0265ed80
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found 76f841a2792e6f2f9bf4d4ccd85c46f467d8daf76081e39dbe00d796a1c08ef3
Create Block, 47606
CPUMiner : proof-of-stake block found 9a6def1eec1a91a625c0638f13aa8a28a947d6484c25d3049d6a15a47d105dee
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found c5cd44552698a9efc66030485bbae0adfa3393b60aba37cca534283362b5ee42
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found 6fb9f889fcb09c3a0bd1e5fa7d22abb577fa80d8c7d45d457b9f321f4fefec5c
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found bc04d5df0e1089b50bfc25d3451140864f5e92c81b494ce6ba8dc3bbe3cf7adc
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found eec3d44ba31d66c608dfaeb6e86faa88709a93fed1cfcf02c06729130d519285
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found 33670aedd42b3934470837f516e244e429b18fad2034286fc5b19e21321a0957
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found ad9244c8da94c6054391f85f2284c561467472135aaa20eb8e410d5812933534
Create Block, 47606
CPUMiner : proof-of-stake block found f5f0cde46115a2051fe8aa95ddb0ffdc51893a10387c4164d81941f62dc3e40d
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found 5fc280a19f8947e7caa1bb30d93517ae989aa7db4d377bcd3c169ce017c89e2b
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found 2480d6e1cfc2324aed9cb56b99ab388ba5261ab605e392b577214ee0c0f4743f
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found 7dacb1dce9a9bc80bc07ac81514482aa1de46cfa644c251d4acdf82c1b74f207
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found 089cbe25f183ce51ecd120c0a3483e8e8176b9e6cd2deb80a13e2fd8c563d7f0
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found 4dd7f9bc4584aec2df981c12758132fdb23620d0a391c2b62102c31ed782979a
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found 11331f79e41273c6067e450c3090ae8cc46316db2f2f4f917b072abfb3468a5a
Create Block, 47606
CPUMiner : proof-of-stake block found a602e7225f94cf0977b61d107e6f4229668eee439d4bc031744f0460a410308a
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found 5fbfc01f9e822c3b409df73b9f5f0deda2c6aae12dca5470aa08d5bacdeb0372
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found e29aed61c8b1e6259228f020f60e085a44c3b1ae7b36a84a819d07d790fba3ef
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found f1730945739efbd2aacf5c15c6233953abb8d6201e5441fdefc5e518c570ade0
Create Block, 47606
Create Block, 47606
CPUMiner : proof-of-stake block found ec59aba9edb967c886509ed6c77a6268da3978f47ecee9226b6478951bab35df

UPDATE: It moves one block after pop-up of minted, with stake. But its utterly slow.

[Kloks]

yes, blockchain reload with old Wallet

1. delete chain, NOT wallet.dat

or just starts the old wallet, then closing immediately.

and then start the new wallet, then runs, too!!

I can confirm thit method works on WinXP 32 bit.
Just exit from the old wallet before it connects to nodes, but after it created needed files in wallet directory.
Sync stucked on last day (about 900 blocks left), but after adding ypool to nodes, sync ended right. Command - addnode.

Nope, that method do not work right. After restarting the wallet, it lost some blocks, sync stuck on block 47696. After 3 minutes wallet crashes.

[r05]

The problem witrh syncing is due to the nodes you are connecting to. This is because others have not updated and continue to use the old wallet which still tries to accept PoW block past the 50k mark.

Please try using the node i have told you since it is on the right version and is not having any sync issues.


As for the wallet crash, i need more details such as error messages, or can you post the last part of your debug.log?

Also, let it run a while, give it time to resolve, as you know there ave been thousands of nodes, so it has to work through them and find the active ones then sort through them to find the correct block number, mine took ~ ten minutes from scratch to sync.

We're using Marios nodes. If you have a different set then please post them - searching through ~75 forum pages to find your list isn't a fun task..

[Mario241077]

The problem witrh syncing is due to the nodes you are connecting to. This is because others have not updated and continue to use the old wallet which still tries to accept PoW block past the 50k mark.

Please try using the node i have told you since it is on the right version and is not having any sync issues.


As for the wallet crash, i need more details such as error messages, or can you post the last part of your debug.log?

Also, let it run a while, give it time to resolve, as you know there ave been thousands of nodes, so it has to work through them and find the active ones then sort through them to find the correct block number, mine took ~ ten minutes from scratch to sync.

We're using Marios nodes. If you have a different set then please post them - searching through ~75 forum pages to find your list isn't a fun task..

it's from OP!!!!



6/23 MANDATORY WALLET UPDATE

Source  https://github.com/noirX/NRS

Windows 32/64 Bit Binaries EXE: https://mega.co.nz/#!BUs2gCJC!D6E56cOq3y-KaQKVJSqrYVoNXe-VGdhxi2rnYlTEtTs

Windows 32/64 Bit ZIP https://mega.co.nz/#!oVUDSQYa!mkcSCRAqBUbtyeA1wq8iNSJtvdy38jvMPYfGLF0wwyo

OSX -
Coming soon

Addnode List: http://nrs.argakiig.us/bc_api.php?request=getpeerinfo

[crz]

The problem witrh syncing is due to the nodes you are connecting to. This is because others have not updated and continue to use the old wallet which still tries to accept PoW block past the 50k mark.

Please try using the node i have told you since it is on the right version and is not having any sync issues.


As for the wallet crash, i need more details such as error messages, or can you post the last part of your debug.log?

Also, let it run a while, give it time to resolve, as you know there ave been thousands of nodes, so it has to work through them and find the active ones then sort through them to find the correct block number, mine took ~ ten minutes from scratch to sync.

We're using Marios nodes. If you have a different set then please post them - searching through ~75 forum pages to find your list isn't a fun task..

it's from OP!!!!



6/23 MANDATORY WALLET UPDATE

Source  https://github.com/noirX/NRS

Windows 32/64 Bit Binaries EXE: https://mega.co.nz/#!BUs2gCJC!D6E56cOq3y-KaQKVJSqrYVoNXe-VGdhxi2rnYlTEtTs

Windows 32/64 Bit ZIP https://mega.co.nz/#!oVUDSQYa!mkcSCRAqBUbtyeA1wq8iNSJtvdy38jvMPYfGLF0wwyo

OSX -
Coming soon

Addnode List: http://nrs.argakiig.us/bc_api.php?request=getpeerinfo

Still got this problem, stuck with sync, even with clean start it doesnt load. Waiting for devs reply on this issue.

[r05]

The problem witrh syncing is due to the nodes you are connecting to. This is because others have not updated and continue to use the old wallet which still tries to accept PoW block past the 50k mark.

Please try using the node i have told you since it is on the right version and is not having any sync issues.


As for the wallet crash, i need more details such as error messages, or can you post the last part of your debug.log?

Also, let it run a while, give it time to resolve, as you know there ave been thousands of nodes, so it has to work through them and find the active ones then sort through them to find the correct block number, mine took ~ ten minutes from scratch to sync.

We're using Marios nodes. If you have a different set then please post them - searching through ~75 forum pages to find your list isn't a fun task..

it's from OP!!!!



6/23 MANDATORY WALLET UPDATE

Source  https://github.com/noirX/NRS

Windows 32/64 Bit Binaries EXE: https://mega.co.nz/#!BUs2gCJC!D6E56cOq3y-KaQKVJSqrYVoNXe-VGdhxi2rnYlTEtTs

Windows 32/64 Bit ZIP https://mega.co.nz/#!oVUDSQYa!mkcSCRAqBUbtyeA1wq8iNSJtvdy38jvMPYfGLF0wwyo

OSX -
Coming soon

Addnode List: http://nrs.argakiig.us/bc_api.php?request=getpeerinfo

Still got this problem, stuck with sync, even with clean start it doesnt load. Waiting for devs reply on this issue.

+1. Adding the ypool node doesn't make any difference for me. Wallet is still stuck.

[Mario241077]

but the trouble at the start of the new wallet without chain stays

Mario.. eventually.. I was able to sync, but took some time.. but it got some "trusted" nodes...

I am trying the noirds.com as suggested by barwizi.. and its the same file.. working.. as I stated too... and after 1 minute.. it syncs..

I have all the nodes deleted from my config and the peers.dat. and yes i got the new version then nevertheless a sync

Same problem here:
Using new version,
Deleted peers.dat,
Got 8 connections,
Stuck at blocks" : 47583,
Debug.log ->
Create Block, 47586
ERROR: mempool transaction missing input,
Endless Sync.

please try from scratch with only your wallet.dat

it's taking a while to find nodes on the correct version

you can use the block explorer as a node and i think all the exchanges. ypool as well has updated.

ypool.net it's a post of barwizi our dev

[Anduril_FotW]

new wallet just crashes win8.1 exe or zip...nothing works

Are you still having the same problem? The issue is that some simply have not updated their wallets. Use he block explorer address as the only node and it will sync.

Hi Barwizi,

Can you please explain how I use the block explorer adress as the only node ?
Can I input this somewhere in the client ?

Thanks for your help

[wallace512]

I download the new wallet from here which post by Barwizi

https://drive.google.com/file/d/0BwGL9FkcBurEc21tTk8wMzFZemM/edit?usp=sharing

uninstall the old one, delete everything except noirshares.conf and wallet.dat, install the new one.

everything is working okay for me now.

[patkim]

I installed new wallet and deldeted old one everything looks good but I would like to make sure how can I determine that new wallet is working on new chain?

[Anduril_FotW]

I download the new wallet from here which post by Barwizi

https://drive.google.com/file/d/0BwGL9FkcBurEc21tTk8wMzFZemM/edit?usp=sharing

uninstall the old one, delete everything except noirshares.conf and wallet.dat, install the new one.

everything is working okay for me now.

The problem for me is that this doesn't work (!!!)

If I delete the old client, clear everything in %appdata% except for wallet.dat and then install the new client, the client will not start !
Only after I copy everything back into my %appdata% folder, I can start the client again.
And then I have the same problem again.

Also please give me the command for adding nodes. And what is the syntax ?
Do I just type the following in the debug log:

addnode ["173.236.43.58:39565","66.69.215.216:64946","5.9.158.79:47779","178.125.216.61:63731","107.170.207.147:8500","8.38.76.74:8500","121.185.195.12:8500","14.201.25.59:8500","70.114.143.108:8500","124.168.225.125:50023","59.55.230.181:59019","65.128.192.240:8500","98.250.252.199:8714","88.8.127.16:49448","192.99.144.139:59973","198.101.10.110:8500","75.143.69.254:8500","86.163.25.105:59196","85.243.107.186:51194","211.149.148.150:58600","82.66.239.16:50554","124.231.7.138:6415","178.15.70.226:4178","77.185.64.103:56833","82.127.140.248:63416","83.227.236.11:54676","118.186.153.220:56250","203.173.207.126:59262","64.58.8.35:55490","213.125.187.244:1193","89.99.191.4:6691"]

Or without the brackets ?

Cause if I add this, also nothing happens.

Please help me with this. It's really frustrating.

Thanks

[r05]

I installed new wallet and deldeted old one everything looks good but I would like to make sure how can I determine that new wallet is working on new chain?

Go to the debug console, type "getblockcount" and compare the value with that here: http://nrs.argakiig.us/

[MisO69]

I'm having the same problem, everything was fine yesterday with the new client.

I have it syncing now, here is what I did.

Windows 7 x64 sp1
-deleted everything except wallet.dat, created a new .conf file with the nodes posted a page back. Nodes here: https://bitcointalk.org/index.php?topic=565623.msg7503679#msg7503679
-the new version of NRS just closes on startup, no window opens.
-reboot, try again same thing
-started the old client once, got wallet window, closed before it connected to the network.
-opened new wallet, this time it opened and its syncing now.

I will report back when it completes its sync.

[barwizi]

The problem witrh syncing is due to the nodes you are connecting to. This is because others have not updated and continue to use the old wallet which still tries to accept PoW block past the 50k mark.

Please try using the node i have told you since it is on the right version and is not having any sync issues.


As for the wallet crash, i need more details such as error messages, or can you post the last part of your debug.log?

Also, let it run a while, give it time to resolve, as you know there ave been thousands of nodes, so it has to work through them and find the active ones then sort through them to find the correct block number, mine took ~ ten minutes from scratch to sync.

We're using Marios nodes. If you have a different set then please post them - searching through ~75 forum pages to find your list isn't a fun task..

it's from OP!!!!



6/23 MANDATORY WALLET UPDATE

Source  https://github.com/noirX/NRS

Windows 32/64 Bit Binaries EXE: https://mega.co.nz/#!BUs2gCJC!D6E56cOq3y-KaQKVJSqrYVoNXe-VGdhxi2rnYlTEtTs

Windows 32/64 Bit ZIP https://mega.co.nz/#!oVUDSQYa!mkcSCRAqBUbtyeA1wq8iNSJtvdy38jvMPYfGLF0wwyo

OSX -
Coming soon

Addnode List: http://nrs.argakiig.us/bc_api.php?request=getpeerinfo

Still got this problem, stuck with sync, even with clean start it doesnt load. Waiting for devs reply on this issue.

+1. Adding the ypool node doesn't make any difference for me. Wallet is still stuck.

There seems to be a problem for those starting from block zero. Once i get homw, i will create a new vm and try to recreate your problems.

[barwizi]

I download the new wallet from here which post by Barwizi

https://drive.google.com/file/d/0BwGL9FkcBurEc21tTk8wMzFZemM/edit?usp=sharing

uninstall the old one, delete everything except noirshares.conf and wallet.dat, install the new one.

everything is working okay for me now.

The problem for me is that this doesn't work (!!!)

If I delete the old client, clear everything in %appdata% except for wallet.dat and then install the new client, the client will not start !
Only after I copy everything back into my %appdata% folder, I can start the client again.
And then I have the same problem again.

Also please give me the command for adding nodes. And what is the syntax ?
Do I just type the following in the debug log:

addnode ["173.236.43.58:39565","66.69.215.216:64946","5.9.158.79:47779","178.125.216.61:63731","107.170.207.147:8500","8.38.76.74:8500","121.185.195.12:8500","14.201.25.59:8500","70.114.143.108:8500","124.168.225.125:50023","59.55.230.181:59019","65.128.192.240:8500","98.250.252.199:8714","88.8.127.16:49448","192.99.144.139:59973","198.101.10.110:8500","75.143.69.254:8500","86.163.25.105:59196","85.243.107.186:51194","211.149.148.150:58600","82.66.239.16:50554","124.231.7.138:6415","178.15.70.226:4178","77.185.64.103:56833","82.127.140.248:63416","83.227.236.11:54676","118.186.153.220:56250","203.173.207.126:59262","64.58.8.35:55490","213.125.187.244:1193","89.99.191.4:6691"]

Or without the brackets ?

Cause if I add this, also nothing happens.

Please help me with this. It's really frustrating.

Thanks

Pm me your entire .conf

[wallace512]

I download the new wallet from here which post by Barwizi

https://drive.google.com/file/d/0BwGL9FkcBurEc21tTk8wMzFZemM/edit?usp=sharing

uninstall the old one, delete everything except noirshares.conf and wallet.dat, install the new one.

everything is working okay for me now.

The problem for me is that this doesn't work (!!!)

If I delete the old client, clear everything in %appdata% except for wallet.dat and then install the new client, the client will not start !
Only after I copy everything back into my %appdata% folder, I can start the client again.
And then I have the same problem again.

Also please give me the command for adding nodes. And what is the syntax ?
Do I just type the following in the debug log:

addnode ["173.236.43.58:39565","66.69.215.216:64946","5.9.158.79:47779","178.125.216.61:63731","107.170.207.147:8500","8.38.76.74:8500","121.185.195.12:8500","14.201.25.59:8500","70.114.143.108:8500","124.168.225.125:50023","59.55.230.181:59019","65.128.192.240:8500","98.250.252.199:8714","88.8.127.16:49448","192.99.144.139:59973","198.101.10.110:8500","75.143.69.254:8500","86.163.25.105:59196","85.243.107.186:51194","211.149.148.150:58600","82.66.239.16:50554","124.231.7.138:6415","178.15.70.226:4178","77.185.64.103:56833","82.127.140.248:63416","83.227.236.11:54676","118.186.153.220:56250","203.173.207.126:59262","64.58.8.35:55490","213.125.187.244:1193","89.99.191.4:6691"]

Or without the brackets ?

Cause if I add this, also nothing happens.

Please help me with this. It's really frustrating.

Thanks

add below to your noirshares.conf and see what will happen

addnode=107.170.254.5
addnode= 41.78.77.178
addnode=192.241.213.244
addnode=172.245.183.30
addnode=162.243.131.88
addnode=54.213.71.178
addnode=192.241.213.224
addnode=54.80.61.11
addnode=198.199.96.129
addnode=54.197.175.238

[patkim]

I installed new wallet and deldeted old one everything looks good but I would like to make sure how can I determine that new wallet is working on new chain?

Go to the debug console, type "getblockcount" and compare the value with that here: http://nrs.argakiig.us/

oh nice I have a same blockcount same as you provided link thanks man!

[r05]

I installed new wallet and deldeted old one everything looks good but I would like to make sure how can I determine that new wallet is working on new chain?

Go to the debug console, type "getblockcount" and compare the value with that here: http://nrs.argakiig.us/

oh nice I have a same blockcount same as you provided link thanks man!

No problem dude