Both my wallet and the explorer (https://explorer.innovacoin.io) seem to be stuck with the last block being 499999 (dated 29th May 2020).  Is this a bug in the wallet or just a lack of transactions?

Just so people reading this know - the chain is still running, just slowly and with very few transactions.

If you want to make sure that you are on the right chain and up-to-date, I have uploaded a zipped copy of the 'blocks' and 'chainstate' folders here: https://www.kethiel.org.uk/monoeci/monoeci-chain.zip [372 MB] and my peers.dat file: https://www.kethiel.org.uk/monoeci/peers.zip [401 KB].   Before unzipping either, back up your current data directory.  If you are going to extract monoeci-chain.zip, move or delete the 'blocks' and 'chainstate' folders in your data directory first.

DO NOT DELETE YOUR WALLET.DAT!

When you start the Monoeci wallet after this, you have to wait until the next block is added to the chain before it will finish syncing.  Due to very few transactions being sent currently, and very slow mining of blocks, this could take a few days - you'll need to leave it open if you want it to sync (and you'll have to do the same again if you close the wallet).

Like the rest of us, their wallet is probably stuck.

In other news, apparently Monoeci is getting delisted from Crypto-Bridge, Coinexchange is closing down, and the ongoing saga of Cryptopia - well, who knows when anyone will be getting anything back from their (or in what form).

For whatever good it does, I have forked this coin's repository to https://github.com/gwestwood/monoeci-core and merged in an outstanding pull request to fix a regex vulnerability.  Note that I am not an experienced crypto developer and I can't take on maintaining this wallet, but if other devs will join with me to work on this we can at least get a working wallet to get the network moving again...

I don't have any addnodes added, but my current peers are:


        "addr" : "80.211.45.157:10086",
        "addr" : "94.177.249.141:10086",
        "addr" : "91.243.97.63:10086",
        "addr" : "91.90.230.185:10086",

(That's not many...)

91.243.97.63 is the currently running Block Explorer.

Not necessarily.  Let's all compare block hashes for a recent block:


> getblockhash 867665
3984dec64238c71e960ddebbb9ef9cd57eff765f84644bbb61398673123b6d27

If we are all on the same chain, this value for block 867665 should be the same.

Edit: I can see 13 MNs at this time.

As a side note, I suspect I'm on a fork again, as I can only see 16 masternodes now.  Can someone else tell me what you can see?  Thanks.

I have now created a Masternodecoin Community Team organisation on Github and forked the repository there: https://github.com/masternodecoin-community-team/masternodecoin
I've applied some minor text changes (you can see the list of changes at https://github.com/masternodecoin-community-team/masternodecoin/commits/master - mine start today on the 7th July).

I will add access for others to commit code once we have actually formed a team and worked out roles, but you can submit patches as pull requests, or report issues on https://github.com/masternodecoin-community-team/masternodecoin and I'll take a look at them (but I would appreciate pull requests, as I am not a wallet developer).

In the long-term, it might be better to switch to a different codebase and perform a swap like IdeaUpdater was talking about, but this should be decided as a team and will involve a lot of work and preparation that I cannot do myself.

I've merged the latest changes in the repo into my fork from the MasternodeCoin repository, but not tested if that is able to compile and run without issue.

There are many instances of community takeovers of a coin.  The main thing is to get the majority of the network to move to the community version of the wallet.  This will first require various things to be done in the code before the community release to ensure that the new team can manage the sporks, possibly freeze/block/take-over the old developer funds, and obviously fix any major bugs, before deciding a new roadmap.

You can test it, but you can't transfer your coins to it (different chain) nor do anything else with it (I tried to mine on that chain, but that doesn't seem to be possible now).

I went down from over 200,000 coins to about 65,000.  All my staking rewards since 14th November 2018 (until I gave up and stopped running the wallet in mid-January) were on another chain, so were lost.  I'm still worried by the regularity of rewards as to whether I am already on a fork again.

Can someone confirm their block height and hash?
As at Tue Jun 18 13:53:04 2019 my block height is 841038.

> getblockhash 841038

f88d34c96ee4b1ab292c25484389549e71611d5ab55cac3820a2e03b086abb47

You won't have any coins in the new wallet as it is a fresh chain and, without any further information by ideaupdater on swapping to the new chain, the new wallet has no use or function.

I suggest you use the option to download all the .rar files inside a zip file, then extract the .rar files from the zip, and finally run extract on the first .rar file, which should extract from the other partial .rar files.

Try the official Github: https://github.com/masternodecoin/MTNC-client-blockdate/raw/master/MTNC%20Client%20v4.1.0.0.rar (You will need a tool like WinRAR to extract).

VirusTotal scanned and shows as clean: https://www.virustotal.com/#/url/f7cd0102d20a0d35cced6b839935d2b2caf342f1f439df7a5247e4d8e1ed454e/detection

However, we cannot use this wallet until there is a swap, so pretty much this can be ignored for now.

Hello Rasto.

What Ideaupdater didn't make clear enough is that the wallet released there is for the new chain, not the current one and, as such, you cannot import/transfer your wallet to it.

Basically, you can ignore that new wallet until we know there is a running chain and how to do the swap.

What is the swap ratio for old MTNC?  Given that MNs currently only require 50,000 MTNC, if the ratio isn't 1:10 for existing holders there will be a number of upset MN holders.

Edit: Ah, I found the relevant post confirming that it is 1:10:

Indeed.

@Ideaupdater - Please can you release an updated version of the Masternodecoin wallet with up-to-date checkpoints and kicking old versions off the network, so that we can all get back on the same chain again?

Yes, a lot of people will lose rewards, but they will do anyway once you decide what chain you will support for the swap and better to have that pain now and be able to get on with getting rewards on the right chain from this point onward until your intended swap, than the mess and confusion that there is now.

Can someone post some working peers (running version 4.0 or 4.1 as there still seem to be a number of old wallets out there) from what they *believe* to be the valid chain, please?  I can't sync and am currently 12 weeks behind (gave up trying to sync back then).

I have three peers:
```
188.165.251.199:10086
159.69.36.241:10086
80.211.59.224:10086
```

Edit: It looks like these may all have different heights anyway, * sigh *.

Edit 2: After leaving the wallet running for 15 hours, all I have is a debug.log full of mentions of "ORPHAN BLOCK" and still 12 weeks behind. :-(