Policies

We classify policies within these categories: Technical, Ecosystem, and Risk. Technical: Technical policies define the routing protocol itself as well as the scope within which new proposals can be made – either to strengthen safety, enabling new economic opportunities, or enhance the functionality. Ecosystem: Ecosystem policies are defined more broadly. In general, they provide context for possible markets and collaterals accepted, applications running on top of the Protocol, or other ecosystem enhancing developments. Risk: To mitigate risks and strengthen the safety precautions undertaken by the Protocol, risk policies provide a way of evaluating risks for approving and implementing new developments, both in advance of putting a proposal to vote as well as to make an informed decision during the voting process. This touches on both technical and ecosystem policies, and includes but is not limited to:

• Compatibility of the proposed integration with the HUMAN routing Protocol

• Cost vs. reward

• Ease of implementation

• Ability to execute

• Business model/incentive

• Behavior and reputation

• Collision with existing features/markets

• Disabling a fraudulent actor

Each proposal needs to enter all required information to allow for an informed decision-making process. Uncomplete proposals will automatically be rejected. Required information may include, among other things:

• Financial requirements;

• The team and gaps within it;

• Value proposition;

• Timeframe/roadmap; and

• If technical, scope/architecture proposition