OK everyone. It was just brought to my attention that the chain started moving again. Some clown went ahead and custom compiled a wallet with the staking time parameter removed and figured they would get all of the coins for a day. I am going to make a new checkpoint at block 201 and we will all have to roll back to keep them from getting away with these shenanigans. I was actually worried that this might happen earlier today when I let the 259201 hash that was checkpointed out into the wild.

We are all going to need a new wallet and recync thanks to this guy. I will get on that in a few, but I think I am going to keep the relaunch at the 9PM tomorrow time, unless there is an outpouring of people asking for more time to prepare.

Correct. They are active now, they should be fine once the chain starts moving again tomorrow.

No. Just figured out the issue. I screwed up. Last night when I entered the time parameter I added a day to the converter without looking at the date. I inadvertently made the start time tomorrow at 9PM EST by doing that. It is too late to change that now and still have a fair launch. Totally my fault, I am so sorry. It is what it is now.

For anyone wondering, the reason for the blocks that did go through is that I had to make a custom wallet to get the chain moving again. Otherwise everyone would be sitting there waiting for the sync to finish before they could stake, and with no one staking the newest block would have continue to be 2 days old, and no one would start staking, and so on and so on.

So, with that said, tomorrow, same bat time, same bat channel.

It did serve as a good quick test. Thanks for forgiving my screw up.

And we're off!!!

Nope, that is the 201 block I checkpointed in to be sure we are all starting on the same chain.

PM your email address to s3v3n and he will send you an invite.

Yeah, the v2.0.5.0 wallet is 70650, but can also connect to 70600.

Things are looking good with v2.0.5.0 right now. There are a few wallets staking that would have forked the chain by now on the previous versions. Fire up some more staking wallets people!!

While we appreciate your service, you do realize that that is currently a testing chain, everything over block 259200 is going to be bogus soon when we roll back and relaunch PoS, right?

Yup, we are testing v2.0.5.0 right now. We noticed that there were still a few people getting off on separate forks. Non-staking wallets seemed to not be affected, only those staking, and it seemed you had to be staking a pretty good number of coins as well. We make another small tweak and are beating up on it now. If anyone wants to join in you can grab it here, https://github.com/Darknet-Crypto/Darknet/releases/tag/v2.0.5.0.

If you are going to test this wallet, and we hope you will, delete your peers.dat, and sync from scratch using the nodes from http://www.presstab.pw/phpexplorer/DNET/nodes.php. You should add listen=0 to your darknet.conf, once you are synced up you can shut down the wallet and remove the listen=0. That line may not be needed, but I did find myself getting sucked onto a bad chain without it this morning.

Let us know what you get. Thanks again, we are almost there.

OK guys, while we really appreciate the way everyone is so willing to help others out in here please be careful about spreading misinformation. That will just add to the confusion.


No, your wallet does not need to be encrypted in order to stake.


Your v2.4.0.0 wallet should be staking. I have found that after syncing from scratch I need to restart my wallet before it will start staking.

It is the v2.1.0.0 wallet is the one that will not stake until a given time.

You got it.

Yup.

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.

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.

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.

Remove the addnodes and sync from scratch. There are enough 2.0.4.0 wallets up now that does not take that long.

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.

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.

Just a blockhash for folks to check.

If you enter "getblockhash 259852" in the console you should get 8b59e1cdbf2fd60ef1a28bb8a09a8c9bc660ac0977d933b5584ca34ff7dfb2e6