This repository was archived by the owner on Feb 24, 2023. It is now read-only.

Description
Motivation
Currently the way TCD works does not encourage more data providers beyond the active ones. Thus, if a provider goes offline or stops providing data, adding a new data provider may not be as smooth. Looking at EOS, for example, reserved validator nodes are in place to prevent such situation. Band should also have that.
Suggested Implementation
- Add two governance parameters:
reserved_providers_count and reseved_reward_percentage.
- Whenever
distributeFee function is called, also split some revenue to the reserved providers.