Actually, since I posted that I haven't had a single problem. Whatever it was must have gotten sorted.

You could try presstab. Dunno if he'll do it, but he's good. He and I are on good terms, so tell him I recommended him. This will prevent any snide remarks to anyone but me I'd do it, but I'm offline in an hour.

sounds like you have some orphans stuck in your system. go into the debug console and type repairwallet.

I think so, if you make sure you're above the forked block on the proper chain first.

step 2, yes. Step 4, it's always good to back up your wallet, but incorrect transactions will simply not confirm. If you're resyncing from zero or the uploaded blockchain, it shouldn't matter.

@ david, yes, it's normally addnode instead of connect. But to make sure, prior to the checkpoints and exclusions, connect will ONLY connect to the noted IP, whereas addnode will allow you to connect to as many peers as it can find.

That is in fact one way to make a test chain. Get the ip of the other guy's wallet, remove or comment out all addnodes, put in the connect statement for ONLY that wallet, and voila! new chain

64.188.164.77  leave this one out. It's my ip, and it's going to go away tomorrow most likely, as I'm moving. It's a good node until I take it down, so no worries, but I'd take it out of your configuration to avoid any problems when I go offline. I'll probably be offline for like a week to ten days, or very spotty if I am online, and then I'll be a solid node again.

David, you probably have a better understanding of this than I do, but I think the NVCS adjusment will calm down in a few days, so if all of us use coin control and stage our staking, it likely won't go nuts again, barring further catastrophe.

Thundertoe or Defaced can correct me if I'm wrong here, but I believe they are going to release another wallet with checkpoints and exclusions very soon, but it will NOT be a mandatory update as this last series was because the checkpoints and exclusions will be the only change. That being said, there ain't no good reason NOT to update when that happens.

I personally think IRC is a disease, but in this instance, I have to agree with your assesment. Either that or a skype room for the duration of any emergency.

Probably wise for a little bit. Cryptsy is working with the devs, so they'll be straight soon if they're not already, but I'd honestly either wait for them to announce it or send them a ticket.

On the difficulty issue, I'm pretty sure it'll even out over time. Remember, it was a block being solved in the future (but accepted by the chain for unknown reasons) that caused all this grief in the first place. That screwed the difficulty calculations all up. the fix lowers the threshold for recalculating difficulty for a short period, then makes it so the first cause can't ever happen again. I would have expected it to be worse, honestly.

Those of you who have not staked yet, it actually might be a good idea to not let it stake for a few days, let things settle down. My own were a mix. some blocks staked pretty high, others, as y'all have noted, were significantly low. All in all, I'm happy with it. A little hit now to get everything straight is minor.

Hopefully it comes out before monday or after a week from monday (I'm moving, won't be able to upgrade.) Looks fantastic. Very nice work, sir!

anybody on minerpools having issues besides me? It keeps going "dead" in cgminer. Yet it seems to be ok from the stats page. I'm not having this issue with any other pool I mine.

You seem to like all the coins I like Maybe you should tell me which ones you don't, so I can avoid them 

I'm good with Zerostake too. Though it just occured to me that it might be better stylized as Zer0stake

I'm kind of stuck in the middle here

Which is ok, I volunteered. I'm not a good enough programmer to make a decent "hello world" program in anything other than basic, bash, and batch, so I pass on what I've gleaned and hope for the best.

so, the basic story  is that the original error took almost everyone by surprise, because when it happened Tek had been working flawlessly for a long time. Thundertoe didn't know where it went wrong (he's an ok programmer, but not a genius like some of these people), but figured out WHAT went wrong. Tranz figured out where. Defaced, who is friends with Thundertoe and I, and a Tekhead himself, volunteered to help out. We all had a lot of other shit going on at the same time, and frankly, mistakes were made. Along the way, several other people volunteered to help and  review code. Somehow nobody realized the lack of checkpoints and exclusions of old wallets until after the fact. In testing, everything worked fine, but we didn't realize (hindsight being 20/20 it's obvious now) just how much competition there would be for staking. Shit broke.

Y'all have been very patient, and even the angry accusations have come across more like venting. For that, I'm quite proud to be part of this community. We may get a bit contentious, but we get things done. ANY other coin that I've been involved in would have had it's community come unglued over far less. Other communities could learn a lot from this.

All I can say, from my POV, is that while mistakes were made, they are being corrected. Hopefully by tomorrow there will be a checkpointed and exclusionary wallet. And if not, it won't be long. Thanks again, all of you, for making this as easy as it can be given the circumstances. Should such an instance arise again, we'll do better at the fixes. Hopefully the coin will run on rails like it has for a long time now once again. Meanwhile, don't be too eager to sell, and we'll beat this bitch into shape.

It wasn't pointed at you, specifically. Just a general statement. It's something I see a lot. The coins that are long term successful, with few exceptions, do not get on the exchanges right away. Those that do spike for a minute, and drop, then everybody bails. After that happens, the real merits of the coin become more apparent. BTC didn't go that route, there were hardly any attempts even.

Exchanges are useful, but they tend to be the sole focus of most coins, which leads to an early death. Merchant support will drive the price way further, if it can be made to happen.

It's happening. Defaced is adding checkpoints and making that happen soon. It's currently being tested, but he went to bed. We needed to get a stable chain first, as I understand it.

Xhabit's pool is on the correct chain, so it's good to use as a reference for the block height right now. Thundertoe is contacting the people that run the block explorer. http://ppl.port-x.de/mops/public/index.php?page=statistics

if you have your wallet in sync and connected, you are a node. Just post your IP if you want people to use it as an addnode in their .conf file.

I had this happen once a while back. I ended up removing wallet.dat until it was fully synced, then deleting the new wallet and replacing it with the old one. It worked, but I don't know what caused the error. Hope it helps.

Another option could be to start the client with -salvagewallet, just being sure that the wallet.dat file is backed up. (I know you know that, Tom, just for other eyes )

It's a rather large chain Took me several hours from zero.

That is incorrect. It should be more stake for a longer time. I haven't calculated mine, but by eyeball it looks about right.

Can't recall who asked for it due to sudden brain fart, but my address is: BmmkHdBj3V9CuGqGPMfwXAB8NRWYiMjmCB

Too my knowledge, nothing has been changed in the staking formula, just in how it calculates difficulty. Defaced will know better on that than I. But that is my understanding of what changed. However, as screwy as things got, it may have dropped some weight somewhere. That's a guess, so don't quote me on it as any sort of fact

Don't forget to include yourself in that, press. And Argakiig,Tranz, me, and a few others who I'm not sure want to be mentioned Not bad for a volunteer effort, even if the first attempt went nuts.