UMAprotocol / UMAprotocol/uma-docs

Outdated code and addresses in Optimistic Oracle Getting Started guide

Open
#26 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
6
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Hello UMA team,

While following the Getting Started guide, I noticed that some parts of the example contract are outdated:

  1. Interface path – The OptimisticOracleV2Interface.sol link in the guide points to

    /packages/core/contracts/oracle/interfaces/OptimisticOracleV2Interface.sol
    

    which no longer exists. The current path appears to be:

    /packages/core/contracts/optimistic-oracle-v2/interfaces/OptimisticOracleV2Interface.sol
    
  2. Network and addresses – The example uses Görli testnet addresses, which are deprecated.
    For Sepolia (chain ID 11155111), I updated:

    • OptimisticOracleV2Interface to 0x9f1263B8f0355673619168b5B8c0248f1d03e88C from network JSON
    • WETH (IERC20) to 0x7b79995e5f793A07Bc00c21412e50Ecae098E7f9 (from Sepolia Etherscan)
  3. After these changes, I was able to compile and deploy the contract via Remix, and successfully call requestData().


Here are some transaction details from my successful deployment and requestData() call:

Deployment transaction:

requestData() transaction:

Despite this, I cannot see the request on the UMA Testnet Oracle Explorer.

Could you clarify if additional steps are required for requests to appear there, or if there is a delay/update needed for Sepolia testnet visibility?

Thank you again for your help!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with developers/optimistic-oracle/getting-started.md and compare its OptimisticOracleV2Interface path and Görli examples with the current protocol network JSON and Sepolia details in the issue. Update the guide so the example uses the current interface path and addresses, then verify the documented flow still compiles and deploys; the Oracle Explorer visibility question needs maintainer clarification.

Written by the indexing model from the issue text.

Assessment

Tech stack
solidity
Domain
blockchain, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.