Thanks for the encouragement, but I am not giving up with this one. We are planning a better code base and we will see what that will be. We are looking for stability so we can move forward with services.

The nodes are:
45.63.43.114
45.32.234.45

Having a patent is a big thing as there are no patents in the cryptocurrency space so if you have one you should show it and people will be very interested.

Can you link us to the patent for the PoW. If you already have a patent you are safe. In which country is the patent held and what type of patent is it?

You are entitled to an opinion but that does not mean that we are giving up on this, just because you don't like what is happening. This forum is always the same, people just moan endlessly and sit back and wait for their coins to appreciate. Very few people contribute to the value of the coins they hold. We were unfortunate that one of the devs involved in the V2 code delivered a dysfunctional code that we have to keep fixing. This is the reason why progress is slow and we can't focus on the utility and PR of the coin. It simply doesn't work they way it was intended and therefore there is a decision to move to a new code base and make sure that works so we can concentrate on other sides of the project.

There is no point at all in just posting complaints, we are working towards goals but it may take some time. We are not doing any PR as there are problems. We will do PR once we are happy that we have a good product.

I'm looking for privacy and the whole masternode idea is deeply flawed, wait and see what the long term effects are on DASH, DNET and others. The mixing, if and when it works does not provide any privacy and the mixing does not provide the privacy you think it does. There is a new breed to coins that will leave DASH and others behind. The reckoning will happen when the majority of people see that the coins that promote privacy, like DASH, does not provide this at all. I want MOJO to be something different than this code can provide.

It's not going to close down, we will continue. You must know that crypto goes up and down and there are no guarantees of price. We will take it into the next version which will be a new code base and away from all the issues and ditch the masternodes. If you want to get out, that would be your choice.

I'll check the nodes and update

Updates in progress, v2.4.5.0 is on GitHub so new wallets and updated OP soon...

You're missing my point again. The sprout file is unique to the Zcash genesis block. You will need to generate a new sprout file for your genesis block for the Zclassic clone, you can't use the same as they used for Zcash.

Of course, I mean to mine the genesis block only, how can you confirm that the security is maintained in the clone?

You used the exact same file from https://s3.amazonaws.com/zcashfinalmpc/sprout-proving.key

Does that work to verify keys and everything once you changed the code? I thought it was generated from the unique source of Zcash so if you changed the source you would need to generate another one?

I am interested in this, did you use the same sprout-proving.key (980MB) used by Zcash to verify keys etc. or did you generate your own? I am asking because this info seems to suggest it was created just for zcash

https://github.com/zcash/mpc

As there isn't full information on how this is generated, how did you do it?

Sorry, I will update the OP shortly

It would be useful with some further information on this. What address(s) did you have the coins in? In the first instance, try to do a -dumpprivkey for the addresses with the funds and then see, and then import it back and rescan. See if that works, if not let me know.

Have you checked the block explorer for the addresses? Your funds wouldn't be lost...

I'm off for a walk in Wales for a few days and won't be online until Sunday night. If there are any issues Limxdev might be around. Otherwise, just let it run for a while and we will see. 

Yes, I am aware and looking into it

BOUNTY / POSITION:
1. PR manager (fee negotiable)
2. Copywriter / marketer (fee negotiable)
3. Social media manager (fee negotiable)

I wanted to remind everyone that we are looking for the above to promote MOJO from where we are now and towards MOJOv3. It is thought as an on/off position that would require input once every two weeks in the form of a PR push through Twitter / Steemit / Facebook etc. and with regards to the copywriting, one article per month or every other month. Payment would be per piece of work and depending on your background and ability. We can discuss the details and the payment. If you want to do this but do not wish to participate here I have submitted job ads to Coinality as well.

BLOCK 200,000 'fork' w/ updates


At 06:10:17 (GMT -1) on Saturday 22/10/2016 we passed block 200,000 and the following changes kicked into action:

Zapwallet Command can be used for stuck transactions (conflicted transactions)
-zapwallettxes removes all wallet transactions that are not broadcast and not confirmed on the blockchain. It can therefore remove "stuck" transactions that will show up as 'conflicted' or 0 confirmation transactions that are not on the blockchain. It differs from -rescan in that it does not rebuild the "stuck" transactions. To use this you need to start the command line prompt:


Please always backup before doing any such operations

Blocktime target is now 5 min. It may take some time for the network to stablise so give it a few days

POW blocks are now disabled and there should only be PoS blocks created. This will hopefully make the rewards more stable.

All nodes below protocol 90001 will be locked out.

It's fairly common with forks in many coins if you're making changes that are not backward compatible or you want to introduce new features. I would suggest that if someone made a coin and never needed to make any changes it either suggest that they are able to predict the future and anticipate what they will need and what might need improvement or they do not develop the coin. Bitcoin has had forks as have many others "big" cryptos. It's not an issue, just update to latest version and you're fine.