Bitcoin XT Developer Gavin Andresen Won’t Rule Out Block Reward Change

In a bizarre interview where he claims the block size decision should be left to Coinbase and Bitpay at least six different times, and labels Bitcointalk users and Reddit users “trolls”, Bitcoin XT developer, and CIA informant, Gavin Andresen (aka Gavin Bell) seemed to leave the door slightly open to possible changes in bitcoin’s block reward.

Interestingly, he doesn’t completely rule out adjusting the block reward when asked during the interview around 1:10:00. With hazed over eyes indicative of an individual on mind bending meds, he states that he “doesn’t think” he would support a change to the block reward, then grins from ear to ear.

Sponsored Links

If I could go back in time, I would urge Satoshi to make the block reward change continuously every single block. Take the time stamp and calculate what the reward ought to be.

This is a frightening revelation and one of the most shocking I’ve personally encountered in my 35 plus years of technology coverage. In June, Jon Matonis warned that if Bitcoin XT is successful in bullying its way into consensus, a block reward change would become inevitable.

Matonis does believe it might be possible to preserve the 21 million bitcoin cap, but only if Mike Hearn and Gavin Andresen fail in their attempt to hard fork bitcoin by propagating their software to existing nodes.

Bitcoin XT is attempting to fork the core code by propagating it through the existing nodes. I would urge Gavin and Mike Hearn to withdrawal the Bitcoin XT propagation starting today. (If Gavin and Hearn succeed) it will eventually lead to a 21 million cap change.

Now it looks like Matonis had some insider knowledge as to the secret plans of Gavin and his co-conspirator Mike Hearn. If two rouge developers are successful in taking Bitcoin hostage and controlling its network of users, it would become the most centralized currency on the planet.

Will you support Bitcoin XT? Should the block reward system remain unchanged? Log in below using your favorite social network and weigh in on the discussion.


error: Content is protected !!