Flux docs

1.1 Roles and Responsibilities

At least three distinct roles exist in the protocol:
  • Requesters, who are responsible for creating resolvable data requests in return for a fee paid to validators. Requesters implement a smart contract with methods to create data requests and receive outcomes (see 3.1.). Requesters have a high degree of flexibility when creating data requests, having the ability to choose the type of data, which sources to choose from, the initial resolution window time, etc.
  • Validators, who are responsible for staking FLX on data requests with correct outcomes to earn more FLX and ensure data integrity either by running node software with low system requirements or manually answering data requests through a CLI or web interface. Some FLX is distributed from a requester to validators that staked on the correct outcome after a data request has been finalized, and incorrect outcomes that have been bonded have their associated stakes slashed.
  • FLX holders, who are responsible for participating in governance through the Flux DAO to curate requesters that will generate the most value for the protocol and delegating to validators. The Flux DAO aims to maintain a healthy balance of TVL to total market cap, curate requesters that are able to pay out validators and create valid data requests, and upgrade features of the protocol.