Disclaimer: The governance is currently in its bootstrapping phase, with the governance strategies still under beta. Thus, guidelines are subject to change at any given moment. Additionally, even if proposed, particular suggestions might not be implemented if they are considered detrimental to the protocol.
This handbook provides direction on how to govern the parameters of the Razor Network—a decentralized oracle network. Note that the governance will be progressively decentralized, with various protocol components transitioning to decentralized governance over time.
Governance Mechanism's Scope:
- Datafeeds and Collections
- Where to Propose: Submit Proposals Here
- Voting Delay: 2 days
- Voting Period: 12 days
- Quorum: 100M
- If needed, initiate a Pull Request in the appropriate repository.
- Start a discussion thread at Razor Network Governance Discussions.
- Draft a proposal and include links to the PR and the discussion thread.
- Update the discussion thread and PR, adding a link to the finalized proposal.
- Eligible Voters: All RAZOR token holders on the Polygon mainnet and Ethereum mainnet.
- Razor network validators and delegators are also eligible to vote. They must vote with the address holding sRZR. Their voting power equates to the number of equivalent RAZOR tokens they hold.
- Minimum Tokens for Voting: Currently, no minimum.
NOTE: If you are a delegator on Razor Network, you must vote on governance yourself. Your delegated staker cannot vote on your behalf as of now.
- At present, only authors are permitted to draft proposals. Future outlook: Individuals with a specific minimum voting power can create a proposal.
- Submit a governance proposal at Proposal Submission Portal.
- Proposals should fall within specified categories and meet the pertinent criteria.
Governance can add or remove data feeds based on votes. Requirements for a valid data feed:
- API must be accessible to the public.
- The endpoint should exhibit stability, with minimal errors.
- API call limits should be ample. 1 Request per 10 minutes at the minimum, from the same IP address. (Razor network currently makes one request every 20 minutes)
- API responses should be in JSON or XHTML formats.
- The feed should be available across all geographical regions.
- It must clear specific tests.
A collection refers to an amalgamation of data feeds specific to a particular dataset. Key characteristics of collections:
- Should comprise a minimum of 5 and a maximum of 10 data feeds.
- All data feeds within a collection must be interrelated.
- The power metric used should be uniform.
- The collection must pass designated tests.
Note: Proposals can request the addition or removal of a single collection at a time.
Governance can propose changes to the Razor Network parameters based on votes. All parameters are crucial for the protocol and are available in the JSON file located at mainnet/parameters.json in the parameters repository.
- Go through the Contribution guidelines.
- Make sure the parameter being updated is updated within a threshold with proper reasoning
- All tests should pass
- Only selected parameters that contribute to Inactivity penalties will be allowed to be changed through a governance proposal for now. (
penaltyNotRevealNum,penaltyAgeNotRevealNum)
Note: Currently, only the parameters associated with inactivity penalties, specifically Penalty Not Reveal Num and Penalty Age Not Reveal Num, are eligible for updates through a proposal.
For Datafeeds and Collections proposals, draft a PR at Razor Network Datasources, for Parameters draft a PR to Parameters and include the link to this PR in the proposal documentation.
Further Reading on Data Feed and Collections and Parameters.