🎯 North Star 🎯
To make the Saturn network as “Web3” as possible. Full trustlessness and decentralisation may not be possible yet but there is still many ways we can move the dial from Web2 towards Web3. Let’s aim for Web2.999
Why?
- Because what is the point otherwise! There are some brilliant Web2 CDNs already on the market. However, here at Protocol Labs, we care about:
- content addressing,
- verifiability,
- data privacy and ownership,
- trustless protocols,
- decentralisation.
- The more Web3 Saturn becomes, the less liability and responsibility is in the hands of Protocol Labs.
- Saturn is suddenly getting noticed by the Web3 community! It has the potential to go all the way. The more Web3 Saturn becomes, the more kudos it will get from the Web3 community which will lead to more use cases and adoption from the Web3 community. Conversely, if we keep building Web2 features we will cross the Web2 Rubicon and not be able to migrate to a web3 architecture.
Working Group
This working group will include experts from RM lab, Consensus Lab, CEL and potentially CryptoNet and others in order to make progress quickly and in the right direction.
Current Saturn Control Plane Responsibilities
The existing centralized Saturn control plane performs the following tasks, that we have laid out as workstream. We would like to turn all these tasks into ones governed by smart contracts.
Workstream Tracker
Web3 Saturn Workstream Categories
Verifiable Payments System
This workstream aims to take the existing Saturn payment system and make it as verifiable as possible, whilst not risking the security of the network. The fraud detection module must remain a black box for now but how verifiable can we make the payment system?
- ‣
- https://github.com/filecoin-saturn/zk-fraud: ZK-circuits for running the fraud detection algorithm and summing the resulting non-fradulent logs to calculate payout. Also supplies contracts to verify the generated proofs.
- ‣: (for now) a payment splitter contract for dispensing Saturn rewards + the scripts for deploying to FEVM
- ‣ page by @Anonymous (includes diagram of payments Impact Evaluator)