pardon me which nodes for "protocolversion" : 70600 ?
for start I have 2 master nodes both at the following sync point, once more pool join the network and below moves to Staking Active I will roll out additional 7, then re-group with all here and a consensus for a rollback and then full 45 master nodes and back in business
{
"version" : 2000400,
"protocolversion" : 70600,
"walletversion" : 61000,
"balance" : 10000.91355966,
"obfuscation_balance" : 0.00000000,
"blocks" : 261014,
"timeoffset" : 0,
"connections" : 4,
"proxy" : "",
"difficulty" : 20663.46769305,
"testnet" : false,
"keypoololdest" : 1470928679,
"keypoolsize" : 1002,
"paytxfee" : 0.00000000,
"relayfee" : 0.00010000,
"staking status" : "Staking Not Active",
"errors" : ""
}
Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 368. (Read 782375 times)
August 13, 2016, 12:22:41 PM
August 13, 2016, 12:02:37 PM
Cool!
But unfortunately, busy for the next several hours... Good luck!
But unfortunately, busy for the next several hours... Good luck!
August 13, 2016, 11:56:34 AM
OK everyone, first, you guys are awesome. I just want to reiterate a few of the comments above about how great this community is being as we work through these issues.
Now, onto the reason for my post. For all of you self compilers out there v2.0.4.0 is up on github, delete your peers.dat and either use a pre-PoS blockchain backup, or sync from scratch. If you are not 100% sure that your backup is from before block 259200 fire up an older version of the wallet with your backup and verify the block number. We seem to have a lot of people not following this step, which is exacerbating the problems with our testing.
We will get the precompiled binaries up as quickly as we can, let's try to break this one, we think we have it fixed, but, as you all know, it is not the first time we thought that. Most of the previous fixes were based on less complete info than this one, so....
Everyone should not get too attached to any coins you have staked or earned with your masternodes, once we confirm the problems are solved we will be rolling back to the beginning of PoS, so if that is the reason some of you are not replacing your blockchain when switching to the new version, please stop.
As usual, report all issues here, we really need your help. So far all of these versions have worked well when testing with a small group, it isn't until we release you guys on it that you are able to break it for us and further the cause. We just want to thank you all again for being so great about this.
Now, onto the reason for my post. For all of you self compilers out there v2.0.4.0 is up on github, delete your peers.dat and either use a pre-PoS blockchain backup, or sync from scratch. If you are not 100% sure that your backup is from before block 259200 fire up an older version of the wallet with your backup and verify the block number. We seem to have a lot of people not following this step, which is exacerbating the problems with our testing.
We will get the precompiled binaries up as quickly as we can, let's try to break this one, we think we have it fixed, but, as you all know, it is not the first time we thought that. Most of the previous fixes were based on less complete info than this one, so....
Everyone should not get too attached to any coins you have staked or earned with your masternodes, once we confirm the problems are solved we will be rolling back to the beginning of PoS, so if that is the reason some of you are not replacing your blockchain when switching to the new version, please stop.
As usual, report all issues here, we really need your help. So far all of these versions have worked well when testing with a small group, it isn't until we release you guys on it that you are able to break it for us and further the cause. We just want to thank you all again for being so great about this.
Great news! thanks for your work. furthermore worth bolding this part, best explanation... Please guys, by having a perfectly working chain it will be better than clinging on some stakes or mn payment that may become worthless if the chain can't stabilize...
OK everyone, first, you guys are awesome. I just want to reiterate a few of the comments above about how great this community is being as we work through these issues.
Now, onto the reason for my post. For all of you self compilers out there v2.0.4.0 is up on github, delete your peers.dat and either use a pre-PoS blockchain backup, or sync from scratch. If you are not 100% sure that your backup is from before block 259200 fire up an older version of the wallet with your backup and verify the block number. We seem to have a lot of people not following this step, which is exacerbating the problems with our testing.
We will get the precompiled binaries up as quickly as we can, let's try to break this one, we think we have it fixed, but, as you all know, it is not the first time we thought that. Most of the previous fixes were based on less complete info than this one, so....
Everyone should not get too attached to any coins you have staked or earned with your masternodes, once we confirm the problems are solved we will be rolling back to the beginning of PoS, so if that is the reason some of you are not replacing your blockchain when switching to the new version, please stop.
As usual, report all issues here, we really need your help. So far all of these versions have worked well when testing with a small group, it isn't until we release you guys on it that you are able to break it for us and further the cause. We just want to thank you all again for being so great about this.
Now, onto the reason for my post. For all of you self compilers out there v2.0.4.0 is up on github, delete your peers.dat and either use a pre-PoS blockchain backup, or sync from scratch. If you are not 100% sure that your backup is from before block 259200 fire up an older version of the wallet with your backup and verify the block number. We seem to have a lot of people not following this step, which is exacerbating the problems with our testing.
We will get the precompiled binaries up as quickly as we can, let's try to break this one, we think we have it fixed, but, as you all know, it is not the first time we thought that. Most of the previous fixes were based on less complete info than this one, so....
Everyone should not get too attached to any coins you have staked or earned with your masternodes, once we confirm the problems are solved we will be rolling back to the beginning of PoS, so if that is the reason some of you are not replacing your blockchain when switching to the new version, please stop.
As usual, report all issues here, we really need your help. So far all of these versions have worked well when testing with a small group, it isn't until we release you guys on it that you are able to break it for us and further the cause. We just want to thank you all again for being so great about this.
Good stuff so this release is really a test? So not the final thing? There will be a 2.0.5.0 which will be the final and start at block 259200 again?
This is what I understood too (ie a test).
August 13, 2016, 11:49:43 AM
I sincerely hope this time is the charm! Can't wait to stake.
August 13, 2016, 11:45:23 AM
OK everyone, first, you guys are awesome. I just want to reiterate a few of the comments above about how great this community is being as we work through these issues.
Now, onto the reason for my post. For all of you self compilers out there v2.0.4.0 is up on github, delete your peers.dat and either use a pre-PoS blockchain backup, or sync from scratch. If you are not 100% sure that your backup is from before block 259200 fire up an older version of the wallet with your backup and verify the block number. We seem to have a lot of people not following this step, which is exacerbating the problems with our testing.
We will get the precompiled binaries up as quickly as we can, let's try to break this one, we think we have it fixed, but, as you all know, it is not the first time we thought that. Most of the previous fixes were based on less complete info than this one, so....
Everyone should not get too attached to any coins you have staked or earned with your masternodes, once we confirm the problems are solved we will be rolling back to the beginning of PoS, so if that is the reason some of you are not replacing your blockchain when switching to the new version, please stop.
As usual, report all issues here, we really need your help. So far all of these versions have worked well when testing with a small group, it isn't until we release you guys on it that you are able to break it for us and further the cause. We just want to thank you all again for being so great about this.
Now, onto the reason for my post. For all of you self compilers out there v2.0.4.0 is up on github, delete your peers.dat and either use a pre-PoS blockchain backup, or sync from scratch. If you are not 100% sure that your backup is from before block 259200 fire up an older version of the wallet with your backup and verify the block number. We seem to have a lot of people not following this step, which is exacerbating the problems with our testing.
We will get the precompiled binaries up as quickly as we can, let's try to break this one, we think we have it fixed, but, as you all know, it is not the first time we thought that. Most of the previous fixes were based on less complete info than this one, so....
Everyone should not get too attached to any coins you have staked or earned with your masternodes, once we confirm the problems are solved we will be rolling back to the beginning of PoS, so if that is the reason some of you are not replacing your blockchain when switching to the new version, please stop.
As usual, report all issues here, we really need your help. So far all of these versions have worked well when testing with a small group, it isn't until we release you guys on it that you are able to break it for us and further the cause. We just want to thank you all again for being so great about this.
Good stuff so this release is really a test? So not the final thing? There will be a 2.0.5.0 which will be the final and start at block 259200 again?
August 13, 2016, 11:43:02 AM
cool, engaging git master and 45 master node updates and enabling POS, resyncing all from the ground up, stand by for an update
August 13, 2016, 11:37:49 AM
OK everyone, first, you guys are awesome. I just want to reiterate a few of the comments above about how great this community is being as we work through these issues.
Now, onto the reason for my post. For all of you self compilers out there v2.0.4.0 is up on github, delete your peers.dat and either use a pre-PoS blockchain backup, or sync from scratch. If you are not 100% sure that your backup is from before block 259200 fire up an older version of the wallet with your backup and verify the block number. We seem to have a lot of people not following this step, which is exacerbating the problems with our testing.
We will get the precompiled binaries up as quickly as we can, let's try to break this one, we think we have it fixed, but, as you all know, it is not the first time we thought that. Most of the previous fixes were based on less complete info than this one, so....
Everyone should not get too attached to any coins you have staked or earned with your masternodes, once we confirm the problems are solved we will be rolling back to the beginning of PoS, so if that is the reason some of you are not replacing your blockchain when switching to the new version, please stop.
As usual, report all issues here, we really need your help. So far all of these versions have worked well when testing with a small group, it isn't until we release you guys on it that you are able to break it for us and further the cause. We just want to thank you all again for being so great about this.
Now, onto the reason for my post. For all of you self compilers out there v2.0.4.0 is up on github, delete your peers.dat and either use a pre-PoS blockchain backup, or sync from scratch. If you are not 100% sure that your backup is from before block 259200 fire up an older version of the wallet with your backup and verify the block number. We seem to have a lot of people not following this step, which is exacerbating the problems with our testing.
We will get the precompiled binaries up as quickly as we can, let's try to break this one, we think we have it fixed, but, as you all know, it is not the first time we thought that. Most of the previous fixes were based on less complete info than this one, so....
Everyone should not get too attached to any coins you have staked or earned with your masternodes, once we confirm the problems are solved we will be rolling back to the beginning of PoS, so if that is the reason some of you are not replacing your blockchain when switching to the new version, please stop.
As usual, report all issues here, we really need your help. So far all of these versions have worked well when testing with a small group, it isn't until we release you guys on it that you are able to break it for us and further the cause. We just want to thank you all again for being so great about this.
August 13, 2016, 09:44:07 AM
So is everything good now? Can I open my wallet (2.0.2.0) and start staking or are things still in disarray? Thanks.
Unfortunately is not good yet. Even v2.0.3.0 is not good.
So please wait for next major wallet update.
OK, thanks for saving me a lot of frustration!! I'll wait then.
August 13, 2016, 09:36:48 AM
So is everything good now? Can I open my wallet (2.0.2.0) and start staking or are things still in disarray? Thanks.
Unfortunately is not good yet. Even v2.0.3.0 is not good.
So please wait for next major wallet update.
August 13, 2016, 09:29:32 AM
I feel like my small investment has already paid for itself in the knowledge I have gained in the short time I have been here. I don't feel like I have invested in a crypto currency, I feel like I have enrolled in a school.
For me these technical problems are teaching me more about blockchain technology and allowing me to practice skills that were on the brink of being forgotten. I bet I am not alone in thinking this way.
Thanks for the inspiration and motivation.
For me these technical problems are teaching me more about blockchain technology and allowing me to practice skills that were on the brink of being forgotten. I bet I am not alone in thinking this way.
Thanks for the inspiration and motivation.
If, "Bitcoin is the devils way of teaching computer geeks about economics" ~ SWIM / Source unknown.
DNET is currently the antithesis of the above.
August 13, 2016, 09:12:04 AM
I feel like my small investment has already paid for itself in the knowledge I have gained in the short time I have been here. I don't feel like I have invested in a crypto currency, I feel like I have enrolled in a school.
For me these technical problems are teaching me more about blockchain technology and allowing me to practice skills that were on the brink of being forgotten. I bet I am not alone in thinking this way.
Thanks for the inspiration and motivation.
For me these technical problems are teaching me more about blockchain technology and allowing me to practice skills that were on the brink of being forgotten. I bet I am not alone in thinking this way.
Thanks for the inspiration and motivation.
August 13, 2016, 09:01:02 AM
So is everything good now? Can I open my wallet (2.0.2.0) and start staking or are things still in disarray? Thanks.
August 13, 2016, 08:05:39 AM
Notices that Navcoin is running some full TOR nodes... details here:
https://bitcointalksearch.org/topic/m.15857415
This would also be an interesting way for DNET to get more publicity.
https://bitcointalksearch.org/topic/m.15857415
This would also be an interesting way for DNET to get more publicity.
It's in the works for the guide on how to do it. The person who made that post is active in this thread and I believe already has a basic guide ready.
August 13, 2016, 07:55:54 AM
Notices that Navcoin is running some full TOR nodes... details here:
https://bitcointalksearch.org/topic/m.15857415
This would also be an interesting way for DNET to get more publicity.
https://bitcointalksearch.org/topic/m.15857415
This would also be an interesting way for DNET to get more publicity.
August 13, 2016, 07:37:18 AM
I suppose there can still something else wrong with verifying the blocks other than the multiple chains. I tried to sync a node (using "connect=") from some of my masternodes that were on the same chain and it still gets stuck...
Maybe the devs could describe a bit about what they see as the problem and how to approach fixing it and get some fresh eyes on the code in github. The new software versions forks have put the DNET network into a weak and unstable state, this is something that could be addressed.
Maybe the devs could describe a bit about what they see as the problem and how to approach fixing it and get some fresh eyes on the code in github. The new software versions forks have put the DNET network into a weak and unstable state, this is something that could be addressed.
My opinion is that the "light" syncing that new core version of bitcoin and others have, which are centered around headers, is the root of the cause. You cannot check proof of stake with the information supplied in the current headers, so many wallets are essentially blindly accepting headers and supposing that they are valid. Every once in a while invalid headers slip in, and this creates a problem when trying to sync up.
I have created a blocks-only wallet, and I believe it is the solution for now. It suspends the "light" headers syncing functionality. I have had success testing the blocks-only wallet internally on my machines. It needs to be put to the test by everyone else though.
Nice to hear your opinion.
So the staking will be based on the available balance instead of unspent (and unlocked) transactions? I'm sure more would like to hear about how staking will work when there is time to explain.
August 13, 2016, 07:21:59 AM
Dropbox link with chain is not working
Error (429)
Please share it again.
Error (429)
Please share it again.
Don't bother with that chain or v2.0.3.0 wallet.
Dev team will be releasing a new wallet & chain with the workaround fix as mentioned above by presstab.
great! dnet is one of most prized possessions... I made ie nn,nnn% gain on emer (one example) believe same potential exists here
btw there will be rush (POW rush) on this https://z.cash/ in September we wont have this problem as we wiil be way into POS and master node phase, also look at dash run at 12 and change now.. yeah so these POS problems are minor providing we stabilize
doubtful zcash will do POS or maybe, and if they do , this enterprise is tricky as we all see here, aaaaall coins trying to do this will have perturbations and we will be loong pass that
(it is not just codebase but network and out of sync wallets .. takes time to stabilize even with the fix.. dash due to how expensive it is i hiiighly doubt will do POS, investors would tear em apart on any single mistake...
1,200$ for dash master node... and I am very sure it will go much higher.. its a great architecture (master node based that is) watching space close and see others will try to get into master node business.. it is complex... good!
also strangely bittrex unblocked wallet.. I would wait and test heeeeck out of this, have a great weekend!
https://bittrex.com/Market/Index?MarketName=BTC-DNET
August 13, 2016, 06:33:51 AM
Dropbox link with chain is not working
Error (429)
Please share it again.
Error (429)
Please share it again.
Don't bother with that chain or v2.0.3.0 wallet.
Dev team, will be releasing a new wallet & chain with the workaround fix as mentioned above by presstab.
Waiting for it
August 13, 2016, 06:32:43 AM
Dropbox link with chain is not working
Error (429)
Please share it again.
Error (429)
Please share it again.
Don't bother with that chain or v2.0.3.0 wallet.
Dev team will be releasing a new wallet & chain with the workaround fix as mentioned above by presstab.
August 13, 2016, 06:30:03 AM
Dropbox link with chain is not working
Error (429)
Please share it again.
Error (429)
Please share it again.
August 13, 2016, 06:18:53 AM
What is this mess ?!
i m stuck @bloc 260824 with wallet 2.0.2 ..
i m stuck @bloc 260824 with wallet 2.0.2 ..
Jump to: