2/ The blog post essentially says that now they are open to integrating existing currencies once they reach characteristics only available to centralized currencies ATM, but will integrate MobileCoin in the meantime.
Requirements:
3/ It also intentionally mentions Zcash as a future possibility (with speed improvements) without mentioning Monero, who MobileCoin have to thank for their entire privacy protocol.
Full quote:
4/ They also, interestingly, call out Lightning (properly, IMO) for being unsuitable due to it’s reliance on onion routing for privacy which breaks down when a single entity is the routing node for all channel liquidity (as they would be in this case):
5/ For some reason they still completely ignore the use of 0-conf for small payments, but the rest of the requirements are certainly understandable if naive.
There is simply no way with current technology payments can be done as specified without centralization.
6/ Honestly, if MobileCoin hadn’t gone 100% pre-mine the tradeoffs would actually be understandable, but with the pre-mine and their suspicious refusal to acknowledge Monero or put out any proper response to these issues, I just can’t get behind it on any level.
Not sure where all of this “Lightning Network will destroy all outside of #Bitcoin” is coming from lately, but important reminder that if LN succeeds, it can be implemented on #Monero:
But if all of those issues are able to be resolved (among others), Monero can implement LN on top of a private and scalable base-layer, which would make it *better and cheaper* than LN on Bitcoin.
Bitcoin has proven it cannot iterate, Monero has proven the opposite.
Last month Zcash had 181,568 transactions and only 5,365 of those were fully-shielded.
Less than 3% of Zcash users *actually use* the privacy of Zcash.
Anything less than z2z-only shows disdain for the few users of Zcash.
It’s also interesting to note that this new wallet SDK seems to imply that users will not be able to tell if their transaction will be fully shielded or not, and it depends on recipients wallet.
Which is… incredibly harmful for end-users if I’m understanding that properly.
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:
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: