as I wrote above, kpx.io is not current
use the explorer inside iguana for more current data

we are deploying a hotfix across the ecosystem.

We promised not to sell the BTCD during the 1 year swap period.
Beyond that we did not promise anything.

In the even the BTCD chain stops advancing due to lack of stake, we might need to use some of it to keep the blockchain alive.

Komodo effectively purchased the BTCD, so it should be used to benefit komodo, but I am not smart enough to know how best to do that one year from now, so I decide to not decide until then.

Clearly we cannot be selling it during the 1 year swap period. That is all I know about the BTCD. That is what we promised. That is what we will follow

Just pushed hotfix.

Isolated the cause of an earlier issue, which prevented notaries from mining.

Restarted basilisk servers.

If you are running komodod, please pull the latest. If it doesnt resync automatically adding a -rewind=186000 (just one time!) appears to get it to sync right up.

kpx.io is not updating yet, but the blockchain is advancing. please check in the iguana explorer to find the current blocks

komodopool.com is back up and running.
coinexchange.io is updating

Not sure when kpx.io will be current. please do not complain that the blockchain is stopped, because kpx.io is not updating. I am sure it will be updated within a day or so.

The komodopool went on its own fork this morning, investigating the causal factor. seems like it accepted an early coinbase spend somehow.

I will be compensating komodopool and all its miner works for the downtime, just assuming the historical one third of blocks average so there is no lost earnings from this.

The overall network did not fork as all the notary nodes stayed in sync, but the network was flooded with a lot of transactions that did not validate, so got rejected, peers blacklisted, etc.

Separately, a bug in the notary miner was found and fixed. This only had the effect to slow down block generation a bit and extend the free-for-all period

pool is resyncing now
should be ready within an hour

only the wallets show the interest in realtime

I am not doing the GUI and iguana core supports it in full mode, but I have asked satinder

try again, basilisk should just now be running

Basilisk seed node issue confirmed, router is being restarted. all should be good in basiliskland in 10 minutes.

this is  a quirk in the basilisk bootstrap, which starts with a seed node and each request gets a random node. It then accepts some (not all) of the returned nodes and increases its list of available notaries to connect to. Over time, eventually all notaries will be connected to.

Once you get even just an additional notary, then the seed node is not needed. Recent gui added an init phase where it established contact.

However, currently for a node that is starting up, it does require the seed node to be active.

What this means is that you are better off not restarting iguana if you are already connected. Also if you get an error when starting up, it is likely just a short term problem and just try again later.

making this seed process a lot more redundant is one of the things on the todo list.

investigating.

looks like some networking issue with a seed server. If you already are running the basilisk it should be fine, but if you restart it, then it could be some troubles until this is fixed

try typing into the console:

Network has transitioned to almost normal blocktimes.

komodopool.com is providing a decent 40,000 sols and is getting about a third of the blocks.

We were able to downshift from the 200,000 sols test to free market forces.

Come to think of it,  I think the REVS snapshot was over on the 15th of January. Look in the BTCD addresses in your wallet, the REVS is there

ONLY the BTCD swapped before the snapshot deadline would be in the KMD payout address.

I will ask the ICO platform DB guys to look into this, it does seem like something is amiss

the payout request I had didnt have any REVS for you.
you swapped BTCD on the site before the cutoff for the REVS snapshot?

If it was before, the REVS will be in your BTCD addresses the moment of snapshot

did you check the REVS blockexplorer with your KMD address?

revs.supernet.org

If you received KMD, you most likely also received REVS at the same time. There is a chance that a small number of the 10,000+ REVS payouts got messed up, if so, plz PM me your KMD payout address, expected amount of REVS

We are in the 64 block mining freeforall started 184000 and this ends the 200,000 sol GPU mining test.

We will be ramping down the 200,000 sols in halves and during this transition, there will be slower than normal blocks.

Dont panic.

This is all expected and by 184065 blocks will resume at regular pace and if we can get the diff down to 300,000 or so, the new pools hashrate will supplement the notary blocks to sustain the one minute blocktime

of course, just put the address in

If you did a payout that was processed, it would have been processed.

it is a display bug,clearly REVS should be REVS and not KMD