Has anyone yet examined the first few thousand blocks to figure out why Milkshake added two checkpoints to the git repository, to manipulate the blockchain and cause miners with majority hashpower (that weren't constantly pulling from git) to fork off onto a separate chain and leave the blockchain with blocks generated by the minority of mining hashpower? Does everyone understand the forking issue wouldn't have occurred and the blockchain would've eventually resolved itself if Milkshake hadn't done that?
static MapCheckpoints mapCheckpoints =
boost::assign::map_list_of
( 0, uint256("0x521d2bc9fdb2534f26e5df423db7a64da14892993e4b4f0329c829a5e8194305"))
( 2500, uint256("0xd301c065649cbbfb1e93cec353047a12256365c9d50ac689b23ad913df25b6fd"))
( 5000, uint256("0x7671812122b751155ca6ed038f7b48e0f4f98a27a40dc9521d1c61d98e587544"))
;
It seems Milkshake did manipulate the blockchain with these checkpoints. Now the question is why. An analysis of the first ~5000 blocks should prove insightful.