Network Information

UMA Contract AddressesChain IDFully Permissionless SettlementBot SupportDVM SupportoSnap SupportOracle 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

81457

Yes

Yes

Yes

No

168587773

Yes

No

Yes

No

No

1116

Yes

Yes

Yes

Yes

Boba Mainnet (Deprecated)

288

Yes

No

No

No

No

Ethereum Kovan (Deprecated)

42

n/a

n/a

No

No

No

Ethereum Rinkeby (Deprecated)

4

n/a

n/a

No

No

No

Ethereum Göerli (Deprecated)

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.

Last updated