Ability to Be Notified of New Referendum Proposals

Question Should future EOS tokens sent to eosio.ramfee and eosio.names accounts be allocated to REX? Method To do this, the Block Producers will have to set CHANNEL_RAM_AND_NAMEBID_FEES_TO_REX = 1 (https://github.com/EOSIO/eosio.contracts/blob/44d53447e04cb9fc32e1a73aacb7119511363a29/contracts/eosio.system/include/eosio.system/eosio.system.hpp#L23) Background Information The EOS Resource Exchange (REX) enables token holders to lend/borrow CPU and NET resources. One of the features of REX is that it can also distribute EOS fees paid into system accounts, eosio.ramfee and eosio.names, on top of the fees paid by those borrowing the resources. eosio.ramfee account: This account holds the 0.5% fee paid for all RAM purchases and sales on EOS. eosio.names account: This account holds all EOS paid for short names (e.g. ".eos") each day in the shortname auction Original Announcement of REX from Dan Larimer: https://medium.com/@bytemaster/proposal-for-eos-resource-renting-rent-distribution-9afe8fb3883a Additional notes The addition of these funds would not increase inflation nor effect the 4% inflation allocated to the eosio.saving. The current funds in both accounts in question would not be touched, only future tokens that enter the accounts would be reallocated into REX.

Would EOS be better off if ECAF would not be able to issue key switching orders and we would rather rely on the code and block producers 15 out of 21 multisig?