Sorry about the delay, I've be waiting until I've found and resolved the issue so I can do a one time correction. Unfortunately it happened again last night so now I've put in code to attempt to detect the issue when it happens and autocorrect. This means going forward the bug, while still existant, won't have an effect. Now that that's done I'll revisit the uncorrected blocks and do a fixup. What I'll probably end up doing is a btc payment to all the affected accounts based on the affect the extra blocks had.

Those short blocks aren't found. It's a bug in the pool software I'm using that occasionally reports a double finding of a block. I'm trying to track it down. If you read the thread on the HHTT pool they're having the same issue (I use the same software as them in the backend for Stratum users).

Here's the discussion on my pool about the same same short block/orphan issue.

Without actual commerce in ixcoin there won't be much in the way of fees so it's unlikely that the current large miners will continue mining.  Enthusiasts will likely still mine so the coin will probably continue. One of the reasons for ixcoin, if I recall correctly, was to see what would happen when a coin stops having a subsidy to get an idea of what will happen with bitcoin.

I have had the same on my pool which uses the same stratum software as HHTT. I wonder if there's an issue somewhere. I'd get a 'block' with 20 seconds of another which is never submitted to the network.

BTC increases when a block is found. Note the 'Round Duration' on your page. It's over 24 hours. That's why you haven't had an increase - no blocks have been found in that 24 hours.

Back up now.

Yeah, just went down due to a bitcoind crash. Bringing it up now.

Withdrawals should be working. Email admin@bitparking.com with account details if you have issues.

I've not finished it yet but I will complete it soon.

Be careful about the blockchain you get. A while back I had numerous issues getting the right chain and my client refusing to reorg to the correct one.

i0coin is tradeable on Vircurex now.

I've removed the two erroneous blocks from the system and put a note on the front page of the pool about it. I'll adjust the DGM payment amounts this weekend and comment here when done. I've put some logging and changes in place to track down where the double submission might be occurring.

You won't be penalized for it - when I've tracked it down I'll reverse the effects.

Technically it's not "known good" until 120 confirmations because that's when the pool gets paid.

I haven't looked at that specific case, I'm commenting on the 'should have gotten X shares in a block' remark. I'll take a look at the block in question and see if there's anything unusual about it.

The duration times shown on the website are actually the times the website got notification of the solved block, not the time the actual block was solved. It can be off by up to 60 seconds depending due to caching in the services that notify the database of shares and blocks found. That block duration was probably more like 10 seconds.

I'm not at all upset or shocked that people would be upset. By the same token I would hope others aren't shocked and upset to know that I'm being careful with the situation involving large numbers of namecoins so as not to make further mistakes. I'm not at all prepared for the task of dealing with so many angry emails - this was just a hobby project I set up when coins were pretty much worthless - and I admit I'm not great at responding to them. I'd rather just do the job of fixing things.

I have had updates of progress here and here. I respond to polite emails about progress when I can. A large number of people have had their funds restored. A large number haven't - in particular ones involving trades around the day of the crash. Corruption in the trade data, corruption in the wallets, has made things difficult. My current step has been to work out what namecoin funds cannot be recovered, and then work try to work out a payment of existing funds followed by some form of ongoing payment for the remaining amounts I wasn't able to recover. At that point I'll put an update on the website with details so users can know where there stand.

The exchange had backups but unfortunately I was caught out by the flurry of activity with the pumping of prices that occurred over the few days around the crash. There were a significant number of transactions during the day of the crash that occurred after the last backup. Hundreds of thousands of namecoins were traded. The disk data was corrupted and I've not been able to recover everything. Recovering the state of transactions and funds has been, and continues to be, a significant amount of work. I'm trying. Yes, I'm not fast as people would like but I'm doing the best as I can. It was obviously a mistake keeping the namecoin exchange going once the price of bitcoins and namecoins went beyond hobby status.

That said I'm still processing data. I've slowed sending refunds out while I process the state of the unrecoverable data and will pay out what exists and then some form of ongoing payment system for the unrecoverable funds.

I can temporarily disable i0coin and groupcoin generation which I added around August 6 and see if that makes a difference. If you can confirm that you're still mining and can check if disconnections still occur I'll make the change and see if it affects it.