Comment on page
"It was never easy to look into the future, but it is possible and we should not miss our chance." — Andrei Linde
Predictoor needs privacy for:
- Submitted predictions
- Compute aggregate predictions; and
- Aggregated predictions — only subscribers can see
This could all be done on fully-centralized infrastructure. But doing so would fail on our other goals: being globally distributed, censorship resistant, and non-custodial.
Targeting these needs, we researched & prototyped many privacy technologies. Oasis Sapphire emerged as the best choice because, as the only privacy-preserving EVM chain in production, it could handle these needs cleanly end-to-end.
The image below adds detail around the backend (bottom 1/3 of diagram). Let’s discuss.
Details of Predictoor Structure (Architecture)
Smart Contracts. There’s one Predictoor contract for each prediction feed, at each exchange/timescale: BTC/USDT at Binance/5m, ETH/USDT at Binance/5m, and so on. Each contract is an Ocean datatoken contract, with a new template for prediction feeds.
- ERC20 behavior. It implements the ERC20 interface and therefore plays well with ERC20-friendly crypto wallets, DEXes, etc.
- Ocean behavior. Being part of Ocean, having 1.0 datatokens means you can access the underlying data asset for the duration of the subscription (once you’ve initiated the order). For Predictoor contracts this is 24h. Each datatoken contract has a parent Ocean data NFT with metadata, means to specify & collect fees, and more.
- Predictoor behavior. Each datatoken contract has additional methods specific to Predictoor: submitting predictions, submitting truevals, computing aggregated predictions, etc.
Last modified 1mo ago