Quote from: drays on January 30, 2018, 06:45:00 PM

Quote from: bakra on January 30, 2018, 12:09:04 PM

Quote from: drays on January 25, 2018, 02:37:14 AM

Quote from: bakra on January 24, 2018, 07:01:15 PM

Quote from: drays on January 16, 2018, 11:53:42 AM

Quote from: bakra on January 16, 2018, 09:34:44 AM

Quote from: drays on January 16, 2018, 08:40:14 AM

Quote from: bakra on January 15, 2018, 06:30:09 PM

I have one wallet controlling multiple masternodes.
Can I use this wallet for staking as well or do I need a separate wallet for staking?

Do you use that wallet only for controlling masternodes (start/stop etc), or also for running them? In other words, do all your masternodes use a single (the same) datadir, and do you run just single instance of 8bitd daemon opening multiple TCP ports (one per MN)?

On the vps they have their own datadir. Up untill now the local wallets had their own datadir as well. As that uses too much resources I compiled a wallet that can control multiple masternodes from one wallet.
I have to see if it works as expected because I set it up yesterday for one wallet to test. Did not receive rewards yet. If it works I'm going to control the other wallets on the vps from the same local wallet

Ok, thanks for clearing this up! I was wondering if there is a way to run multiple masternodes using just a single hot wallet. I was trying to figure that out few years back and found it is impossible, so your previous message confused me a bit.

The setup you have now - multiple hot wallets for MN (with 0 coins sitting there), and a single cold wallet (with all the coins) controlling the MNs - is exactly what I was using back then - and it worked perfectly, so yours should work too if everything is correct.

How to see from which hot wallet the rewards are coming? All incoming rewards have the same name so how can I see that all MN's are paying rewards?

Well, as far as I remember, the rewards are payed to the masternode collateral address. So you could check your masternode collateral address balances, and see if they are bigger than 112, and by how much...

I got 4 MN's on the vps and 1 controller wallet.
When, in the controller wallet I type " masternode start-many" I get the following reply:

{
"overall" : "Successfully started 4 masternodes, failed to start 0, total 4",
"detail" : {
"status" : {
"alias" : "MN8BIT1",
"result" : "succesful"
},
"status" : {
"alias" : "MN8BIT2",
"result" : "succesful"
},
"status" : {
"alias" : "MN8BIT3",
"result" : "succesful"
},
"status" : {
"alias" : "MN8BIT4",
"result" : "succesful"
}
}
}

But since 4 days MN2 payed 4 times, MN1 payed once and the other two didn't pay at all.

Any suggestions how to see what is going wrong?

Are all the MN's working on the same machine? If they are on different network segments, it is possible some staking wallets do see them, others don't.

In any case this has to do with propagation of the masternode info inside the 8bit network. As far as I could see, this is random, so running MN on current 8bit network is kind of a gamble.
The dev may have deeper insight though.

In any case I just hope the new codebase will be out soon. The existing one is tricky, whimsical and unpredictable, and I personally like it for being such

.
But I know not everyone likes it that way, so new codebase could make things more fair and more predictable...

MN1, MN2 and MN3 are running on one vps, MN4 is running on another one.
Before they all had they're own controlling wallet and where paying out all 4 of them.
After trying to control all 4 with one controlling wallet this trouble started.
After starting them they all appear in masternode-list, but after some time some of them disappear.
Will they propagate after waiting some time or won't they at all?
Is there a way to get them all properly propagated on the 8bit network?