Recently got into the topic of data ownership on a conversation with Carey Lening which helped catalyze a few ideas I’ve been kicking around for a while.
In short, data ownership requires layer fungibility.
I’ll elaborate below.
Over at BlueSky, Dell Cameron brought up that Facebook’s involvement in crypto, VR, and GenAI aren’t working out because they are only secondary to their main business purpose: surveillance. (link)
I disagreed. Cameron was right in that it failed because their main business is surveillance, but I suspect they screwed it up because it was such a great fit that they got too greedy.
Crypto would have been for them - if Libra had taken off, Meta would have gotten access to their users' transaction information, something they don't necessarily have right now.
They luckily came out the gate too hard and scared everyone off by making it too obvious it was a supranational currency.
— Ricardo J. Méndez (@ricardo.bsky.social) Jun 4, 2024 at 9:08
[image or embed]
Would it have been different if they’d seen it as a technology investment?
Two projects grew on the compost of Facebook’s Diem open source dump: Sui and Aptos. As of June 4, 2024, their combined fully-diluted valuation is about $10 billion. Facebook could have captured that value if they had spun it out from the start, even as a subsidiary where they control most of the token supply.
But Libra was never a tech investment. You don’t get to have an arms-length independent company and share data.
When all you have is surveillance, everything looks like a data trove.
Some thoughts on a 1996 paper by Narayana R. Kocherlakota.
Fully private systems, like Aleo, will be mostly memoryless systems (memory will be provided only by an individual’s viewing keys).
These systems will allow for a class of application we haven’t seen online before - UTXO/records as rai stones that just happened to materialize along with a zkp.
Given that fully private systems will be memoryless black boxes with zero-knowledge proofs, one cannot verify that a contract path got executed in the exact same way that you would have wanted. Therefore, it makes no sense to cling to the notion of traditional execution, and one should focus on the result that one wanted to achieve.
This would seem to indicate that private systems lend themselves to intent-based approaches.
We do not intend to enforce any sort of identity verification or unique identities in distributed[C]. We do not think encouraging people to doxx themselves is a good idea.
This goes beyond concerns about privacy, though. We believe that having multiple personas, which you can use depending on the context you are in, is healthy.
This raises concerns regarding disinformation. If the platform is uncensorable, and we do not plan to enforce identity, how will this not become a cesspool of fake news?
I think crypto is past the PGP point, where individuals controlled how to communicate with and how, but it’s still at the Bittorrent stage of chaotic yet mostly permissionless exchanges.
Its core tech might end up reaching the markets only as CBDCs, however.
This would mean that the majority of people limit themselves to what organizationally centralized services offer them, while the properly decentralized alternatives get more and more walled off.
In a worst-case scenario, crypto has a value in a closed economy. You use your ZCash to pay for decentralized hosting services, but you have to access it all through a VPN to avoid giving yourself away. You don’t generate these coins through fiat onramps, but through providing services to others, such as shared access or a mesh network relay.
Meanwhile, most of the world welcomes Netflix, where you only have whatever rights the company gives to you, for as long as you continue to pay them.
My goals for this talk are to:
A talk on conceptual accessibility being fundamental for adoption, while discussing mistakes I’ve made.
I delivered this talk at SAP Inside Track Berlin in September 2018. The audience was mostly enterprise developers, almost all of them specifically working with SAP as a platform.
Given how many companies I’ve seen flirting with the idea of distributed ledgers, I thought it would be useful to give people an idea of which cases I see as being a good fit for them, to give them a leg up the next time it enters the discussion.
I delivered Remember The Rubber Hose, a talk on privacy and distributed applications, at DappCon Berlin 2018. Skipping the introduction and going straight to the beef…