soopy452000, an indictment
Sometime around the exit of Bryce Weiner, the Unobtanium project acquired a new "developer" who goes by the moniker of soopy452000. Let's examine a few alarm bells on why you shouldn't let this guy anywhere near you coin, or anything to do with mission-critical code for that matter, and put this conversation to bed.
Love 'em and leave 'em. Señor soopy has a reputation of inserting himself into cryptocoin communities, making questionable code changes, and absconding with funds. Good 'ol Bitcointalk registers a complaint from a user who testifies he sold 3 billion Beecoin for LTC, left the community hanging, and moved on to Navcoin. (archived)
anotherlateminer: "Read 2 pages from here: https://bitcointalk.org/index.php?topic=601247.msg8923728#msg8923728 BEEs have been sold in order to be used for development and there are still no signs of any development. LTC are just gone."
Telegram chats have provided a few gems as well:
A kind stranger comes to the main channel to warn what UNO might be getting into. (archived)
It didn't take long for teh lulz to manifest:
Readers of this blog already know about the war on cryptography from various "nation-states", and why you should be very careful of what tools you use when working with these items. Soopy exhibits very amateur behavior when dealing with such, from generating keys using keybase.io1 (archived), to posting unusable signed walls of text to Telegram chats that can't be verified.
Yes, this has predictable results, and clowns in this camp will likely come up with the same tired excuses to explain it. (archived)
Socialisms, like zooko.usg "dev subsidies" have no place in cryptocurrency. But that doesn't stop picadors trained in the Democratic Socialist Republic of Sri Lanka from trying to print unlimited money, and hoping no one notices, as was the case with 42coin:
"What is remarkable in the history of 42, is that until the spring of 2014 the coin supply was really capped at 42, but on March 17, 2014, the GitHub user sherlockcoin (aka soopy452000) made it unlimited. He was working under KGW implementation and no one noticed this "small change"." (archived)
So there you have it folks, and the above-stated reasons are just a few examples of why I won't be trusting any code pushed by this moron to the "official" Github2, and neither should you. But, Caveat Emptor, do your own research, and decide for yourself.
1. You may as well just go to iGolder and generate keys if you are using Keybase. Because cryptography is hard. ↩
2. Nor any binaries or wallets compiled and offered for release.↩
