bitember working?

//e

looking good

[2014-03-13 11:48:14] Network difficulty changed to 2.91k (20
[2014-03-13 11:48:14] Stratum from pool 0 detected new block
[2014-03-13 11:48:18] Accepted 03137b42 BFL 0c Diff 83/64
[2014-03-13 11:48:20] Accepted 00dd4a76 BFL 0f Diff 296/64
[2014-03-13 11:48:26] Network difficulty changed to 2.91k (20
[2014-03-13 11:48:26] Stratum from pool 0 detected new block
[2014-03-13 11:48:31] Accepted 003b9aad BFL 0e Diff 1.1k/64
[2014-03-13 11:48:41] Accepted 00f1e9d9 BFL 0g Diff 270/64
[2014-03-13 11:48:43] Network difficulty changed to 2.93k (20
[2014-03-13 11:48:43] Stratum from pool 0 detected new block

As I said, the coin is still under testing. We have our stratum open for testing purposes only.
Since no announcement has been made that we're good to go, I imagine that those blocks will be deleted from the chain once those tests have finished.

I would like the administrators of all pools to come to irc #versioncoin on freenode.

Solo mining for what? Blocks found will not be calculated...

I think we're at "Something is still busted" right now.

mine stopped at block 58211.. fresh install using the connect command in conf file.
still says out of date.

A lot of progress has been made and we're very close to a solution. Please bare with the coin dev and the people who assist him. Please believe that most of us haven't slept for days now, working on this, trying to find a permanent solution instead of just "patching" things up.

I have one question.I buy version coins on NXT market .Then I send them to my wallet two days ago and they are not arrived .The same thing happen with transfer from pool.
Thanks

Keep up the great work guys.  I'd rather wait for stitches then live with a band-aid if it's stitches we need.

You are correct in that it is easy to exploit.  But, the PoS in the coin is also its own enemy.  One way to think about it is that the coin has been executing this exploit against itself.  We solved that part of the problem.

We are working though it.  The root cause of our issue is a problem with the way the KGW algorithm interacts with PoS blocks.  As we've been peeling back the layers of the onion and solving problems we are uncovering other potential issues and a situation where the formula won't produce the proper result.  We think we have a workaround for the latest formula issue we uncovered and need to implement and test.  It is a situation where the stops and restarts of the blockchain result in the exploit noted above taken to an extreme degree against itself (extended future time warp).

Trying to get the chain back up as soon as possible, but also want to make sure once its up - its up and we don't have anymore issues.  Need to make sure it is reliable.

On top of all that, what mindfox mentioned is true, I know I personally haven't really slept in the last 4 days and my body is probably going to give out on me shortly, and I got some bad news to deal with in my personal life earlier today which is the icing on the cake.  So, we are literally working tirelessly (or perhaps, tirefully ).  We will test the latest fix and depending on the outcome of that I am going to make a decision on whether to back out KGW for now or not so we can get back up and running.  At this point I gotta take a short break and catch some zzzz's or I'm going to give myself a stroke

I appreciate everyone's patience, I know Version picked up a fair amount of popularity and everyone is eager to get back to mining and trading, and I am very grateful for the interest.  We are going to make sure it is solid and then get back in business.  Just a little more patience and we should be in good shape.

When will start pool mining ?