UPDATEIssueI've investigated what's going on with the KOBO blockchain. There's no quick answer as to what's occurred here. My current thinking is that there are multiple forks existing right now because of the very low transaction volume. It happens...
Proposed Solution- I've spoken with CryptoID (https://chainz.cryptoid.info/kobo/) and Coinomi (https://www.coinomi.com/asset/kobocoin/). We've agreed that the client needs to be updated.
- The updated client will use an updated checkpoints file to point all clients at the right chain (up to block 2575000). This is not the solution used in the newer v20 bitcoin codebase, but kobo is still at a much earlier codebase, so it's a valid solution until kobo is upgraded. While transaction volume is low, it may require regular client updates (maybe every 6 months) to maintain blockchain integrity.
- I'll build 2x kobo nodes in the cloud (one with a koboseeder - https://github.com/kobocoin/koboseeder) for 24/7 operation. This should help. I used to have 3 cloud nodes running when the android wallet was in use but I discontinued them once we got onto Coinomi. They're not cheap!
- Update Github and inform community, CryptoID, Coinomi, and YoBit (if they'll listen) to update their clients.
This should hopefully resolve the issue. I should have github updated by the end of this week (I want to test locally before uploading). I'll then be in contact with Coinomi and CryptoID to update and regen their blockchains, and hopefully have the 2x new nodes fully operational by the end of next week (Sept 12th).
My block height while writing this is
2575909TT