Block explorer is back up and in sync with the pool.

I got everybody's messages and emails.  I will recycle the seed nodes and the block explorer and unstick the network.

I could turn on automated checkpointing as well, I am reluctant to do so because it adds some centralization, but it might be some extra protection.  I will wait for feedback from you all before going this route.

A big part of the problem is that there are still a lot of people trying to connect with the old version of the client and it periodically overloads the seeds and is causing synchronization issues.

As another poster noted, I did lose my job over all of this coin stuff ;-)  So, I have been heads down spinning up a company.  I am building an exchange and working on getting some project work.  But I am tending to the coins as well.

Give me an hour or two to do some maintenance on the servers and lets see if that helps.  I will also push the updated build today and then after that based on your feedback I can either turn automated checkpointing on as a temporary measure, or leave it off.

Dev lost job and is trying to start company in real life.

I have not abandoned Version but I am tied up with "real life" stuff e.g. job situation.  That said, if mindfox and crew want to put development resources/effort in and submit pull requests I will not turn them down as it only helps everybody.

I started going down a path that is, unfortunately, very time consuming.  The problem is because of our fork issue, there is kind of what you can think of like a "plug" trying to go through a pipe and clogging it up - which is a large chunk of orphaned chain that needs to be processed through and then things go on - but this processing consumes a huge amount of resources and brings the RPC interface etc. to its knees, which causes a big operational problem for the pools.  So, part of the solution is to get the codebase onto leveldb as it is still on bdb.  Unfortunately, this is not so simple to achieve.  There are also some threading improvements that could be made, etc.  One possible solution that may be easier, is to take a codebase that is already on leveldb with recent updates, and then port the Version coin parameters, difficulty algorithm, and block reward algorithm over into it.  This may prove faster to implement than bringing leveldb into the existing code base.

For normal users its not a blocking issue, but for pools who depend on high RPC throughput it is a problem.

There is no fork...  The block explorer and all nodes under my control are all in agreement with cpu-pool etc.  I do notice there are still a LOT of folks (a LOT of folks!) trying to connect with the old version and getting banned by the nodes, and as a result there is some network slowness - and to be honest I'm kinda wondering who/why that is because all it is doing is clogging the network resources - if you are one of those people, update your wallet, it will help make the network faster for everyone.  If you are having trouble catching up you can try deleting your peers.dat and letting it seek out nodes again.  You can also try the things already mentioned in the thread and you can run the wallet once with the -rescan command line argument.

The block explorer is up to date now.  It will go down for a little bit maybe later tonight so I can reload the database.  There may be some data and transaction details unavailable in it as I forgot to turn on transaction indexing, hoping a reload will provide a more complete data set.

I haven't been on here as much as I have "real life" stuff to deal with but I am checking in/keeping tabs from time to time and keeping the infrastructure maintained.

I completed a few of the features that were requested and will push a minor release out when I get a chance...probably this weekend.

Block explorer is now available at:

PROBE Signals

Its a small box at the moment, I can bump up the resources if needed.

I've got the block explorer up and working, after much hacking of bitcoin-abe.  Just working on making it look cool and then I will drop the URL.

I did the unlock button in the toolbar, and looking into putting the minting status in the taskbar, maybe an icon but at a minimum I can put some status text.  I'll drop another minor optional update once thats done tomorrow.

You can do the inverse, which is to set a reserve amount of coins that should not be staked that you want to make sure you have available for spending, by adding this line to your PROBE.conf:

Where 100 is whatever amount you want to keep available.

PROBE 0.8.9.2 Windows QT Wallet

PROBE-0.8.9.2-Windows.zip (Mega.co.nz link)

Please update your wallet.  Make a backup of everything in your PROBE data directory (c:\users\you\appdata\roaming\PROBE on Windows 7/8, ~/.PROBE on Linux) and then remove everything except for your PROBE.conf and wallet.dat.  Then add:


to your PROBE.conf and run the wallet and it will redownload the blockchain.  Afterwards close the wallet, remove the connect= line, and restart the wallet.

I have pushed the updated code to git.  All of the seed nodes are updated.

This update bumps the required protocol version so that the new version will only talk to other nodes of the same new version.  I also added a bunch of checkpoints for the correct chain.

I am going to build the Windows wallet now and then you'll be able to connect up and resync.

You may need to redownload the blockchain.  You can easily do this by making a backup of the blk*.dat files and database directory within your PROBE data directory, and then removing them from the PROBE data directory.  Make a backup of your wallet.dat and DON'T remove it.

Add this entry to your PROBE.conf, run the client once until it has completed the download, and then you can remove the entry and go on as normal:


This will connect you up to one of the seed nodes from which you can pull the right data.

The new version is 0.8.9.2.  Will post an update once the Windows QT wallet is ready.

Thanks!

We will have this stabilized and CPU-Pool on the right track within a few hours.  Stand by.

Also I'd love to start collecting a list of things from the community that you would like to see.  Top of the list right now is the Abe based block explorer and paper wallets.  Beyond that, what would you like to see?  I know I would like to have an Android wallet, and was going to work on that this weekend.  What other ideas do y'all have?

I'll do another build with some more checkpoints later today.  The problem is that CPU Pool was off on a fork for awhile before they updated their daemon.  I'm guessing they did not rescan the blockchain.  The coins between block 8600 and when they updated will have invalid difficulty.

What you can do is add this line into your .conf:


or run the wallet or daemon with -checkblocks=0 on the command line.  It will take a long time to start up, as it will doublecheck every block in your chain.

Supernova was updated right when the new daemon was released, and the exchange shortly thereafter, but everyone seems to be piled up on cpu pool.  Its not good to have all the hashpower concentrated on one pool.  Spread the love around to help distribute the hashpower.

I'm tempted to set up a pool myself to distribute the hashpower more...one thing I have not done yet is operate a pool.

Yes, I provisioned the server to host it and the paper wallet.  Should have it going in a day or two.

There are over 250 miners mining at CPU Pool right now according to their dashboard.  You are mining at your own risk at the moment as you are off on a fork and you will lose all of your coins.  Switch to the other pool on Supernova or wait until CPU-Pool updates their daemon.

Looks like CPU-Pool has not updated yet, if you are mining there you are mining on a fork.  The current network diff is 33.8 at block 8628.  Suprnova's got the right diff and looks good.

I'm seeing a fair number of you on .8.9 in getpeerinfo.  The pools have already updated.  Please update to 0.8.9.1 now if you haven't, we are past block 8600 and the diff has come back up.

If you haven't updated yet you should update NOW.  We are going to hit block 8600 pretty soon.

If you have not noticed, now that PoS blocks are minting the difficulty has dropped dramatically.  This is a side effect of the KGW interaction and will go away when we hit 8600 and then the diff will come back up to par again.

You probably have maybe 10-15 minutes before it cuts over at 8600 if you have not updated yet.

I was looking at this too because I didn't see anything to deal with the really long block separation exploit, but then noticed he put a box around it at the end so it will only allow up to 3x adjustment in either direction.

IMPORTANT! UPDATE BEFORE BLOCK 8600

New PROBE version 0.8.9.1 is released.  Source is updated in github and the new Windows wallet can be downloaded here:

PROBE 0.8.9.1 Windows (Mega.co.nz)

This update has a lot of stylesheet fixes for colors on Windows.

In addition, there is a hardfork at Block #8600.

Based on what I have experienced with another coin and information that has come to light with the Kimoto Gravity Well, I have made a pre-emptive move to back out the KGW at 8600 for everyone's protection.  This gives a few days notice for everyone to get updated.

I also added some checkpoints.

UPDATE AS SOON AS POSSIBLE

Thanks!

I've been busy dealing with a situation with another coin, and assessing some potential issues.  As an outcome of information from that situation I have made the above very important update for v0.8.9.1.

I am not shopping this coin around to exchanges right out of the gate because I don't want my coins to be pump and dump coins.  I try to do something unique and different and make things that will stand through time with good infrastructure support.  Right now the coin is on nxt-e, which is a nice but small exchange but it seems like they are growing.  I like them, and other exchanges will pick up PROBE naturally over time.

PROBE will be getting a few things soon as things settle down - block explorer, paper wallet and social media.  Need to come up with a cool paper wallet design