[MOJO] MOJOv3 has been taken over by new devs

[Emerger]

Hi, I was running a MN which was working fine until this morning I woke to find it giving me the error:


    "status" : 2,
    "pubKeyMasternode" : "MTTNc16j3x2b84Ji8kgy6EtQAMkwSBS2G6",
    "notCapableReason" : "Could not find suitable coins!"


It's my first time running a Masternode, so I'd appreciate advice. Why would it work fine and then just stop working? The 200,000 coins are still in the account but look like they have been staking, which I'm not sure is expected. Any ideas? Thank you.

[1714252233]

1714252233

[1714252233]

1714252233

[1714252233]

1714252233

[cjmining]

Sent some coins to my wallet and not sure if i have a problem or not. Sent 4 transactions, 500 5000 5000 10000 all ok. They are confirming with 5 confirmations currently. I have also sent 3 more transactions, 5000 10000 10000, i sent these about 30 mins after the first 4. All of them say unconfirmed with a question mark at the side. When they arrived in my wallet the first sends only had 1 confirmation, at the time, but now have 5 and these transactions have none. What has happened to my 25k Mojo ?

TX ID of the not received coins.
7687c8004e8b52e3c3ac41075791b9707b627b0a0d70c6f291df79a71d7a95b8 (10k)
5c18abecedf8205e7b5cc0644a69f3f7094264460c31f98faad4594fa344b398 (10k)
59ec14ca0ab23ee77604525fdc78a410d37f68420ad13f5de3573d3d6ed3b9c8 (5k)

[Emerger]

I think the reason my masternode stopped working was that it staked the collateral coins. I wonder if there is a way to tell mojocoind NOT to stake the coins that are being held as collateral for the Masternode, but to go ahead and stake the regular balance?

[EBK1000]

Hi, I was running a MN which was working fine until this morning I woke to find it giving me the error:


    "status" : 2,
    "pubKeyMasternode" : "MTTNc16j3x2b84Ji8kgy6EtQAMkwSBS2G6",
    "notCapableReason" : "Could not find suitable coins!"


It's my first time running a Masternode, so I'd appreciate advice. Why would it work fine and then just stop working? The 200,000 coins are still in the account but look like they have been staking, which I'm not sure is expected. Any ideas? Thank you.

We believe that you need to put 'staking=0' in the controller mojocoin.conf file and in the masternode.conf file:
alias <space> address <space> genkey output <space> outputs output <space> index number of outpus (usually 0 if single)

[EBK1000]

Sent some coins to my wallet and not sure if i have a problem or not. Sent 4 transactions, 500 5000 5000 10000 all ok. They are confirming with 5 confirmations currently. I have also sent 3 more transactions, 5000 10000 10000, i sent these about 30 mins after the first 4. All of them say unconfirmed with a question mark at the side. When they arrived in my wallet the first sends only had 1 confirmation, at the time, but now have 5 and these transactions have none. What has happened to my 25k Mojo ?

TX ID of the not received coins.
7687c8004e8b52e3c3ac41075791b9707b627b0a0d70c6f291df79a71d7a95b8 (10k)
5c18abecedf8205e7b5cc0644a69f3f7094264460c31f98faad4594fa344b398 (10k)
59ec14ca0ab23ee77604525fdc78a410d37f68420ad13f5de3573d3d6ed3b9c8 (5k)

My best guess is that they haven't been broadcast yet, wait for another few confirmations. The chain is moving slow but it is moving now.

[hagie]

I think the reason my masternode stopped working was that it staked the collateral coins. I wonder if there is a way to tell mojocoind NOT to stake the coins that are being held as collateral for the Masternode, but to go ahead and stake the regular balance?

Put staking=0 in the conf file this disable staking. This is the best and easiest way until this bug is fixd.

Regars

[hagie]

Hi, I was running a MN which was working fine until this morning I woke to find it giving me the error:


    "status" : 2,
    "pubKeyMasternode" : "MTTNc16j3x2b84Ji8kgy6EtQAMkwSBS2G6",
    "notCapableReason" : "Could not find suitable coins!"


It's my first time running a Masternode, so I'd appreciate advice. Why would it work fine and then just stop working? The 200,000 coins are still in the account but look like they have been staking, which I'm not sure is expected. Any ideas? Thank you.

We believe that you need to put 'staking=0' in the controller mojocoin.conf file and in the masternode.conf file:
alias <space> address <space> genkey output <space> outputs output <space> index number of outpus (usually 0 if single)

You ony need staking=0 if you let the controller running. You must not put it in the masternode.conf. if the remote masternode is started just TURN OFF the controller and no staking will happen.

I will create a small tut about the two ways to du. MN online soon.
Regarcs

[Beoga]

Am I right - if there are no masternods in MOJO network - no POS?

[EBK1000]

Am I right - if there are no masternods in MOJO network - no POS?

There are three running but no PoS blocks for a while, we are investigating if the PoS is working the way it should

[EBK1000]

Quick update:
1. I have the initial contractor reviewing the code and an additional dev. looking at the problem
2. I have put out an ad (on BCT) for an additional dev with in depth knowledge of PoS / MN to do paid work with the code
3. If this does not resolve our issues I will hire another freelancer with provable credentials for the job
We will make this work

[Beoga]

Am I right - if there are no masternods in MOJO network - no POS?

There are three running but no PoS blocks for a while, we are investigating if the PoS is working the way it should

May be the problem is because no availible masternods in Mojocoin network folder?
I mean on some reason wallet doesn't see any masternod and can't POS.

[FogHorn_LegHorn]

Quick update:
1. I have the initial contractor reviewing the code and an additional dev. looking at the problem
2. I have put out an ad (on BCT) for an additional dev with in depth knowledge of PoS / MN to do paid work with the code
3. If this does not resolve our issues I will hire another freelancer with provable credentials for the job
We will make this work

Presstab the dev?

[EBK1000]

Quick update:
1. I have the initial contractor reviewing the code and an additional dev. looking at the problem
2. I have put out an ad (on BCT) for an additional dev with in depth knowledge of PoS / MN to do paid work with the code
3. If this does not resolve our issues I will hire another freelancer with provable credentials for the job
We will make this work

Presstab the dev?

I'm speaking to him as well, pls let the MN run for now, we are working hard to get this fixed.

[hagie]

Hi all,

at the moment we have 3 MN's running. They are needed for PoS because on every generated PoS Block there need to be at least ONE MN to send fees to.

mojo@vmd13444:~$ mojocoind masternode list
{
    "a0743510dc19b802aa47969c3f4e8e76cd6b1f38d60e1c7d12e58991c6c919b4-0" : "ENABLED",
    "062a8afbb689a54ad271f48124002e3e3b3a5d16c79cec92389b7f346d623bd7-1" : "ENABLED",
    "da977953b56dd0ba52704adb51668312eeea8c8795c07135da2b85012d8a2245-0" : "ENABLED"
}

PoS Blocks are generated (found) by nodes with mature transaction which are at least 24h (min staking time) untouched in the wallet. Since Blocks are also need to for confirmations on transactions this all is a bit slow at the moment.

We had some transactions yesterday which hopful will be mature soot to start staking and finding blocks - that was the reason for my request to get some coins, split them and distribute them to other staking wallets. Since PoS is slow we have to wait longer for mature coins. It's like a Hen - Egg paradoxon ...

regards

[FogHorn_LegHorn]

My kung fu strong.

[EBK1000]

I am fully aware of the situation and that the chain is stuck and we are working on solutions. We will not give it up and will find a solution to drive this forward. If MNs could please keep running for the time being that would be useful. I will update when I have something to update about. If anyone can read code and wants to help then please do, and if you find a problem please highlight but be specific.

We are working on this so there is little point in making complaint posts unless you have a specific idea or have found a bug.

[FogHorn_LegHorn]

I am fully aware of the situation and that the chain is stuck and we are working on solutions. We will not give it up and will find a solution to drive this forward. If MNs could please keep running for the time being that would be useful. I will update when I have something to update about. If anyone can read code and wants to help then please do, and if you find a problem please highlight but be specific.

We are working on this so there is little point in making complaint posts unless you have a specific idea or have found a bug.

Thanks for the update!

[bigs21024]

I am fully aware of the situation and that the chain is stuck and we are working on solutions. We will not give it up and will find a solution to drive this forward. If MNs could please keep running for the time being that would be useful. I will update when I have something to update about. If anyone can read code and wants to help then please do, and if you find a problem please highlight but be specific.

We are working on this so there is little point in making complaint posts unless you have a specific idea or have found a bug.

ok is that why i have lost coins again that never made it Status: 0/unconfirmed
Date: 7/23/2016 14:24
To: MGvJAPj8kzCxmw9MX9xm9w9UN7SNf7jjAF
Debit: -23014.00 MOJO
Transaction fee: -0.0002 MOJO
Net amount: -23014.0002 MOJO
Transaction ID: 056a8a880ecfb5f4c08486d1cd31ae61b8001f70b52067e46c4dac9c94328dfc-000

[EBK1000]

IMPORTANT UPDATE

We realise that we are effectively stuck at the moment and that we will not be able to move the chain effectively so this is what we will do:
1. Update the protocol version with an immediate hard fork to activate X11 PoW blocks to move the chain.
2. We will burn 5,000,000 MOJO to take the total down.
3. We will activate X11 PoW mining with a block reward of 20 MOJO per block for 6 months and keep PoW enabled for a while as a backup measure to make sure we never end up with a stuck chain again.
4. We will remove the restriction that requires a master node to be running for other wallets to stake.

We have made a review of the code and believe that the MN system / PoS is correct and will work post hard-fork.

We expect to implement this on Tuesday 26/07/2016 evening time (GMT)

Since there is no moving chain and the wallet.dat will be compatible with the new post hard-fork wallets this should not present a problem for anyone.

This will ensure that we can drive The Mojocoin project forward and not get bogged down in issues like these. We can then focus on the utility of MOJO and move forward with the roadmap.

I will update the OP, Twitter, blog etc. shortly.

Links to new wallets will be up hopefully by Tuesday evening. Hang in there...

Thank you

[BanzaiBTC]

IMPORTANT UPDATE

We realise that we are effectively stuck at the moment and that we will not be able to move the chain effectively so this is what we will do:
1. Update the protocol version with an immediate hard fork to activate X11 PoW blocks to move the chain.
2. We will burn 5,000,000 MOJO to take the total down.
3. We will activate X11 PoW mining with a block reward of 20 MOJO per block for 6 months and keep PoW enabled for a while as a backup measure to make sure we never end up with a stuck chain again.
4. We will remove the restriction that requires a master node to be running for other wallets to stake.

We have made a review of the code and believe that the MN system / PoS is correct and will work post hard-fork.

We expect to implement this on Tuesday 26/07/2016 evening time (GMT)

Since there is no moving chain and the wallet.dat will be compatible with the new post hard-fork wallets this should not present a problem for anyone.

This will ensure that we can drive The Mojocoin project forward and not get bogged down in issues like these. We can then focus on the utility of MOJO and move forward with the roadmap.

I will update the OP, Twitter, blog etc. shortly.

Links to new wallets will be up hopefully by Tuesday evening. Hang in there...

Thank you

Great news...

Some other things that could help keep the network more stable..

Lower minted confirms.. This will release your coins sooner to start gaining age again..
And lower the minimum stake age to 6 hours or so.. If not many people are staking, a 24 hour stake age can be troublesome if people dont have many mature inputs..
Add a blockplitter tool to split your inputs for staking..(Or manually send many transactions through daemon/console)
Rent a few cheap vps's to stake in the background...

Then again, you basicly solved a lot of issues with the solutions you came up with..