[MOJO] MOJOv3 has been taken over by new devs

[kenscho]

the coins v2 works for v3? what will happen with the old coins?

[1714277254]

1714277254

[1714277254]

1714277254

[clickerz]

the coins v2 works for v3? what will happen with the old coins?

I dont get it...Is there another update? Since I deposited or transfered my MOJO to Livecoin, i didnt move it. I let it stay there until now. I didnt also read updates as I am busy. Hope devs will continue this coin as this is also a promising one. Any update?

[muchoman]

Things are moving to right direction!

"PoSv3 will be a fair for all system where you will have an equal chance to get a stake with a small balance as a large balance as long as you stake. To increase your chances of getting a stake you will need to run the wallet 24/7. Additionally, if fewer nodes are staking the stake reward will increase per node.
We hope that this system will ensure that nodes are always online."

[kenscho]

what is with the maxminers pool? they will fix theyr issue?

[EBK1000]

MOJOcoin v2.4 released

First I have to apologise for scant updates over the last few weeks. I have been busy on many fronts. I will make an effort to publish regular updates. Rest assured however that MOJOcoin is pushing forward and we are learning as we progress and we have made some decisions for the future as I will explain later. We have just released the updated code for MOJOv2.4 and also an updated Windows-Qt wallet. A new Mac-Qt will be released in the next day or so. You can always find the most up to date wallet releases at our GitHub repo.

https://github.com/MojocoinV2/mojocoin/releases
   
What’s new in MOJOv2.4?
We have added the Zapwallet Command to the wallet. This is a useful command that removes all wallet transactions that are not in the blockchain whilst reconstructing all confirmed transactions. It can remove “stuck” transactions and causes the wallet to “forget” any unconfirmed transactions so they will not be reconstructed. You can either add the -zapwallettxes argument on the command line:

mojocoin-qt-win-v2.4.0.0.exe --zapwallettxes=1

or

Add zapwallettxes=1 to the mojocoin.conf file.

PoW blocks will be disabled at block 200,000. This will help to stabilise the PoS system and hopefully provide more consistent rewards for staking. The PoW system was meant as a backup and to move the chain at a time when there were too few addresses staking. This should no longer be an issue.

Nodes are added for protocol version 90001 only. That means that older protocols will be ‘banned’ from the network. This aims to avoid forks with older clients.

5 min block time to reduce blockchain size. The initial block target time was 1 min but as the network is running the actual block time is closer to 30 sec. This creates a very large block chain very quickly and we believe this will be an issue as time passes. We have therefore set a new block time of 5 min.

All the changes will be ‘activated’ at block 200,000 which should be on or around 11th or 12th October 2016. Make sure you upgrade to MOJOv2.4 before that time.

Take care!

[GoldenEye]

With the release of v2.4 connection problems etc. should be solved and hopefully the system will run until we can move on to v3.

Ok, connection problems seem to be gone.

But there are still transaction issues.
Tried to send yesterday some coins. Different transaction sizes from 5k to 90k. That is now 12 hours so far, no tx was confirmed yet.

[Limx Dev]

With the release of v2.4 connection problems etc. should be solved and hopefully the system will run until we can move on to v3.

Ok, connection problems seem to be gone.

But there are still transaction issues.
Tried to send yesterday some coins. Different transaction sizes from 5k to 90k. That is now 12 hours so far, no tx was confirmed yet.

We need a clean network that is all. This is a fallback mode for safe the transaction. Please note Update 2.4.0.0 is a mandatory.

Best Regards Christian

[kenscho]

what is with the maxminer mojo pool?

We are investingating issues in the backend. Your shares and hashrate are safe and we will fix things ASAP.

Findblocks disabled, new blocks will currently not show up in the frontend
Blockupdate disabled, blocks and transactions confirmations are delayed
Payouts disabled, you will not receive any coins to your offline wallet for the time being

will the coins pay out?

[hagie]

With the release of v2.4 connection problems etc. should be solved and hopefully the system will run until we can move on to v3.

Ok, connection problems seem to be gone.

But there are still transaction issues.
Tried to send yesterday some coins. Different transaction sizes from 5k to 90k. That is now 12 hours so far, no tx was confirmed yet.

Same here - I tried to send transactions between 1K and 500K - all without success - they stay in the wallet. maybe it's the big amount of small transaction caused by 3 masternodes.

Regards

[EBK1000]

With the release of v2.4 connection problems etc. should be solved and hopefully the system will run until we can move on to v3.

Ok, connection problems seem to be gone.

But there are still transaction issues.
Tried to send yesterday some coins. Different transaction sizes from 5k to 90k. That is now 12 hours so far, no tx was confirmed yet.

Same here - I tried to send transactions between 1K and 500K - all without success - they stay in the wallet. maybe it's the big amount of small transaction caused by 3 masternodes.

Regards

This is under investigation

[EBK1000]

MOJOv2.4 - Mac-Qt

https://github.com/MojocoinV2/mojocoin/releases

[hagie]

With the release of v2.4 connection problems etc. should be solved and hopefully the system will run until we can move on to v3.

Ok, connection problems seem to be gone.

But there are still transaction issues.
Tried to send yesterday some coins. Different transaction sizes from 5k to 90k. That is now 12 hours so far, no tx was confirmed yet.

Same here - I tried to send transactions between 1K and 500K - all without success - they stay in the wallet. maybe it's the big amount of small transaction caused by 3 masternodes.

Regards

After approx 10h the transactions finaly ALL went through ...

Regards

[kripteka]

And when MOJO v3 will be work? If coins at livecoin must I do somthing?

[GoldenEye]

With the release of v2.4 connection problems etc. should be solved and hopefully the system will run until we can move on to v3.

Ok, connection problems seem to be gone.

But there are still transaction issues.
Tried to send yesterday some coins. Different transaction sizes from 5k to 90k. That is now 12 hours so far, no tx was confirmed yet.

Same here - I tried to send transactions between 1K and 500K - all without success - they stay in the wallet. maybe it's the big amount of small transaction caused by 3 masternodes.

Regards

After approx 10h the transactions finaly ALL went through ...

Regards

With me now too 

[altseeker]

With the release of v2.4 connection problems etc. should be solved and hopefully the system will run until we can move on to v3.

Ok, connection problems seem to be gone.

But there are still transaction issues.
Tried to send yesterday some coins. Different transaction sizes from 5k to 90k. That is now 12 hours so far, no tx was confirmed yet.

Same here - I tried to send transactions between 1K and 500K - all without success - they stay in the wallet. maybe it's the big amount of small transaction caused by 3 masternodes.

Regards

After approx 10h the transactions finaly ALL went through ...

Regards

With me now too 

Transactions went smooth for me as well using the latest version.

[GoldenEye]

what is the difference between --zapwallettxes=1 and -rescan ?

[marcelocoin]

same problem persists in version 2.4, without connection

[Limx Dev]

same problem persists in version 2.4, without connection

Please delete your "peers.dat".  And give your wallet time.

[cjmining]

Downloaded 2.4 connected, synced and is staking without a hitch. Cheers

[Jack Liver]

what is the difference between --zapwallettxes=1 and -rescan ?

zapwallettxes implies a rescan and cleans the list of wallet transactions, really useful when you have a stuck transaction because of mistake with a zero or too low fee or the actual problem of stuck transaction.