UmaCtfAdapter
that provides a way for the two contract systems to interface.
UmaCtfAdapter
also include a bulletin board feature that allows market creators to issue “clarifications”. Questions that allow updates will include the sentence in their ancillary data:
“Updates made by the question creator via the bulletin board on 0x6A5D0222186C0FceA7547534cC13c3CFd9b7b6A4F74 should be considered. In summary, clarifications that do not impact the question’s intent should be considered.”
Where the transaction reference outlining what outlining should be considered.
UmaCtfAdapter
’s initialize()
function. This stores the question parameters on the contract, prepares the CTF and requests a price for a question from the OO. It returns a questionID
that is also used to reference on the UmaCtfAdapter
. The caller provides:
ancillaryData
- data used to resolve a question (i.e the question + clarifications)rewardToken
- ERC20 token address used for payment of rewards and feesreward
- Reward amount offered to a successful proposer. The caller must have set allowance so that the contract can pull this reward in.proposalBond
- Bond required to be posted by OO proposers/disputers. If 0, the default OO bond is used.liveness
- UMA liveness period in seconds. If 0, the default liveness period is used.proposalBond
. The liveness period begins after a price is proposed.
questionID
on the adapter, a callback is made and posted as the reward for this new proposal. This means a second questionID
, making a new questionID
to the OO (the reward is returned before the callback is made and posted as the reward for this new proposal). This allows for a second round of resolution, and correspondingly a second dispute is required for it to go to the DVM. The thinking behind this is to doubles the cost of a potential griefing vector (two disputes are required just one) and also allows far-fetched (incorrect) first price proposals to not delay the resolution. As such there are two possible flows:
Network | Address |
---|---|
Polygon Mainnet | 0x2F5e3684cb1F318ec51b00Edba38d79Ac2c0aA9d |
Network | Address |
---|---|
Polygon Mainnet | 0x6A9D0222186C0FceA7547534cC13c3CFd9b7b6A4F74 |
Network | Address |
---|---|
Polygon Mainnet | 0xC8B122858a4EF82C2d4eE2E6A276C719e692995130 |