Approved Price Identifiers
This table includes identifiers that could be useful for new contracts and are likely to be encountered by proposers, disputers, and voters. It does not include identifiers that have been deprecated, identifiers that have fallen out of use, or specific token pairs.
If you need the price of one fungible token asset denominated in another token or USD (such as BTC/USD, or ETH/DAI), you can use TOKEN_PRICE. Fiat forex pairs are still included in the list, as well as certain non-USD-fiat/token pairs, since they are not supported by TOKEN_PRICE (since they don't involve a token).
If you need an identifier that is not included in this list, you can submit a new UMIP for approval. If a price request is made with an identifier that is not on this table, please refer to the canonical UMIP directory on GitHub. The absence of an identifier from this table does not necessarily mean the identifier is not approved, it just means it is not recommended for new contracts.
If you want to use an approved identifier that is not on this list, let us know and we can add the identifier back to this table for easier voter/disputer reference.
ACROSS-V2
Verification of whether a bundle of Across bridge transactions submitted to mainnet is valid.
CONSTANT
A price identifier which will always return the value, that is specified in the ancillary data passed along with the price request, or default to a value of "1" if no ancillary data is used.
COVENANT_V1
The COVENANT_V1 identifier is intended to be used with an Optimistic Distributor contract to verify Covenant bribing protocol payouts
General_KPI
General_KPI price identifier will allow any team to use the KPI identifier to track any verifiable key performance metric a team would want to create KPI options for. Ancillary data will guide voters to reach the KPI result correctly.
IS_RELAY_VALID
IS_RELAY_VALID will allow the DVM to validate relay requests coming from Optimism or Arbitrum using the bridge contracts here.
NUMERICAL
Generalized identifier that returns a number value based on a question asked in the ancillary data.
SHERLOCK_CLAIM
The SHERLOCK_CLAIM price identifier is intended to allow users of Sherlock to request the DVM for arbitration in the case of a disagreement about a smart contract exploit insurance claim.
TOKEN_PRICE
The TOKEN_PRICE identifier returns a price of any fungible token expressed in units of another fungible token, cryptocurrency or fiat currency. Ancillary data will guide voters in identifying which token should be priced, what should be its quote currency, which markets should be queried and any other processing instructions for resolving a particular price request.
uSPAC10
The purpose of these price identifier is to create synthetic token, price of which is linked to the value of index of 10 most active SPACs (Special Purpose Acquisition Companies) shares.
VolatilityDAOracle
The Volatility DAOracle is a collection of methodologies and implementations for indices and benchmarks. Each index can be verified by decentralized users through its data endpoint, open-source code, and methodology paper.
XSUSHI_APY
A price identifier that tracks the xSushi APY derived from an arbitrary number of days of sushi yield data.
YES_OR_NO_QUERY
YES_OR_NO_QUERY is intended to be used with ancillary data to allow anyone to request an answer to a "yes or no" question from UMA governance.
ZODIAC
The ZODIAC identifier is intended to be used with a Zodiac module that allows you to control a Gnosis Safe according to a set of rules defined off-chain and enforced with UMA's Optimistic Oracle. Unless the module contract has extra restrictions, any address can propose transactions that follow the rules and any address can dispute a proposal to UMA's Optimistic Oracle within a challenge window.
Last updated
Was this helpful?