Quote from: thelonecrouton on July 05, 2014, 07:39:40 PM

Quote from: TheBlackDogeOfWallStreet on July 05, 2014, 07:29:23 PM

Alright cheers, I'm forwarding this to my engineers to see if we could make this work.

Quote from: flound1129 on July 05, 2014, 07:30:16 PM

We are adapting. The point is via lazy coding you are increasing the number of headaches in my life and I have enough already.

Dear fellow DRKheads, these guys do have a point, stop ragging on them so much.

Maybe someone with Evan's ear might mention these issues and see what might be done in future to improve the situation?

The whole ecosystem needs to be supported, not just our particular favourite parts of it, anything that can be done to help should be considered.

To expand on this, if you are looking for mass adoption, you want every part of the system to be accessible.

Pools do centralize, but fewer pools means more centralization. So creating barriers or unnecessary complications for pools is a bad idea.

The ideal situation would be to have the coinbase payments handled within the wallet (and return to me an accurate coinbasevalue when I pull the blocktemplate, with the masternode payout already removed), and have the voting stuff be optional (looks like you have already done that). It seems extremely clunky to me to have stratum-mining be responsible for generating masternode payments.

That said, I am intrigued by this voting system and would like to hear more about exactly how it works. There is not much information publicly available about it (other than that it exists.)