LogoLogo
UMA HomeProjectsVoter DappOO Dapp
  • Welcome to UMA
  • What's New!
  • FAQs
  • Developers
    • Optimistic Oracle v2
      • Quick Start
      • Deposit Box
      • Event-Based Prediction Market
      • Insurance Claim Arbitration
    • Optimistic Oracle v3
      • Quick start
      • Data Asserter
      • Escalation Managers
      • Sandboxed Oracle Environment
    • oSnap
      • oSnap Quick Start
      • oSnap Deployment Tutorial
      • Snapshot Proposal + Transaction Tutorial
      • oSnap Proposal Verification
      • oSnap Configuration Parameters
      • Migrate to oSnap Safe App
      • Monitoring Bot Setup
    • Setting Custom Bond and Liveness Parameters
  • Protocol Overview
    • How does UMA's Oracle work?
    • Example Projects
    • DVM 2.0
    • DVM 2.0 FAQ
  • Community
    • Governance
      • The UMIP Process
      • DAO Proposals
  • Using UMA
    • Voting Walkthrough
      • Voter Guide
      • Voting Gas Rebates
    • Proposing Oracle Data
    • Disputing Oracle Data
    • Resolving Disputes
  • Verification Guide
    • Verification System
    • Polymarket
    • Across
    • oSnap
    • Y2K
    • Index
  • Resources
    • Network Information
      • New Network Requests
    • Audit & Bug Bounty Programs
    • Approved Price Identifiers
    • Approved Collateral Types
    • Subgraphs
      • Mainnet Voting Entities
      • Queries
    • Voting with a 2-Key Contract
    • Unsupported Contracts
    • Additional Resources
    • Glossary
    • Links
    • UMA TVS Methodology
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Resources

Network Information

UMA Contract Addresses
Chain ID
Fully Permissionless Settlement
Bot Support
DVM Support
oSnap Support
Oracle UI

1

Yes

Yes

Yes

Yes

11155111

Yes

No

Yes

Yes

137

Yes

Yes

Yes

Yes

80001

Yes

No

Yes

Yes

80002

Yes

No

Yes

Yes

10

Yes

Yes

Yes

Yes

42161

Yes

Yes

Yes

Yes

421611

Yes

No

Yes

No

No

100

Multi-sig relay

No

Yes

Yes

No

43114

Multi-sig relay

No

Yes

No

No

8453

Yes

Yes

Yes

Yes

84532

Yes

No

Yes

No

No

81457

Yes

Yes

Yes

No

168587773

Yes

No

Yes

No

No

1116

Multi-sig relay

Yes

Yes

Yes

1514

Multi-sig relay

Yes

Yes

No

1516

Yes

No

Yes

No

288

Yes

No

No

No

No

42

n/a

n/a

No

No

No

4

n/a

n/a

No

No

No

5

Yes

Yes

Yes

No

UMA's data verification mechanism (DVM), which is used to resolve disputes, is on Ethereum mainnet. Where possible, UMA uses a chain's native messaging bridge to relay dispute and governance information between that chain and Ethereum.

On chains where no such native messaging bridge exists, UMA uses a multi-sig controlled by UMA core engineers at Risk Labs to relay disputes to the DVM, to return data from the DVM to requesters on that chain, and to execute governance actions (for instance, adding new identifiers).

UMA is researching decentralized cross-chain messaging systems to make these chains fully permissionless.

Anyone can propose and dispute on any chain, and run bots to monitor contracts or propose and dispute automatically. For convenience, Risk Labs runs monitoring bots connected to UMA Discord channels, as well as proposer and disputer bots, on chains that secure significant value.

If you plan to launch on a chain not currently supported by the bots, we recommend you contact Risk Labs to add bot support, which will make it easier for third-party proposers and disputers to monitor your contracts. We also recommend running your own bots to provide additional resiliency.

PreviousIndexNextNew Network Requests

Last updated 1 month ago

Was this helpful?

(Deprecated)

(Deprecated)

(Deprecated)

(Deprecated)

Ethereum Mainnet
Yes
Ethereum Sepolia
Yes
Polygon Mainnet
Yes
Polygon Mumbai
Yes
Polygon Amoy
Yes
Optimism Mainnet
Yes
Arbitrum Mainnet
Yes
Arbitrum Rinkeby
Gnosis Chain Mainnet
Avalanche C-Chain
Base Mainnet
Yes
Base Sepolia
Blast Mainnet
Yes
Blast Sepolia
Core Mainnet
Yes
Story Mainnet
Yes
Story Odyssey
Yes
Boba Mainnet
Ethereum Kovan
Ethereum Rinkeby
Ethereum Göerli
Yes