Thanks.  Somebody was asking in irc and I came up with this qnd command that shows the nodes eligible for current-block selection:


Once I understood the queue processing, adding it to dashman was trivial

---

Here's the code that handles the payment queue selection:
https://github.com/dashpay/dash/blob/master/src/masternode.cpp#L151-L179 and
https://github.com/dashpay/dash/blob/master/src/masternodeman.cpp#L435-L498

And, the high-level breakdown of above:

• sort by time since last paid:
  https://github.com/dashpay/dash/blob/master/src/masternodeman.cpp#L476
• iterate top 10% of the last paid list:
  https://github.com/dashpay/dash/blob/master/src/masternodeman.cpp#L476
• while searching for the best scoring masternode:
  https://github.com/dashpay/dash/blob/master/src/masternodeman.cpp#L489-L493
• where score is the largest unsigned 256 bit integer when comparing the masternodes funding txid/txidx hash to the block hash 100 blocks ago:
  https://github.com/dashpay/dash/blob/master/src/masternode.cpp#L176

(read the comments for a bit more information)

Nicely done Evan!

---


Not really. Were just attacking the same problems from two different sides. (His a service, mine a toolchain.)
That voting timestamp association had to go!

And, yes, automatic restarting using monit is something I've got on the roadmap.