So, presstab has updated his block explorer to the latest wallet, so that is right, thank you presstab. Now, if the exchanges could just show that same sense of urgency. Will keep you guys posted as we notice things getting back on the right wallet.

That must have been before block 86400, around 10:30 PM est last night.

Very cool, much appreciated.

OK, so, everyone out there in DarkNet land, if you know of any other services that were on the v1.0.2.1 wallet before block 86400 let us know. Once we get a list of those that were there doing a good job, in turn helping out DarkNet to be all it can be, we will throw a few coins their way as a thanks for your support kind of gesture.

Everyone should hold off on sending coins to or from exchanges for a bit. I noticed that presstab's explorer was off after block 86400, did some test transactions, it looks like trex, yobit and safecex are all on the old wallet still, the 2 chains are incompatible. If you send coins now they won't show up until the exchanges update their wallets. If you sent coins recently, since block 86400 they are safe in the blockchain, they will just be in limbo until the wallets are updated on the exchanges. We will let you know as soon as we know of exchanges updating their wallets, they were all given ample notice, so don't know what happened there. In the meantime, we know that the explorer at http://darknetexplorer.coin-server.com/ is right, coin-server's pool is on the right wallet, and the suprnova pool as well. Those are the only services we can confirm to be updated with 100% certainty. We will keep you posted.

Any Node.js and Python gurus in here? PM s3v3nh4cks or myself.

The idea is to get a lot of coins out in the wild, with a nice circulation, before the beginning of PoS. Right now we seem to have the highest hashrate of any other quark based coin I looked at, by a longshot. That is providing for a very secure network. In order to have a similar level of security during PoS a high number of coins is required. If you think of each coin as a mining machine, and each wallet as a miner, you can see why this is important. Once we have enough coins to securely switch to PoS we will taper off the coin supply, as there is no need to continue the high rate of inflation such rapid coin production yields. We decided to reduce the coin supply over as short a time as possible to reduce the overall supply as much as could be. We choose to reduce things at as steady a rate as reasonable to help prevent the wild swings in prices that would come with sharp reductions such as halvings.

So, everyone, PoS rewards schedule, any suggestions? Amounts, stages, supporting arguments? We could just dictate them to you from on high, but this is your coin too, own it.

OK guys, while I appreciate everyone sharing thoughts and ideas, I think things are getting a little of course. We have a while to discuss and debate other aspects of the way things will work, crunch numbers, etc. Right now the question at hand, the one that sparked this flurry of conversation, has seen only one person weigh in with an opinion. Let's try and stay focused. How does everyone feel about the numbers s3v3n laid out? Are you in favor, or against? Why? There are a lot of smart people in here, with a lot of good questions, and a lot of valuable insight. If we don't try to keep the conversation revolving around one specific item at a time we will just go down the rabbit hole and never come to any firm conclusions on any particular subject. Again, for the sake of steering things back on course:


Food for thought, personally, I am torn. I agree that we don't want to have billions of coins in the long run, and that cutting the rewards once we hit PoS is the thing to do. My concern is that these numbers may cut them too much too fast. I can envision a scenario where as we approach the end of PoW knowing the rewards will drop many masternode owners would shut them down and cash out. Without an equally drastic rise in the price at around the same time as the drop in rewards the return from running a masternode would be dramatically reduced. Masternode owners shutting down and cashing out would cause the price to drop, further exacerbating the reduced income from owning a masternode and perpetuating the cycle. I am sure things would level out at some point, but the unpredictability and volatility would not be good for the coin as a whole.

Feel free to tell me I am thinking about it all wrong, and why. I would like to see these numbers become the ones we use for PoS. At the same time, I want it to be because it is the right thing for the long term health of DarkNet, and not just because large holders, myself included, would stand to make a quick profit.

The split between the masternodes and the staker would still be using the seesaw mechanism we had discussed before. The numbers for the split between stakers and masternodes are still being hashed out. Our intent is still to have masternodes be only slightly more profitable than staking on a per coin basis when the network is balanced properly between coins staking and locked up in masternodes. We are really just trying to see how everyone feels about the overall block rewards and coin production. Once we are switched over to PoS we can reduce inflation by lowering the rewards for each block. What we want to do is start a conversation about the pros and cons of such substantial rewards reductions.

Nope.

Edit: Not without shutting down your masternode, anyway

Just an update folks, we have been working diligently to figure out what the hell is going on. s3v3n and I are in the same boat as everyone else, and are exhausting all of our options to remedy this. I have held off on saying much, but I think that the fact that there are wallets of all versions, 1.0.1.0, 1.0.2.0, and 1.0.2.1 acting up suggests that something other than a wallet issue is at play. We reverted most of the changes that were brought about in v1.0.2.0 with v1.0.2.1 just to make sure that there wasn't something we were missing, it would seem that there wasn't.

The only thing that can ever cause a Masternode's state to go to "EXPIRED" is if it hasn't been able to be pinged by the network for 65 minutes. If you go to http://www.yougetsignal.com/tools/open-ports/ and verify that you Masternode is reachable on port 51472 then you should sending and receiving pings. If it is reachable, and your Masternode is going to expired the only remaining explanation is that something, or someone, is blocking communication somehow. After checking quite a few Masternode addresses at random and finding them reachable, I have to assume there is something nefarious afoot.

Please bear with us as we work to figure out exactly what is happening, and how to alleviate the problem. Communication from us is limited as we are trying to focus all of our energy on getting things back to the smooth operations we had prior to this. Please, keep posting anything you are noticing, good, bad, or indifferent, we may not respond immediately, but are checking in here often for updates from you guys.

Thanks for your patience while we work this out, as soon as we are certain of the next move we will let you know.

Just put the windows v1.0.2.1 wallets up, link in OP.

Are all of your wallets in sync? Wallets falling out of sync seems to be the cause of that issue. Current block is 73322.

Hey everyone, check your wallets, Masternodes and not. I have noticed a problem with a bunch of my nodes, I am not sure how widespread it is, but it was preventing Masternode payments for a few of mine. I haven't narrowed down the cause yet, but quite a few of my nodes were stuck at block 69085, and no amount of rebooting or restarting the wallets seemed to work. I ultimately had to delete everything except my darknet.conf and wallet.dat from the data directory and resync. They all seemed fine after that.

Oh, man. Yeah. The output from "masternode genkey" is not the same as the private key for your address. No coins can be spent with that.

Edit: Backup, Backup, Backup

I think, if I understand you correctly, you are looking for "masternode start-alias XXX" where the XXX would be replaced with the name of your Masternode as you have it in the masternode.conf.

Without more information no one can help you. Is this a local Masternode, or a remote/local setup? Did you do anything in your data directory when upgrading? Any other information you can think of?

StakeBox.com?

Raspbian is the default RPi OS, it is a version of Debian specifically for the RPi.