UMA is a decentralized financial contracts platform built to enable Universal Market Access. The technology has two components: self-enforcing smart contract design templates and a provably honest oracle. Together, they enable liquidity providers to create synthetic asset tokens - trustless ERC20-compliant tokens that represent ownership in the price returns of any fiat or cross-chain crypto asset.

The UMA team needs your help to test the security of first component in the UMA system to be publicly released -- a smart contract that lets participants create and distribute synthetic asset tokens on the Ethereum blockchain. We look forward to working with you, the security community, to find security vulnerabilities in order to keep our businesses and customers safe.

Response Targets

We (UMA Project) will make a best effort to meet the following response targets for hackers participating in our program:

• Time to first response (from report submit) - 2 business days
• Time to triage (from report submit) - 2 business days
• Time to bounty (from triage) - 14 business days

We’ll try to keep you informed about our progress throughout the process.

Disclosure Policy

• Follow HackerOne's disclosure guidelines.
• Please do not discuss or share vulnerability information without written consent from the UMA Project team or until it is publicly listed in a Github PR/issue.

Program Rules

• Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue, the issue will not be eligible for a reward.
• Submit one vulnerability per-report, unless you need to chain vulnerabilities to provide impact.
• When duplicates occur, we only award the first report that was received (provided that it can be fully reproduced).
• Multiple vulnerabilities caused by one underlying issue will be awarded one bounty.
• Social engineering (e.g. phishing, vishing, smishing) is prohibited.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own or with the explicit permission of the account holder.

Priority Issues

While we are interested in many types of security vulnerabilities in our system, of most interest to us are vulnerabilities that:

• Allow unauthorized users to withdraw balances from contracts either through direct withdrawal or token redemption
• Allow unauthorized users to create contract tokens
• Allow unauthorized users to modify or change prices published by the price feed contract
• Allow unauthorized users to modify or change prices published by the oracle contract
• Otherwise corrupt the price that the contract receives
• Lock the contract such that funds contained within it are no longer accessible by authorized parties through approved methods
• Cause funds to be misappropriated or incorrectly moved within the account
• Take advantage of our use of Metamask, Truffle, or Infura

Of lesser interest but still within scope are arithmetic errors or errors that arise because of known issues with Ethereum or the ERC-20 standard.

Test Plan

Instructions for setting up, running, and testing the various components of the UMA system are available in the UMA Protocol README. The README as well as the code should specify the correct behavior of the various contract methods for different user-types (UMA, token sponsor, token holder, and unrelated third parties).

Set up the contract and the Dapp locally or on a testnet and test any of the following (as 'UMA', token sponsor, as a token holder, and as an unrelated third party):

• Contract creation (only applies to sponsors)
• Token creation
• Token redemption
• Addition of margin
• Withdrawal of margin
• Contract expiry
• Contract default

Additionally, test the process of publishing prices both from the Oracle contract and the pricefeed.

All of the code contained in the UMA protocol GitHub is fair game to be tested

#Out of scope vulnerabilities When reporting vulnerabilities, please consider (1) attack scenario/exploitability, and (2) security impact of the bug. The following issues are considered out of scope:

• Vulnerabilities previously documented in the Trail of Bits Security Audit: F450216
• Vulnerabilities disclosed in public issues on the UMA protocol GitHub: https://github.com/UMAprotocol/protocol/issues
• Attacks requiring MITM or physical access to a user's device.
• Previously known vulnerable libraries without a working Proof of Concept.
• Missing best practices in SSL/TLS configuration.
• Any activity that could lead to the disruption of our running production service (DoS).

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Thank you for helping keep UMA Project and our users safe!