ROLES
Last updated
Last updated
1.3.1 Protocol layer roles:
The participant who uses the system: makes transfers of tokens, generates data in exchange for rewards, pays for data, etc. Depending on the type of stored assets, users can be divided into GEO and ODIN holders (there are users who combine both roles). ODIN holders can take part in the governance of the system.
Maintainer of the ODIN system. The main functions of validators are the formation, proposal, verification, and confirmation of blocks in the system. In other words, validators participate in reaching a consensus on updating the state of the accounting system. An additional function of the validator is to receive data from external sources and generate reports (see 3.9).
The participant who has revealed a desire to become a validator. Validators are delegates who have received the most votes (stake) from users.
The participant who does not take part in reaching consensus in the system but at the same time maintains a full node (a complete copy of the database) and checks all transactions and blocks according to the protocol rules.
1.3.2 Business logic roles:
Data provider - the participant who was chosen to act as a data source/data feed. This participant’s main task is to provide external data at the request of validators (in a particular case, after receiving payment). Note that in this case, we are not talking about the final producer of data (this is a more degenerate case), but most often about a service that collects and processes data and is ready to provide them.
Data consumer - the participant whose purpose is to retrieve a dataset or some value calculated from that dataset. Contract provider - the participant who provides scripts that automate and standardize data retrieval and processing.
Data producer - the participant who generates data and exchanges it to the reward (with data provider).
