1. Yes, because you do have issues with the blockchin whether you realize it or not. 'Course , you could wait 'till i recompile with proper checkpoints and cleaner code and strip it properly if you prefer.

2. That's a bit more complicated than I can just "answer" here. Lotsa variables. Try googling, there's a few guides already, but you really kinda need to know whatyou're doing first.


Like i said, it's not really done yet

Alright, so I haven't been able to get in touch with anyone at cryptsy yet, nor have I managed to sync my chain with there's, but i did promise to release the fix today so I will at least do that. I haven't fixed all the forks yet but I have fixed the invalid stake issues so you can at least have a functional wallet again. Maybe the blockchain will even sort itself out before I get a chance to get the checkpoints sorted out.

Anyway, DOWNLOAD PENNIES V0.10.1.0-ALPHA STAKEFIXFIX: Windows-Qt* | Source

If your blockchain is still stuck after you update, you'll probably need to delete it and start from scratch. It'll likely pause frequently, you'll get a lot of errors in debug.log, and the client will likely still be unresponsive and laggy at times, but it will work.


* Still uploading.... Edit: Fuck it, taking to long to upload, if it happens to show up while i'm sleeping congrats, otherwise I'll try again in the morn.

Actually here, I'll try ad up it to Google Drive. Night.

The github does not have the latest changes yet, that was just a bit that I pulled over as a starting point. I already have the main issue fixed, I just need to figure out which fork cryptsy's on so I can insert the right checkpoints.

Edit: I just pushed the functioning code to the github, still needs the checkpoints and a bit of cleaning up though.

No idea yet, I'm having trouble getting in sync with cryptsy's chain. I can't seem to connect my wallet directly to them and my contacts there are unavailable at the moment to give me some checkpoint info =\

Probably, the blockchain past 242000 is all kindsa forked up, so some transactions may get undone, but I'm trying to make sure the checkpoints line up with the fork cryptsy's on so those transactions should all work out.

Good news everyone! I think I have the fix!

I need to give it more time to sync, run some more tests, and clean up the code, but if all goes well it should be released tomorrow!

yay!

ಠ_ಠ How many people do you think are this stupid?

For anyone whose falling for this:

1. Anyone with the smallest bit of competence with an image editing program can avoid "distorted pixels" easily.
2. You don't even need to shoop to make something like this, he can just edit the tweet locally and screencap it.
3. For example:

Nice shoop, too bad his twitter feed is publicly viewable and anyone with an ounce of intelligence can easily check that this never happened.

For anyone interested, this is the comment BigVern made at @CryptoApocolypt, which clearly has nothing to do with removing the withdraw feature. And this is the image bitcoinexpress just tried to pawn off as BigVern's tweet, in case he decides to try and pretend it never happened.

The clientversion file never got updated because it's only ever referenced in peer info and it was forgotten.

It looks strange because he's either running on win98 or earlier, or classic mode on winxp and newer.

No, shake abandoned it because it was broken in the first place, I didn't manufacture the problem.

And btw, there aren't really any forks, the entire chain is stalled because all the blocks containing stake before the last attempted fix were invalidated due to an oversight.

It should be noted that what i'm attempting to do is something the PoS system was not designed for, it's like trying to change the design of a roller coaster while it's actively running. Course, if you want the inflation to continue I could just revert everything back to the way it was before and wait for the blockchain to become so bloated the client never boots again, ever.

Alright, I need sleep, I'll continue trying to fix the problem tomorrow.

In the meantime, if anyone happens to be an expert on the proof of stake system, please take a look and see if you have any ideas. There's got to be a stake validation check somewhere I'm missing somewhere. The problem is that the new stake value is being used to check the old stake transactions and it obviously failing. On re-examination the method we used to change it was pretty obviously not going to work, but the other methods I've tried (using block nTime and nHeight, in various ways) don't seem to be working either.

Right, forgot to address that too. I didn't make craftcoin, i never said that. I'm just involved. I just helped blindmice when he created it, in a "guru" sort of position. I do that a lot.

Well, the main issue is that most implementations in games would require having a server wallet, with a PoS currency that means that users who use their coin mostly in-game (in other words, not store their coins in a local wallet) will most likely lose profit on their coins unless the developer jumps through flaming hoops with their arms tied behind there back and a blindfold on to make sure players get credited all their stake. But even then, it's just kinda weird y'know? Why would you get more coins just for leaving them sitting? That just discourages people from actually using their coins on goods.

Add to that the fact that PoS coins in general, and Pennies notably, have a history of being unstable and encountering weird issues, it's really just not ideal for a dedicated game currency and any sane game dev would stay far, far away.

Response regarding future pennies usage:

Aside from my involvement with craftcoin, and the plans I already have for creating a new currency for games (please, no questions at this time), there's a significant flaw with the idea of using Pennies for games: stake.

Sure, the over valued stake is being fixed, but the whole PoS system is broken as hell from the ground up, and it would just cause unnecessary hassle for in-game usage. I can not in any way endorse or support it's use in games simply because I know it's a terrible idea.

As for promotional use on twitter and whatnot, that sounds like a good idea. I'm not to big on social media myself but I can easily see how marketable it would be for someone that is. I can also see this being used in tipbots on IRC networks and sites like reddit. These i projects I can endorse (though have no desire in participating in).

That's all I have to say on it really.

If shake had his way this coin would be dead by now. In retrospect i shoulda let him do it.

Right, because dividing everyone's wallets by a billion totally fixes the stake issues.

Rest assured, I will not be implementing your "fix", ever. Why don't you go play with your noirbits? Oh, wait, didn't mommy take that toy away from you?




Anyway, to everyone else; I've already diagnosed the problem and am working on a solution, please be patient. Do not revert to the old client, or you may lose all your pennies when I fix this.

I've already said I'm looking into it, calm the fuck down. Proof of Stake was a half-assed hack job and it wasn't designed to be changed in the middle of the blockchain. Complications were expected and they will be dealt with accordingly.

Throwing around insults isn't going to help anything.

I'm not sure why people are getting stuck at 50623, my chain's currently at 242690 and reports that there are currently 243036 blocks  in the chain.

I will look into this further.

Alright, from what i'm seeing there's one of 3 problems going on at the moment.

1. Cryptsy is outdated and everyone who is reporting successful transactions is too.
2. There's a fork.
3. Uhhh, I forgot what this one was.

However, while i was writing this i tried connecting to the cryptsy node with no success, leading me to believe that it's problem #1.
Make sure your wallet is updated and try connecting to these nodes:

I'll be pushing out a checkpoint update that should address any forking issues should there be any in the near future (as well as max_tx).

i never said anything about restarting. It's normal to expect things to be a bit wonky after a change like this.