Quote from: qwizzie on February 13, 2017, 07:43:48 AM

Quote from: tungfa on February 13, 2017, 06:58:45 AM

12.1 info

Merchants ,Exchanges ,3rd Parties ,.... still need time ,so there is NO rush to switch Enforcement back on again - no date is set yet ; )

I'm sorry to hear that as we did commit to a specific date in the official announcement of 12.1 and Amanda repeated that date
in her YouTube show as well.

Now we have an extra delay in having our budget proposals up and running and have missing MN payments because payment enforcement is still off.

Without running code which based on block height triggers the hard fork, THERE IS NO COMMITMENT.

Do you understand the stark contrast between neutral, incorruptible code and squishy, unreliable, wavering humans?

Don't you understand that what makes Bitcoin great is its magical ability to REMOVE the trusted-but-untrustworthy human element from value storage/transfer mechanisms?

That's the entire point of having a blockchain. And you goofballs traded that Holy Grail for some dorky ginger beta's judgement calls. In 2017. WTF I can't even. Sad

When your ~~cult leader~~ benevolent dictator for life tells you one thing (Deadline A) in order to get you to act in certain ways but then says something different (No Deadline A) that's called manipulation.

Duffield never intended to enforce Deadline A. That was merely hocus-pocus optics. It was just for public consumption, so Evan The Instaminer could dump more of his 'accidentally' instamined hoard into the pump.

You were manipulated into believing something that was not true. It's time to stop and reconsider the reliability of your Dash signals, because a very important one just proved to be less signal than noise.

Even worse, the false information you were given about Deadline A was INTENTIONALLY tailored to manipulate your behavior.

Have some dignity and stop letting Evan use you like a puppet.

This isn't the first time Evan has manipulated the Dash community like marionettes by pulling their strings for PR purposes, only to renege on his previously indicated course of action when it proves to be unwise and/or inconvenient and/or beyond his abilities.

It's happened repeatedly. Dash's Decentralized-In-Name-Only governance demonstrates a clear pattern and practice of Commit-->Delay-->Renege-->Repeat.

It happened with Ring Signatures. It happened with Masternode blinding. It happened with 2MB blocks.

I can't believe you guys don't see the pattern; it's like watching Lucy fool Charlie Brown with the football. Every. Single. Time.