Still waiting to hear back from dasource about the explorer; I don't run that. Coins will never actually be lost. If a transaction gets borked locally, they are still on that address on the network

I was recently at NASA for the last SpaceX launch and there was a social media guy there that I swear looked exactly how I picture satoshi to look

That was the goal with MMXIV. To provide a hedge using high stake rates. It's going alright

That's my point

It is watching the many stages of someone who is mentally unstable. Not like the dangerous kind, I've come to realize, but more of the delusional kind that is rather entertaining. If Vlad just toned down the crazy a tiny bit (and especially the italics), I bet he would get taken a lot more seriously

I've come to respect his opinion, but a few less crazy sprinkles on the ice cream would help a lot 

No problem. Basically, just ignore the invalid checkpoint alert for now. It's bullshit; they are all solid checkpoints

Yep. It's pushing the invalid checkpoint alert for valid checkpoints since the fork to timestamp based rewards. Working on a fix that doesn't require a fork, but for now only some people are seeing it and trying to figure out why valid checkpoints are being flagged

The db errors and wallet freezing should be over now, though. I believe I have solved that for good with the last quick patch to checkpoint servers that I threw into the network. The problem, now, is that the fix is now being flagged as invalid. It seems to be a Qt related display issue, as nobody running just the daemon seems to see it

Do you guys want Cloud Staking? As in.. if I set it up, will you actually sign up? I don't want to waste time setting something up for nobody to use like what happened with HYP

Do you guys want Cloud Staking? As in.. if I set it up, will you actually sign up? I don't want to waste time setting something up for nobody to use like what happened with HYP

Now that MMXIV is on CoinPayments, I could use some help approaching new merchants to accept it. If they are already using CoinPayments, it's as simple as activating the coin in Settings. If you guys get anyone that will accept it, let me know and I'll put links for them on the new Media tab I'm working on for GorillaStake.com

We actually get decent traffic, so a free ad on there might them get a sale or two

Half joke. It would only be 10k and BALLS

Yea, I'm going to post a whole media page on GorillaStake. I made a lot of contacts down there and think media will need its own tab now for what I'm going to be up to in the coming months

Then they were not imported properly

BTC market is not important right now; that portion of this coin is over for now, alternate markets are it's new home, just as planned. If the price ever reaches that height again, we can easily be re-added. Don't worry, you will still have somewhere to trade your coins

Well since you posted that here.. my guess is you have a change address. As far as the negative balance in the other wallet, I believe that was an orphaned change transaction. That account only exists as an orphan, so if you import all the positives into a fresh wallet you'll be good

While it is a visually intimidating problem, those coins never actually existed. It is a bug in the display, and has been noted, but just import all the positive keys to a fresh wallet and report back

For anyone else reading this, listaccount will probably have a change address for most of you who did it on accident, resulting is discrepancies between wallet UI and the explorer, as the wallet adds all addresses together while the explorer displays them individually

Just wanted to copy this over as it also applies here

Looks like the checkpoints aren't playing well with timestamp-based rewards. Staking will remain unaffected, but the alert seems to be active even though the checkpoints do appear to be valid. The db errors should be gone now, though. If anyone still sees those after a wallet restart, please let me know. I'm working on making the checkpoints more acceptable without compromising what they need to do

Basically, checkpoints aren't working well with timestamp rewards. Did not see this issue on testnet. Working on a fix without requiring a fork. It appears that the alert doesn't actually verify the checkpoints accurately, as they are valid on the network as far as I can see. So.. I'm going to let the current setup run for a few days (with the INVALID alert, even though they are valid) to test if the new update to checkpoint server permanently resolved the db issues. If the bandaid fixes that, then it is not the old clients causing issues, like I said from the start

I just linked this post to dasource

Change has been pushed to the network. Please ensure you are on version 2.0.2, restart clients and report results. Should be no need to download the blockchain from the start

Vote for it to be added to CoinPayments and I will gladly accept it

https://www.coinpayments.net/vote

MMXIV got 2nd in the last vote; that's how we got it added, but if you guys want it, you need to let them know