
We have:
A) Big data silos, Web2 behemoths craving for more data, and
B) A blockchain protocol for privacy-sensitive data exchange & monetization: @OceanProtocol
How to bring these two together, while creating a better and safer web experience for everyone (Web3)?
@trentmc0 would say: Use what's there (UWT). Let's look into this 👇
Following the paradigm (use what's there), you understand that time is also a factor.
So how to connect A) and B), and when?
Recent developments enabling the concept to be discussed:
NFT hype = Broad, GenZ Crypto Adoption
Metamask 🦊 as a browser = First true Web3 “user autonomy” wrapper
NFTs as Login = On-chain Identities aka: PFP (compare: Twitter Blue)
Ocean data NFT (V4) = Adding data ownership to NFTs
Ocean datatoken (V3) = Buy or sell any subset of your data as a token
Connect these👇
It’s like how @sytaylor stated:
https://twitter.com/sytaylor/status/1514951487608209409
It is about the ID part, and it is also about the "algorithm" part.
Talking AI, we see: algos for system optimization. By existing Web2 behemoths, science, and Web3. Web2 rn has the most valuable data sets and biggest demand. Let's leverage this. But how 👇?
What you need:
I) Data as #dataNFT minted on Ocean Market, for privacy-preserving, incentivized data exchange
II) A "hook" for users to connect A) with B) seamlessly
III) Frictionless data consume and provide for dApps
IV) Actionable, contextual data to improve your UX (written by the platforms)
To get to this, one flavor of leveraging #OceanONDA (V4) would be:
1.) Mint data NFTs on Ocean Market for ur #PFPclub, like BAYC (ERC721âś“, Openseaâś“)
2.) Have them point to #datatoken on Ocean Market âś“
3.) Log into e.g. Twitter Blue w/ ur data NFT
4.) Twitter can read from your data sets, on your premise (accessed by buying your #datatoken w/ $OCEAN) to improve ur UX
5.) Twitter will write your new data bits to your data sets, through your #dataNFT, as they can receive royalties per consume of ur data (token) by other platforms
6.) Other platforms (Instagram, mirror.xyz, all #Web3 dApps) can read from your updated data sets, consuming them via $OCEAN #datatoken, upon login
7.) You set the new rules, you benefit, you give kickbacks, you protect your privacy, YOU chose and empower platforms from in Web3
In my old world, to get there, could have well been a 10y thing. In my new world, Web3, seeing the pace, it could be weeks or months.
Most components are there, few still need a bit of grind, also offering new ecosystem killer spots (compare: Uniswap, Opensea), but in general…
To get real, or TL;DR, gimme the TECH:
Trent, Co-Founder of Ocean Protocol, assembled a brief technical readme to get you started on the vision/concept above, minting on Ocean Market (V4, coming out very soon) 👇
https://github.com/oceanprotocol/ocean.py/blob/v4main/READMEs/profile-nfts-flow.md
And of course, as what I described is only one of many potential use cases for Ocean data NFTs, a bit of a broader look at what’s possible with data NFT (storing atomic user data on chain, on data NFT) 👇
https://github.com/oceanprotocol/ocean.py/blob/v4main/READMEs/key-value-flow.md
If you are 🤷‍♂️ on the above, here’s a non-tech intro (data NFT, datatoken):
https://oceanprotocol.com/technology/data-nfts-and-data-tokens
If your dev colleagues are 🤷‍♂️ on this, here’s a gen readme:
https://github.com/oceanprotocol/ocean.py/blob/v4main/READMEs/data-nfts-and-datatokens-flow.md
We would love to see all this become a reality, and we believe that our work (or that of the teams, I am new) at Ocean of the past 2 years offers all of you the ideal end-to-end framework to get started with this today - and have your user base protect and monetize their data with Ocean Protocol.
If you got any questions, you know where to find us. 🌊✌️
