Surveying and mitigating current and future legal boundaries/parameters, especially around data protection coming from heterogeneous rule setters such as national (Germany) and supra-national bodies (e.g. the European parliament). For an overview have a look here.
How are these data priced and sold?
See Data Brokers and The Value of Data for some information. Stefan tells us a rough estimate is that each data point purchased from a DMP will add 10% to CPM costs.
Pricing Dimensions: Get a better notion of data pricing across categories, demographics, source and reliability
They don't, because they can't. This explains what we've heard repeatedly (e.g. Aurel) that data purchasing is always a gamble — buyers care only about ROI (not accuracy itself), and will buy a small volume first to test the waters.
It's possible there are no good solutions here due to the ease of copying and modifying digital data. If that's the case, we expect to find several inefficiencies in data markets stemming from overbearing due diligence and verification processes.
Design a token economy that incentivizes data producers to join our pool, and provide mechanism to curate, enrich, validate data accuracy, data yield etc.
Identify "one-click" solutions for data producers to plug into our pool and start generating cash flows.
Identify and make it easy to onboard large data producers.
How will we sell data?
A better framing might be: can we balance data privacy and availability? In other words, how do we maintain a decentralized data pool online?
We imagine 2 ways that data can be shared in advertising. The first one is online, during an ad request. A user visits a website they choose to share data with, and the website makes use of these data to deliver better content (through internal customization) and ads (through enriching the ad request). This dovetails neatly with the Data Wallet and is what we've been discussing.
However, this limits data availability to transactional online interactions. Should we focus complementarily, or alternatively, on supporting an offline market? This could be easily done with a centralized pool, but that's not only off-brand but also a ticking time bomb of a honeypot. Alternative solutions might resemble Sovrin's Agents, Solid's Pods, or PolyPoly's polyPods, where an always-online robot deals with data requests according to preferences set by the user.
Deeper research into our data storage alternatives
Explore pricing mechanisms (Aurel is already looking into some of this).
What infrastructure do we use for our Substrate chain?
Once we have a Substrate chain built, we have several options for deployment: running it in isolation with our own validator network, or as a parachain or parathread on Polkadot or Kusama.
Running it in isolation affords us more throughput and fees, and sidesteps the potentially prohibitive parachain auction or parathread execution costs. As a parachain or parathread, we sidestep the overhead of recruiting and incentivizing a validator set, access cross-chain communication for easier trustless integration with other chains, and possibly gain legitimacy in the community.
Independent substrate chain
once available in Polkadot/Kusama
needs own validators
Trustless interoperability with other chains
recruiting and incentivizing validators
It's also possible to develop and deploy smart contracts on Substrate chains that support them, e.g. Moonbeam, Edgeware or Plasm. This option is likely to afford us too little control to be attractive, so we're not considering it at the moment.
Parachain slots aren't sold, but leased for a limited period. These leases are awarded via an auction mechanism.
The auction mechanism was successfully tested in the Rococo testnet by several test parachains, such as Acala's and KILT's. Rococo also saw successful usage of XCMP (trustless cross-chain communication).
When we’re confident testnet parachains are running smoothly and the code has been fully audited and benchmarked, a vote to enable parachains and slot auctions on Kusama will be submitted via on-chain governance