UMIP 114 -Register updated Optimistic Oracle

Mhairi · March 3, 2022, 2:10pm

This UMIP will have the effect of registering an updated optimistic oracle contract with improved ancillary data formatting logic.

github.com

UMAprotocol/UMIPs/blob/master/UMIPs/umip-114.md

## Headers
| UMIP-114    |                                                                                                                                          |
|------------|------------------------------------------------------------------------------------------------------------------------------------------|
| UMIP Title | Register updated Optimistic Oracle             |
| Authors    | Nick Pai (nick@umaproject.org) |
| Status     | Approved                                                                                                                                    |
| Created    | July 8, 2021                                                                                                                           |

## Summary (2-5 sentences)
This UMIP will have the effect of registering an updated optimistic oracle contract with improved ancillary data formatting logic.

## Motivation
DVM price requests are encouraged to take advantage of the ancillary data `bytes` parameter to specify how voters should resolve votes. For example, [this price request](https://etherscan.io/tx/0x9d7a592c2d5dcd72b638967efff008f208bc1e5b06a0fa02b50114accf459370#eventlog) for the `SPACEXLAUNCH` identifier specifies `"id0:Transporter-2,w0:1"` in hex format as the ancillary data to inform voters about which rocket launch (e.g. the rocket is "Transporter 2" in this case) they should be voting on.

Because ancillary data is a `bytes` data type, voter experience is enhanced if there is a soft standard for formatting the ancillary data. This is what the Risk Labs team has tried to do with [this document describing an ancillary data interface](https://docs.google.com/document/d/1zhKKjgY1BupBGPPrY_WOJvui0B6DMcd-xDR8-9-SPDw/edit?usp=sharing). In summary, the goal of this document is to encourage price requesters who use ancillary data to ensure that it can be decoded directly from `bytes` to `utf8` via standard client libraries such as `web3.js` and `ethers.js`, and that the `utf8`-encoded ancillary data is a comma-delimitted key-value dictionary just like the `SPACEXLAUNCH` example above.

The current supported optimistic oracle "stamps" data to the ancillary data informing voters that any price requests were sent by an optimistic oracle. This is useful information and gives voters more information, but the "stamping" does not conform with the above interface; it produces `bytes` data that cannot be directly decoded to `utf8` format. 

This UMIP proposes to register an updated optimistic oracle that "stamps" ancillary data according to the above standard.

This file has been truncated. show original

Topic	Replies	Views
UMIP 52 - Add Optimistic Oracle technical UMIPs	196	March 2, 2022
UMIP 54 -Approve New EMP Financial Contract Template technical UMIPs	187	March 2, 2022
UMIP 144 -Register Oracle Hub technical UMIPs	237	March 3, 2022
UMIP 113 -Register Polygon Oracle Root Tunnel technical UMIPs	213	March 3, 2022
UMIP 53 -Register new Perpetual financial contract with DVM technical UMIPs	183	March 2, 2022

UMIP 114 -Register updated Optimistic Oracle

Related Topics