Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 366. (Read 782375 times)
August 13, 2016, 06:02:06 PM
Cool. I'm now testing v2.0.4.0 wallet on my main controller wallet & 1 masternode as a test. Still syncing.
August 13, 2016, 05:26:44 PM
Awesome work and thanks to all dev team members & community members!
As for this v2.0.4.0, is this just a public test before the real wallet of v2.1.0.0 which will once again be mandatory with a full resync from scratch? (to rollback)
You got it. As for this v2.0.4.0, is this just a public test before the real wallet of v2.1.0.0 which will once again be mandatory with a full resync from scratch? (to rollback)
August 13, 2016, 05:26:28 PM
I´ve synced up to 260107.
00:15:02

getblockhash 260107
00:15:02

523db4fdff2edc9904333e0e10bb0f852e45169549486659af6e1f9e78b192a6
we good now?
00:15:02

getblockhash 260107
00:15:02

523db4fdff2edc9904333e0e10bb0f852e45169549486659af6e1f9e78b192a6
we good now?
Yup.
August 13, 2016, 05:25:46 PM
Awesome work and thanks to all dev team members & community members!
As for this v2.0.4.0, is this just a public test before the real wallet of v2.1.0.0 which will once again be mandatory with a full resync from scratch? (to rollback)
As for this v2.0.4.0, is this just a public test before the real wallet of v2.1.0.0 which will once again be mandatory with a full resync from scratch? (to rollback)
August 13, 2016, 05:15:58 PM
I´ve synced up to 260107.
00:15:02

getblockhash 260107
00:15:02

523db4fdff2edc9904333e0e10bb0f852e45169549486659af6e1f9e78b192a6
we good now?
00:15:02

getblockhash 260107
00:15:02

523db4fdff2edc9904333e0e10bb0f852e45169549486659af6e1f9e78b192a6
we good now?
August 13, 2016, 05:11:47 PM
My debug log has some network errors
2016-08-13 21:44:59 getblocks 260008 to end limit 500 from peer=27
2016-08-13 21:45:53 connect() to [2001:19f0:5000:80a5::4]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:05 connect() to [2a02:120b:c3c4:1610:3c7d:793:a36c:fc74]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:08 connect() to [2001:470:1f11:1d4:5054:ff:fef8:6ee]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:17 connect() to [2a01:4f8:c17:2ff8::101]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:20 connect() to [2a01:4f8:c17:2ff8::104]:51472 failed: Network is unreachable (101)
My network was never down, was watching netflix.
So not sure what caused these issues
Any chance you can hop onto skype or slack using the links in the OP to get this sorted out quicker? There has been no other forking reported, hopefully it is something simple on your end. 2016-08-13 21:44:59 getblocks 260008 to end limit 500 from peer=27
2016-08-13 21:45:53 connect() to [2001:19f0:5000:80a5::4]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:05 connect() to [2a02:120b:c3c4:1610:3c7d:793:a36c:fc74]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:08 connect() to [2001:470:1f11:1d4:5054:ff:fef8:6ee]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:17 connect() to [2a01:4f8:c17:2ff8::101]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:20 connect() to [2a01:4f8:c17:2ff8::104]:51472 failed: Network is unreachable (101)
My network was never down, was watching netflix.
So not sure what caused these issues
August 13, 2016, 05:09:31 PM
Hi Guys
just so that you are aware im will be doing a mass update of my servers when i have been given the ok
from the Devs. So don't be to eager to update your masternodes as the WILL get updated in the mass update
thanks
Paul
just so that you are aware im will be doing a mass update of my servers when i have been given the ok
from the Devs. So don't be to eager to update your masternodes as the WILL get updated in the mass update
thanks
Paul
I went in the other day to change the addnodes and re download the blockchain but got stuck.
Are you reseting them completely? Or will I want to start where I left off?
I have removed nodes from the desktop 2.0.4.0 conf plus all but 3 needed files and am syncing now. I also removed them from the masternode but running darknet-update.sh is still on v2.0.2.0-f97daec.
I'll wait for Paul to update the node wallets.
August 13, 2016, 04:49:02 PM
My debug log has some network errors
2016-08-13 21:44:59 getblocks 260008 to end limit 500 from peer=27
2016-08-13 21:45:53 connect() to [2001:19f0:5000:80a5::4]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:05 connect() to [2a02:120b:c3c4:1610:3c7d:793:a36c:fc74]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:08 connect() to [2001:470:1f11:1d4:5054:ff:fef8:6ee]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:17 connect() to [2a01:4f8:c17:2ff8::101]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:20 connect() to [2a01:4f8:c17:2ff8::104]:51472 failed: Network is unreachable (101)
My network was never down, was watching netflix.
So not sure what caused these issues
2016-08-13 21:44:59 getblocks 260008 to end limit 500 from peer=27
2016-08-13 21:45:53 connect() to [2001:19f0:5000:80a5::4]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:05 connect() to [2a02:120b:c3c4:1610:3c7d:793:a36c:fc74]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:08 connect() to [2001:470:1f11:1d4:5054:ff:fef8:6ee]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:17 connect() to [2a01:4f8:c17:2ff8::101]:51472 failed: Network is unreachable (101)
2016-08-13 21:46:20 connect() to [2a01:4f8:c17:2ff8::104]:51472 failed: Network is unreachable (101)
My network was never down, was watching netflix.
So not sure what caused these issues
August 13, 2016, 04:45:23 PM
My linux controller wallet has now forked three times in a row
I kept wiping everything and resyncing, but after an hour or so it gets stuck on its own fork
Its currently stuck on 260019, with the hashes of 260015 onwards being incorrect.
23:40:20

getblockchaininfo
23:40:21

{
"chain" : "main",
"blocks" : 260019,
"headers" : 260019,
"bestblockhash" : "fa66764e53863da54b0b3f8d57b39fdbebfc700655f28a7f268a51863e27bcc4",
"difficulty" : 363.10622457,
"verificationprogress" : 0.99952380,
"chainwork" : "00000000000000000000000000000000000000000000000000dcfee0426d8af7"
}
23:42:11

getblockhash 260019
23:42:11

fa66764e53863da54b0b3f8d57b39fdbebfc700655f28a7f268a51863e27bcc4
My masternodes are staying synced, just my qt wallet that wonders off.
I kept wiping everything and resyncing, but after an hour or so it gets stuck on its own fork
Its currently stuck on 260019, with the hashes of 260015 onwards being incorrect.
23:40:20

getblockchaininfo
23:40:21

{
"chain" : "main",
"blocks" : 260019,
"headers" : 260019,
"bestblockhash" : "fa66764e53863da54b0b3f8d57b39fdbebfc700655f28a7f268a51863e27bcc4",
"difficulty" : 363.10622457,
"verificationprogress" : 0.99952380,
"chainwork" : "00000000000000000000000000000000000000000000000000dcfee0426d8af7"
}
23:42:11

getblockhash 260019
23:42:11

fa66764e53863da54b0b3f8d57b39fdbebfc700655f28a7f268a51863e27bcc4
My masternodes are staying synced, just my qt wallet that wonders off.
August 13, 2016, 04:30:53 PM
All of the v2.0.4.0 binaries are up now, snag them at https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.0.4.0. Anyone with some coins to stake should get on that. Let's try and break this thing. It is going good now and it looks like we got her licked, let's make sure.
We are going to be pushing out a new version of the wallet later on today. Assuming everything keeps moving along fine like it is it will be version 2.1.0.0. It will be more or less the same as v2.0.4.0, with the inclusion of a blockchain restart time. We will roll back to block 259200 and staking will not be enabled until 9:00pm EST Monday. That should give most everyone the opportunity to get the new wallet installed, synced from scratch, and any masternodes started and waiting. That seems the most fair way of handling this.
We are going to be pushing out a new version of the wallet later on today. Assuming everything keeps moving along fine like it is it will be version 2.1.0.0. It will be more or less the same as v2.0.4.0, with the inclusion of a blockchain restart time. We will roll back to block 259200 and staking will not be enabled until 9:00pm EST Monday. That should give most everyone the opportunity to get the new wallet installed, synced from scratch, and any masternodes started and waiting. That seems the most fair way of handling this.
So will this be an automatic switch over? It's 2.00am Tuesday morning for us in the uk. Don't fancy staying up to restart things at that time.
Yeah. If you have everything setup and ready to go with the v2.1.0.0 wallet staking will just start at that time, as well as masternode payments.
August 13, 2016, 04:22:53 PM
All of the v2.0.4.0 binaries are up now, snag them at https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.0.4.0. Anyone with some coins to stake should get on that. Let's try and break this thing. It is going good now and it looks like we got her licked, let's make sure.
We are going to be pushing out a new version of the wallet later on today. Assuming everything keeps moving along fine like it is it will be version 2.1.0.0. It will be more or less the same as v2.0.4.0, with the inclusion of a blockchain restart time. We will roll back to block 259200 and staking will not be enabled until 9:00pm EST Monday. That should give most everyone the opportunity to get the new wallet installed, synced from scratch, and any masternodes started and waiting. That seems the most fair way of handling this.
We are going to be pushing out a new version of the wallet later on today. Assuming everything keeps moving along fine like it is it will be version 2.1.0.0. It will be more or less the same as v2.0.4.0, with the inclusion of a blockchain restart time. We will roll back to block 259200 and staking will not be enabled until 9:00pm EST Monday. That should give most everyone the opportunity to get the new wallet installed, synced from scratch, and any masternodes started and waiting. That seems the most fair way of handling this.
So will this be an automatic switch over? It's 2.00am Tuesday morning for us in the uk. Don't fancy staying up to restart things at that time.
August 13, 2016, 04:19:17 PM
All of the v2.0.4.0 binaries are up now, snag them at https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.0.4.0. Anyone with some coins to stake should get on that. Let's try and break this thing. It is going good now and it looks like we got her licked, let's make sure.
We are going to be pushing out a new version of the wallet later on today. Assuming everything keeps moving along fine like it is it will be version 2.1.0.0. It will be more or less the same as v2.0.4.0, with the inclusion of a blockchain restart time. We will roll back to block 259200 and staking will not be enabled until 9:00pm EST Monday. That should give most everyone the opportunity to get the new wallet installed, synced from scratch, and any masternodes started and waiting. That seems the most fair way of handling this.
We are going to be pushing out a new version of the wallet later on today. Assuming everything keeps moving along fine like it is it will be version 2.1.0.0. It will be more or less the same as v2.0.4.0, with the inclusion of a blockchain restart time. We will roll back to block 259200 and staking will not be enabled until 9:00pm EST Monday. That should give most everyone the opportunity to get the new wallet installed, synced from scratch, and any masternodes started and waiting. That seems the most fair way of handling this.
August 13, 2016, 04:03:12 PM
Hi Guys
just so that you are aware im will be doing a mass update of my servers when i have been given the ok
from the Devs. So don't be to eager to update your masternodes as the WILL get updated in the mass update
thanks
Paul
just so that you are aware im will be doing a mass update of my servers when i have been given the ok
from the Devs. So don't be to eager to update your masternodes as the WILL get updated in the mass update
thanks
Paul
I went in the other day to change the addnodes and re download the blockchain but got stuck.
Are you reseting them completely? Or will I want to start where I left off?
August 13, 2016, 03:52:14 PM
Hi Guys
just so that you are aware im will be doing a mass update of my servers when i have been given the ok
from the Devs. So don't be to eager to update your masternodes as the WILL get updated in the mass update
thanks
Paul
just so that you are aware im will be doing a mass update of my servers when i have been given the ok
from the Devs. So don't be to eager to update your masternodes as the WILL get updated in the mass update
thanks
Paul
I went in the other day to change the addnodes and re download the blockchain but got stuck.
Are you reseting them completely? Or will I want to start where I left off?
August 13, 2016, 03:30:42 PM
check confirmed
master node 1:
darknet-cli getblockhash 259852
8b59e1cdbf2fd60ef1a28bb8a09a8c9bc660ac0977d933b5584ca34ff7dfb2e6
master node 2:
darknet-cli getblockhash 259852
8b59e1cdbf2fd60ef1a28bb8a09a8c9bc660ac0977d933b5584ca34ff7dfb2e6
excellent...
however getinfo on one says: (listing block # for each)
"blocks" : 259984,
"staking status" : "Staking Not Active",
second:
"blocks" : 259981,
"staking status" : "Staking Active",
update: first master node is @"blocks" : 259987 , maybe there are no more valid coins to stake upon for the time period..
anyways reporting if useful at all
master node 1:
darknet-cli getblockhash 259852
8b59e1cdbf2fd60ef1a28bb8a09a8c9bc660ac0977d933b5584ca34ff7dfb2e6
master node 2:
darknet-cli getblockhash 259852
8b59e1cdbf2fd60ef1a28bb8a09a8c9bc660ac0977d933b5584ca34ff7dfb2e6
excellent...
however getinfo on one says: (listing block # for each)
"blocks" : 259984,
"staking status" : "Staking Not Active",
second:
"blocks" : 259981,
"staking status" : "Staking Active",
update: first master node is @"blocks" : 259987 , maybe there are no more valid coins to stake upon for the time period..
anyways reporting if useful at all
August 13, 2016, 02:42:13 PM
Also, don't forget this site, http://178.254.23.111/~pub/DN/DN_masternode_payments_stats.html. Keep checking your blockhash against the one listed there. Don't worry so much about being on the same block as that site, I have noticed every once in a while it is a few behind, but catches up in short order. If you get a hash that doesn't match the block and hash shown there, then hop in here and say something. So far so good.
August 13, 2016, 02:36:13 PM
Wallet is fully synced at 259881, I bought coins during I think the 2.0.1, whenever it was working before, they are conflicted now. Am I out on those cause if so that sucks
No, we are going to roll back to block 259200 after testing this for a day or so. Any transactions after that will have never occurred. They will still be in the exchange's wallet. We will all need to clean our wallets. I am sure, if you are anything like me you have a boat load of orphan transactions in your wallet after these past few days. You can either start your wallet with the -zapwallettxes option, or, if you are running the Qt Tools->Wallet Repair->Recover transactions 1.I think the exchange just need to resend the transaction and it should appears in your wallet... technically the coins you send are still in the exchange wallet and may not have been attributed back to your exchange wallet.
getblockhash 259852
8b59e1cdbf2fd60ef1a28bb8a09a8c9bc660ac0977d933b5584ca34ff7dfb2e6
I think it's the one update we were waiting for
. Congrats Devs!!! Well done! August 13, 2016, 02:32:24 PM
Hi Guys
just so that you are aware im will be doing a mass update of my servers when i have been given the ok
from the Devs. So don't be to eager to update your masternodes as the WILL get updated in the mass update
thanks
Paul
just so that you are aware im will be doing a mass update of my servers when i have been given the ok
from the Devs. So don't be to eager to update your masternodes as the WILL get updated in the mass update
thanks
Paul
Saves me a job. Nice one Paul
August 13, 2016, 02:10:54 PM
Hi Guys
just so that you are aware im will be doing a mass update of my servers when i have been given the ok
from the Devs. So don't be to eager to update your masternodes as the WILL get updated in the mass update
thanks
Paul
just so that you are aware im will be doing a mass update of my servers when i have been given the ok
from the Devs. So don't be to eager to update your masternodes as the WILL get updated in the mass update
thanks
Paul
August 13, 2016, 02:09:42 PM
Wallet is fully synced at 259881, I bought coins during I think the 2.0.1, whenever it was working before, they are conflicted now. Am I out on those cause if so that sucks
No, we are going to roll back to block 259200 after testing this for a day or so. Any transactions after that will have never occurred. They will still be in the exchange's wallet. We will all need to clean our wallets. I am sure, if you are anything like me you have a boat load of orphan transactions in your wallet after these past few days. You can either start your wallet with the -zapwallettxes option, or, if you are running the Qt Tools->Wallet Repair->Recover transactions 1. Jump to: