Yes this is a fair point, I was thinking along the lines of hacking, which is generally illegal....but you are saying that companies will run self-compromised Masternodes and gather data to sell for profit. So assuming that spying on private financial transactions is OK in a particular territory (I'm thinking blanket regulations around data protection etc) then we are back to how meaningful this data is and how many nodes you need to compromise....guess we'll wait for the MN blinding white paper.
Let me give you thought exercise on the self-compromised nodes.
Let's say I ran a masternode right now and posted real time transaction data on a web site. I could put ads or trackers on the web page and generate revenue, like a chain explorer. Even if the data by itself wasn't that useful, people might still be curious about it, so I'd get traffic. (Of course I could promote on twitter, post links to interesting transactions, etc.)
In fact, given that this data doesn't even really expose anyone (after all its just one masternode, right?), it wouldn't hurt the price of DASH, so my collateral isn't impaired. Nothing has been really compromised.
What would happen?
As far as I can tell, I'd continue to get my masternode payments, people would still use my node,
and I would get extra revenue from traffic on my masternode explorer.
I guess Evan could do something to ban my node from the list or something. Maybe miners could do that if they even cared, but its not clear they would. Then I could just create a new one I think.
OK so 'nothing has been compromised' and you have a bunch of completely random MN data. What's the point? You earn a bit of ad revenue? So what? The only way this poses a threat to the network is if enough MN owners collude and do the same, which makes a number assumptions:
- that enough people are willing to invest 1000 DASH in masternodes to take part in an excercise that compromises the security of the coin they're invested in
- that all these people are savvy enough to set their nodes up to gather data in a common format and share this with their counterparts
- that this data, when re-assembled, provides any meaningful information (back to MN blinding)
- that the community or devs do nothing to counter this kind of behaviour
I think what you have described poses no threat to the network whatsoever.
edit: that's a bit absolute, I would revise to 'what you've described poses a negligible threat to the network'