Mhairi
March 2, 2022, 2:01pm
1
The DVM should support price requests for a CONSTANT price identifier. CONSTANT 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.
# Headers
| UMIP-83 | |
|---------|-|
| UMIP Title | Add CONSTANT as a price identifier |
| Authors | Sean Brown (@smb2796) |
| Status | Approved |
| Created | 04/21/21 |
| [Discourse](https://discourse.uma.xyz/t/add-constant-price-identifier/1018) | |
# Summary
The DVM should support price requests for a CONSTANT price identifier. CONSTANT 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.
# Motivation
For some financial products, it is useful to have a price identifier that simply returns a constant number. As an example, UMA's KPI options always need to be worth 2 UMA before expiry. This can also be accomplished in other ways - like using a financial product library - but for some contract deployers it may be easier to not need to deploy a custom library and instead just set their price by using this price identifier.
This constant identifier will also be the first price identifier to reference ancillary data.
This file has been truncated. show original