Flux docs

3.2 Preparing entry to Requester Registry

Before a proposal is created to request whitelisting in the Requester Registry and is voted upon by the Flux DAO, a requester is responsible for the following:
  • The contract source code matches the interface for the current deployment as defined in the repository
  • The contract source code is made publicly available with an open-source license
  • The requester has a sustainable model to fund data request creation and fee payouts
  • The contract has built-in mechanisms to ensure data requests being created are domain-specific and resolvable. Invalid markets or data requests phrased ambiguously are less beneficial to validators and FLX holders in general.
Last modified 1yr ago