You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 24, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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
reserved_providers_count
andreseved_reward_percentage
.distributeFee
function is called, also split some revenue to the reserved providers.The text was updated successfully, but these errors were encountered: