Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 378. (Read 782375 times)
August 10, 2016, 04:48:25 PM
had a thought about that 60k that is to be burnt. why not use it to pay of coinpayments so we can get added?
August 10, 2016, 04:13:46 PM
Thanks. I hope the devs sort this mess out soon. 
August 10, 2016, 04:10:24 PM
How do we know which is the good chain?
Is there a solid reference of a good chain to compare with all the time?
My masternodes are stuck on various blocks while my controller wallet has a much higher block number.
But the MN info site has an even higher number! I'm getting really confused.
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
Is there a solid reference of a good chain to compare with all the time?
My masternodes are stuck on various blocks while my controller wallet has a much higher block number.
But the MN info site has an even higher number! I'm getting really confused.
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
basically everythings knackered and we will probably be starting back at pos switch over again once its fixed.
i just trying sync one again with only 2.0.1 peers as addnodes here is my list of them
addnode=72.49.184.206
addnode=68.227.30.210
addnode=74.118.192.18
addnode=68.227.23.166
addnode=138.68.50.249
addnode=173.245.157.244
addnode=173.245.158.8
addnode=coin-server.com
addnode=164.132.176.111
addnode=54.183.10.48
addnode=192.241.217.126
addnode=37.59.209.79
addnode=162.220.55.207
addnode=192.241.217.126
addnode=164.132.189.211
addnode=162.220.55.207
addnode=104.236.183.29
addnode=37.59.209.67
addnode=37.59.209.122
addnode=192.99.217.99
addnode=164.132.237.216
August 10, 2016, 03:54:49 PM
How do we know which is the good chain?
Is there a solid reference of a good chain to compare with all the time?
My masternodes are stuck on various blocks while my controller wallet has a much higher block number.
But the MN info site has an even higher number! I'm getting really confused.
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
Is there a solid reference of a good chain to compare with all the time?
My masternodes are stuck on various blocks while my controller wallet has a much higher block number.
But the MN info site has an even higher number! I'm getting really confused.
http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html
August 10, 2016, 03:40:45 PM
I'm on block 260419 now - hopefully this is the correct chain?
getblockhash 260419
f36d30cbfc9424f76f1c04f2cf24ca5be6ae60394e3ed2ce977313bcdf6856f5
getblockhash 260419
f36d30cbfc9424f76f1c04f2cf24ca5be6ae60394e3ed2ce977313bcdf6856f5
Well past that one by now so no.
August 10, 2016, 03:26:45 PM
I'm on block 260419 now - hopefully this is the correct chain?
getblockhash 260419
f36d30cbfc9424f76f1c04f2cf24ca5be6ae60394e3ed2ce977313bcdf6856f5
getblockhash 260419
f36d30cbfc9424f76f1c04f2cf24ca5be6ae60394e3ed2ce977313bcdf6856f5
August 10, 2016, 02:28:04 PM
i made something wrong...my wallet.dat is corrupted same in the backup folder...cant salvagewallet and other commands...nothing working...coins gone i give up...
You probably have a backups folder in DarkNet with a few wallet files which you can use.
August 10, 2016, 01:57:07 PM
Hopefully getting there... In case someone wants to compare or tell me I am on the wrong chain...
Code:
$ darknet-cli getblockhash 260200
c6e2324f5baf1b8dfcc5feee9d2eb6db3481136da78b287b1b2c44ff68932e12
$ darknet-cli getblockhash 260209
c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4
$ darknet-cli getblockhash 260250
427e740be5d6db1820d8d525211a032995f489c5ddad9b8a330de5aae74b1018
$ darknet-cli getblockhash 260300
e7de292ba59b816dd22b47a075b9553161d9782fab1ac55a90f4a4f20f2ef023
$ darknet-cli getblockhash 260350
fbf52102b5212406acb7a03f96accf53309b4bb4c59e09eeab41d3f15c1a86da
$ darknet-cli getblockhash 260391
caeb312a35155ff60bc9751b402cb13180139d05676382282fc09da35fcdce50
c6e2324f5baf1b8dfcc5feee9d2eb6db3481136da78b287b1b2c44ff68932e12
$ darknet-cli getblockhash 260209
c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4
$ darknet-cli getblockhash 260250
427e740be5d6db1820d8d525211a032995f489c5ddad9b8a330de5aae74b1018
$ darknet-cli getblockhash 260300
e7de292ba59b816dd22b47a075b9553161d9782fab1ac55a90f4a4f20f2ef023
$ darknet-cli getblockhash 260350
fbf52102b5212406acb7a03f96accf53309b4bb4c59e09eeab41d3f15c1a86da
$ darknet-cli getblockhash 260391
caeb312a35155ff60bc9751b402cb13180139d05676382282fc09da35fcdce50
All on the wrong one. Would just ignore it till they fix it with new exe that this time will hopefully work. They need enable the masternode lock as well to stop us connecting to all the ones not updated.
Thanks! Will just note I compiled from the latest commit: 9c46858, deleted everything except conf files, and restored a blockchain from before 70200 version masternodes and used the recommended peers from an earlier post.
If we have an official or authoritative chain, it would be nice if someone could post hashes of block ending in 00 and perhaps blocks where people are getting stuck.
August 10, 2016, 01:54:49 PM
11:55:01

getblockhash 260635
11:55:01

3442c235d521c637985ad71893f2c3744780928f7705404d00550c15c5ead769
Could you please share some of the nodes that you're connecting to? I'm stuck on block 260584.
Quote
addnode=108.61.151.69
addnode=173.245.158.8
addnode=coin-server.com
addnode=185.86.151.173
addnode=185.86.149.212
addnode=dnetxef3rmouy5qo.onion:989
addnode=dnetxcvx4iqeunnk.onion:989
addnode=dnetxn4m5kfh4xhr.onion:989
addnode=dnetxu5edp35e4rm.onion:989
addnode=y5kcscnhpygvvnjn.onion:989
addnode=5bmhtjvn2jvwpiej.onion:989
addnode=pyfdxkazur3iib7y.onion:989
addnode=ok3ym5zy6m5klimk.onion:989
addnode=i6vpvzk2jxuqqs5f.onion:989
addnode=bgdhpb76fkbw5fmg.onion:989
addnode=gtlqzb5zbws5di7g.onion:989
addnode=f7j2m26rptm5f7af.onion:989
addnode=dnetzj6l4cvo2fxy.onion:989
addnode=s3v3n7xhqafg6sb7.onion:989
addnode=173.245.158.8
addnode=coin-server.com
addnode=185.86.151.173
addnode=185.86.149.212
addnode=dnetxef3rmouy5qo.onion:989
addnode=dnetxcvx4iqeunnk.onion:989
addnode=dnetxn4m5kfh4xhr.onion:989
addnode=dnetxu5edp35e4rm.onion:989
addnode=y5kcscnhpygvvnjn.onion:989
addnode=5bmhtjvn2jvwpiej.onion:989
addnode=pyfdxkazur3iib7y.onion:989
addnode=ok3ym5zy6m5klimk.onion:989
addnode=i6vpvzk2jxuqqs5f.onion:989
addnode=bgdhpb76fkbw5fmg.onion:989
addnode=gtlqzb5zbws5di7g.onion:989
addnode=f7j2m26rptm5f7af.onion:989
addnode=dnetzj6l4cvo2fxy.onion:989
addnode=s3v3n7xhqafg6sb7.onion:989
With only the nodes thata appear in Ops in this moment.
Thanks for nodes, but they don't get me past 259200, unfortunately.
August 10, 2016, 01:18:26 PM
Hopefully getting there... In case someone wants to compare or tell me I am on the wrong chain...
Code:
$ darknet-cli getblockhash 260200
c6e2324f5baf1b8dfcc5feee9d2eb6db3481136da78b287b1b2c44ff68932e12
$ darknet-cli getblockhash 260209
c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4
$ darknet-cli getblockhash 260250
427e740be5d6db1820d8d525211a032995f489c5ddad9b8a330de5aae74b1018
$ darknet-cli getblockhash 260300
e7de292ba59b816dd22b47a075b9553161d9782fab1ac55a90f4a4f20f2ef023
$ darknet-cli getblockhash 260350
fbf52102b5212406acb7a03f96accf53309b4bb4c59e09eeab41d3f15c1a86da
$ darknet-cli getblockhash 260391
caeb312a35155ff60bc9751b402cb13180139d05676382282fc09da35fcdce50
c6e2324f5baf1b8dfcc5feee9d2eb6db3481136da78b287b1b2c44ff68932e12
$ darknet-cli getblockhash 260209
c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4
$ darknet-cli getblockhash 260250
427e740be5d6db1820d8d525211a032995f489c5ddad9b8a330de5aae74b1018
$ darknet-cli getblockhash 260300
e7de292ba59b816dd22b47a075b9553161d9782fab1ac55a90f4a4f20f2ef023
$ darknet-cli getblockhash 260350
fbf52102b5212406acb7a03f96accf53309b4bb4c59e09eeab41d3f15c1a86da
$ darknet-cli getblockhash 260391
caeb312a35155ff60bc9751b402cb13180139d05676382282fc09da35fcdce50
All on the wrong one. Would just ignore it till they fix it with new exe that this time will hopefully work. They need enable the masternode lock as well to stop us connecting to all the ones not updated.
August 10, 2016, 01:02:08 PM
Hopefully getting there... In case someone wants to compare or tell me I am on the wrong chain...
Code:
$ darknet-cli getblockhash 260200
c6e2324f5baf1b8dfcc5feee9d2eb6db3481136da78b287b1b2c44ff68932e12
$ darknet-cli getblockhash 260209
c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4
$ darknet-cli getblockhash 260250
427e740be5d6db1820d8d525211a032995f489c5ddad9b8a330de5aae74b1018
$ darknet-cli getblockhash 260300
e7de292ba59b816dd22b47a075b9553161d9782fab1ac55a90f4a4f20f2ef023
$ darknet-cli getblockhash 260350
fbf52102b5212406acb7a03f96accf53309b4bb4c59e09eeab41d3f15c1a86da
$ darknet-cli getblockhash 260391
caeb312a35155ff60bc9751b402cb13180139d05676382282fc09da35fcdce50
c6e2324f5baf1b8dfcc5feee9d2eb6db3481136da78b287b1b2c44ff68932e12
$ darknet-cli getblockhash 260209
c1a37179151fd5f44d08d06805e4d4087341eacdf5aaaef2553c69fca29c21d4
$ darknet-cli getblockhash 260250
427e740be5d6db1820d8d525211a032995f489c5ddad9b8a330de5aae74b1018
$ darknet-cli getblockhash 260300
e7de292ba59b816dd22b47a075b9553161d9782fab1ac55a90f4a4f20f2ef023
$ darknet-cli getblockhash 260350
fbf52102b5212406acb7a03f96accf53309b4bb4c59e09eeab41d3f15c1a86da
$ darknet-cli getblockhash 260391
caeb312a35155ff60bc9751b402cb13180139d05676382282fc09da35fcdce50
August 10, 2016, 12:25:07 PM
12:22:03

getblockhash 260658
12:22:03

c23a2b54bf64a86e7ccb6463966a5f7dc251dea48e502f89817be73ec8c6e065
all i did was delete everything in appdata except the 2 confs and wallet.dat then dloaded 2.0.1 and let it sync from zero overnight. woke up, and started my masternode.
August 10, 2016, 12:15:44 PM
11:55:01

getblockhash 260635
11:55:01

3442c235d521c637985ad71893f2c3744780928f7705404d00550c15c5ead769
Could you please share some of the nodes that you're connecting to? I'm stuck on block 260584.
Quote
addnode=108.61.151.69
addnode=173.245.158.8
addnode=coin-server.com
addnode=185.86.151.173
addnode=185.86.149.212
addnode=dnetxef3rmouy5qo.onion:989
addnode=dnetxcvx4iqeunnk.onion:989
addnode=dnetxn4m5kfh4xhr.onion:989
addnode=dnetxu5edp35e4rm.onion:989
addnode=y5kcscnhpygvvnjn.onion:989
addnode=5bmhtjvn2jvwpiej.onion:989
addnode=pyfdxkazur3iib7y.onion:989
addnode=ok3ym5zy6m5klimk.onion:989
addnode=i6vpvzk2jxuqqs5f.onion:989
addnode=bgdhpb76fkbw5fmg.onion:989
addnode=gtlqzb5zbws5di7g.onion:989
addnode=f7j2m26rptm5f7af.onion:989
addnode=dnetzj6l4cvo2fxy.onion:989
addnode=s3v3n7xhqafg6sb7.onion:989
addnode=173.245.158.8
addnode=coin-server.com
addnode=185.86.151.173
addnode=185.86.149.212
addnode=dnetxef3rmouy5qo.onion:989
addnode=dnetxcvx4iqeunnk.onion:989
addnode=dnetxn4m5kfh4xhr.onion:989
addnode=dnetxu5edp35e4rm.onion:989
addnode=y5kcscnhpygvvnjn.onion:989
addnode=5bmhtjvn2jvwpiej.onion:989
addnode=pyfdxkazur3iib7y.onion:989
addnode=ok3ym5zy6m5klimk.onion:989
addnode=i6vpvzk2jxuqqs5f.onion:989
addnode=bgdhpb76fkbw5fmg.onion:989
addnode=gtlqzb5zbws5di7g.onion:989
addnode=f7j2m26rptm5f7af.onion:989
addnode=dnetzj6l4cvo2fxy.onion:989
addnode=s3v3n7xhqafg6sb7.onion:989
With only the nodes thata appear in Ops in this moment.
August 10, 2016, 12:12:22 PM
11:55:01

getblockhash 260635
11:55:01

3442c235d521c637985ad71893f2c3744780928f7705404d00550c15c5ead769
Could you please share some of the nodes that you're connecting to? I'm stuck on block 260584.
August 10, 2016, 11:55:23 AM
11:55:01

getblockhash 260635
11:55:01

3442c235d521c637985ad71893f2c3744780928f7705404d00550c15c5ead769
August 10, 2016, 11:49:14 AM
premature forcing off master nodes on the wrong fork could weaken the network.. saying that I have all nodes checking against correct fork

getblockhash 259880 returns f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098 for all
UI latest block is @ 260391 , staking is still not active
all master nodes are engaged and collecting their share, left around 10K in the UI wallet for POS test and compare
*** update complete ***

getblockhash 259880 returns f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098 for all
UI latest block is @ 260391 , staking is still not active
all master nodes are engaged and collecting their share, left around 10K in the UI wallet for POS test and compare
*** update complete ***
network is already not secure with all these different forks. force them all off that are not on the right chain and maybe we can get going somewhere.
on the second thought.. you might be right.. see my post above.. I can not wear hardware down for too long... +1 on de-activating Mn on the wrong fork , gotta go now but revisit us this thread later tonight and proceed accordingly
August 10, 2016, 11:47:01 AM
*** update addendum ***
due to excessive CPU consumption I am temporarily disabling master nodes, following creates unnecessary CPU cycles.. saving machinery for the time being and turning them off till the next update (my intent is to run hardware for a very long time.. definitely will re-enable them to resolve below and cut CPU there heat intake , which wears the hardware if prolonged ...)
016-08-10 16:45:12 ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake feb1f00c80073b7308a11a3fb956d63c069be0809b548064e910ac3a9cc54fd5, hashProof=0000000000000000000000000000000000000000000000000000000000000000
2016-08-10 16:45:12 WARNING: ProcessBlock(): check proof-of-stake failed for block 8405a6904efbee0b0227b635118430e188ff35ed78de59ff3d799cb0eee090e2
2016-08-10 16:45:12 ERROR: ProcessNewBlock : AcceptBlock FAILED
...
...
...
due to excessive CPU consumption I am temporarily disabling master nodes, following creates unnecessary CPU cycles.. saving machinery for the time being and turning them off till the next update (my intent is to run hardware for a very long time.. definitely will re-enable them to resolve below and cut CPU there heat intake , which wears the hardware if prolonged ...)
016-08-10 16:45:12 ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake feb1f00c80073b7308a11a3fb956d63c069be0809b548064e910ac3a9cc54fd5, hashProof=0000000000000000000000000000000000000000000000000000000000000000
2016-08-10 16:45:12 WARNING: ProcessBlock(): check proof-of-stake failed for block 8405a6904efbee0b0227b635118430e188ff35ed78de59ff3d799cb0eee090e2
2016-08-10 16:45:12 ERROR: ProcessNewBlock : AcceptBlock FAILED
...
...
...
August 10, 2016, 11:45:34 AM
premature forcing off master nodes on the wrong fork could weaken the network.. saying that I have all nodes checking against correct fork

getblockhash 259880 returns f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098 for all
UI latest block is @ 260391 , staking is still not active
all master nodes are engaged and collecting their share, left around 10K in the UI wallet for POS test and compare
*** update complete ***

getblockhash 259880 returns f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098 for all
UI latest block is @ 260391 , staking is still not active
all master nodes are engaged and collecting their share, left around 10K in the UI wallet for POS test and compare
*** update complete ***
network is already not secure with all these different forks. force them all off that are not on the right chain and maybe we can get going somewhere.
August 10, 2016, 11:42:51 AM
I have masternodes on blocks
260391
260203
260369
259200
all latest wallets...
260391
260203
260369
259200
all latest wallets...
August 10, 2016, 11:35:04 AM
premature forcing off master nodes on the wrong fork could weaken the network.. saying that I have all nodes checking against correct fork

getblockhash 259880 returns f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098 for all
UI latest block is @ 260391 , staking is still not active
all master nodes are engaged and collecting their share, left around 10K in the UI wallet for POS test and compare
*** update complete ***

getblockhash 259880 returns f6bf9eae07bbba776309c374ef73b83bf633853b7026ceeff17e20ccd0774098 for all
UI latest block is @ 260391 , staking is still not active
all master nodes are engaged and collecting their share, left around 10K in the UI wallet for POS test and compare
*** update complete ***
Jump to: