And not only switch off the payments. Here follows
the list of what Evan and the core team can change (or switch off) any time at all the
4271 running masternodes, without asking anyone about it:
#define SPORK_2_
INSTANTX_DEFAULT 978307200 //2001-1-1
#define SPORK_3_
INSTANTX_BLOCK_FILTERING_DEFAULT 1424217600 //2015-2-18
#define SPORK_5_
MAX_VALUE_DEFAULT 1000 //1000 DASH (<---
this is the masternodes collateral)
#define SPORK_7_
MASTERNODE_SCANNING_DEFAULT 978307200 //2001-1-1
#define SPORK_8_
MASTERNODE_PAYMENT_ENFORCEMENT_DEFAULT 4070908800 //OFF
#define SPORK_9_
MASTERNODE_BUDGET_ENFORCEMENT_DEFAULT 4070908800 //OFF
#define SPORK_10_
MASTERNODE_PAY_UPDATED_NODES_DEFAULT 4070908800 //OFF
#define SPORK_11_
RESET_BUDGET_DEFAULT 0
#define SPORK_12_
RECONSIDER_BLOCKS_DEFAULT 0
#define SPORK_13_
ENABLE_SUPERBLOCKS_DEFAULT 4070908800 //OFF
This is of course only what I have read into the opensource code (and I have not read all the code yet). Additionaly, there are also the
compiled binaries where no independant tester has ever checked them whether more hidden sporks exist there or not. I wonder why the masternodes owners, while they keep
voting and paying for marketeers for feasts and for conferences, why they have not yet asked an independant tester to check the masternode binaries for hidden sporks or even worst for
password stealer trojans.
The trust the masternode owners put in the core team, seems suspicious to me.
Trust , but verify should be the rational thing to happen.