2/ MobileCoin chose to build their protocol with the entire Monero protocol stack for privacy, while relying on Intel SGX for validation of transactions:
This reliance means that Intel becomes a trusted participant in the network and assumes no backdoor
3/ Unfortunately, even though MobileCoin based their entire transaction protocol around Monero (rewritten in Rust, which is great!) they blatantly ignored the source of the protocol:
4/ The Monero project has been iterating and improving the Monero protocol for 7y, and though it was originally based on the Cryptonote protocol, it has evolved drastically and no longer shares many similarities.
5/ The Monero community always gives credit to the source of innovations, and many of the core pieces of the protocol stem from efforts to improve Bitcoin privacy that were never implemented there.
Examples of this are Confidential Transactions, Bulletproofs, and Dandelion++.
6/ The most interesting deviation from the Monero protocol is the deletion of rings post-validation and pre-inclusion:
I’d love to hear more thoughts on how (if?) this could work for Monero.
7/ To top all of this intentional lack of credit to the Monero project, the lead engineer for MobileCoin took to Twitter to bash Monero’s codebase, obviously without understanding Monero or it’s history:
8/ Another core issue with MobileCoin is that there is no mining or fair issuance — all 250M coins have already been mined in 16 outputs, and are solely the property of MobileCoin and it’s VC investors to use/sell as they see fit:
9/ However, maybe the most troubling of all with MobileCoin is that they already explicitly censor and prevent US citizens (among many others) from using MobileCoin in any way:
10/ Add to this their already explicit support of government surveillance and economic control, and you have something completely antithetical to “cryptocurrency”:
There is no need for all transactions to have multiple confs.
12/ In addition, transaction fees are already extremely high at ~$0.67 per transaction flat fee, far too much for this type of mobile-first micro-payment platform:
This is drastically higher than the current $0.0037 TX fees in Monero.
13/ Note that there are no miners or validators to pay for security, so there is no need for high fees in any way.
I would expect this to be arbitrarily lowered and controlled by MobileCoin in the future, but seems like a serious design oversight on day one.
14/ All of this to say that MobileCoin screams “cash grab” and doesn’t seem to have any basis in technical merit or user-base.
MobileCoin has 0 existing user base, no exchange listings, and has been built from the ground up for VC-funding.
15/ As someone who has been pushing @signalapp for a while, I’m pretty upset by this move the more I learn about MobileCoin and the intentional disregard they’ve taken for crediting #Monero with their entire privacy protocol or building a censorship-resistant platform.
F/ To finish it off, here’s a great old thread that speak to the disconnect between cypherpunk ideals that seems to be rising in the space.
The most painful part of this is if Signal ceases to be a good platform to recommend (and all of this has shaken my faith) I’ve poured *many* hours into onboarding people to Signal.
Hard to change now.
A response (of sorts) from the CEO of MobileCoin on the launch:
1/ @GrapheneOS crossed the line for the last time last night, and I now have to strongly recommend no one use their OS.
After weeks of reply spam, sockpuppet spam, and DMs, they reached out to *another* #Monero community member I respect via DM and slandered my reputation.
2/ While the OS itself may be fine (I know people using it without issues), I cannot in good conscience recommend something that is led and built by people that would stoop to these levels simply because I chose to use @CopperheadOS and recommend it based on my own experience.
3/ As of today I have removed any mentions of it from my blog, and will solely recommend people use @CopperheadOS or @calyxinstitute if they want to move to a de-Googled and more private mobile experience.
Simply adding the block in my NGINX conf file and adding a line to each server block gave a huge increase in load speed to repeat visitors/assets shared by pages.
3/ The second was to enable GZIP but use server-side pre-compression following this guide: