Process
Risk Communication
Last updated:
April 28, 2022

Some risks to a smart contract system are essential or part of the incentives. For example, the risk of impermanent loss naturally arises from the use of Automated Market Makers. These risks need to be well communicated to protocol users as a way to mitigate their impact. This can be done at the end of the review process once all acceptable/essential risks are known.

Where to communicate risks

Ideally protocol risks are communicated in several areas:

  • Project user documentation
  • Any integration guides for third-parties
  • In the primary consumption interface (e.g., dapp)

As a best practice example, see the Ribbon Finance Theta Vault Risks explanation:

https://s3.us-west-2.amazonaws.com/secure.notion-static.com/d3651827-91a8-47b3-ac6f-da85583df0b8/Untitled.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIAT73L2G45EIPT3X45%2F20220428%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20220428T141529Z&X-Amz-Expires=86400&X-Amz-Signature=e16a5ed64ff0b67c20798d9220abdf35f632416702bddff36a84f2ff3d0868ab&X-Amz-SignedHeaders=host&response-content-disposition=filename%20%3D%22Untitled.png%22&x-id=GetObject
Ribbon Finance Theta Vaults

See Also: