Ok, I almost always saw "not capable... or " successfully started, and lately, it just automatically started up when I started the wallet up, which I thought was a new feature. So I posted the quirk ;P Thanks
Short answers are "because someone is cheating" and "not yet".
I'm not sure I get the question. Cold node signs initial broadcast message with 1000 DASH privkey and Hot node signs ping messages after that with mnprivkey.
Yep, MN will go through new sync procedure first now before it tries to self-activate.
https://github.com/dashpay/dash/blob/v0.12.0.x/src/masternode-sync.h#L8-L13
No, I only ever started them using start-many.
No, I created 3 groups of nodes - 10, 10, and 4, and just kept re-starting (which was often because they kept going down)
No, each time I created a group of nodes, I immediately fired them up using start-many, and they showed up on masternodelist as "ENABLED".
Yes, I randomly selected and checked about a half a dozen or so - every one showed status as "This url seems to be expired".
For sure, that was an issue you pointed out, and the devs have fixed it with this latest release.
Ohh, I was under the impression you shut down all 24 of MNs - lol, apparently not?
Cool, I'd prefer to not redo the entire setup process all over again.
Right on.
Already done.
Thanks for keeping me updated, so we have to investigate further..
I did not shutdown any of your nodes, they were already expired as you send me the list.
y99Q9aDgmTDpxf2m7tTMwLU4stVUaSA4kU please send me as much as you can ~
if (tx.IsCoinBase())
{
if (tx.vin[0].scriptSig.size() < 2 || tx.vin[0].scriptSig.size() > 100)
return state.DoS(100, error("CheckTransaction() : coinbase script size"),
REJECT_INVALID, "bad-cb-length");
}