2a) Too many non-complying pools and bad actors is likely throwing a monkey wrench in planning. People are worried about what will happen without a supermajority consensus. How do we get pools to comply? How do we pull off the actual fork (since that's what enforcement is, essentially) without a very strong consensus? Will checkpointing (and the centralization that it implies) be necessary to pull this off? These questions aren't insoluble, they're just on everybody's mind.
So you guys know, there is a solution to the non-compliance issue, but as I think I said in a prior post, it's not something Evan wants to implement.
From an email:
I could also write code to blacklist blocks from bad pools using the
checkpointing code as a solution. So cheating pools would risk being
shut down, but that gives me too much power I think.
From another email regarding what went into RC3:
RC3 includes the spork logic, massive masternode revamping/bug fixes
and non-enforced payments.
So no official support for stacked payments at this time.
Regarding RC4's anonymity enhancements - I've seen it, it is an elegant addition to the anon layers that already exist in Darksend, and it will be worth the wait.
There is an economy-side feature in the pipeline that (to my knowledge) nobody in cryptocurrency has even considered to this point, but again, the time is not yet right to release details on these things.
There is simply nothing to pump right now. Over the next few weeks you'll start to get glimpses, but anything beyond that is premature at this point.
