Feat/gsteenkamp/managed disputer

[gsteenkamp89]

closes FE-388

[linear]

FE-388 Upgraded Oracle dApp able to detect and support the upgraded MOOv2 implementation version

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
amoy-optimistic-oracle-dapp-v2	Ready	Preview, Comment	Feb 17, 2026 1:02pm
optimistic-oracle-dapp-v2	Ready	Preview, Comment	Feb 17, 2026 1:02pm
optimistic-oracle-dapp-v2 (mirror-managed-oo)	Ready	Preview, Comment	Feb 17, 2026 1:02pm
sepolia-optimistic-oracle-dapp-v2	Ready	Preview, Comment	Feb 17, 2026 1:02pm

[0xjorgen]

Nit/suggestion (not a blocker for this PR): The raw string "Managed Optimistic Oracle V2" is now compared in many places across the codebase — this PR adds a few more. A typo in any one of them would silently break.

Would it be worth converting oracleTypes from an array to an as const object? This is already the pattern used by chainsById in the same file:

// shared/constants/oracle.ts
export const oracleTypes = {
  OOV1: "Optimistic Oracle V1",
  OOV2: "Optimistic Oracle V2",
  OOV3: "Optimistic Oracle V3",
  SkinnyOO: "Skinny Optimistic Oracle",
  SkinnyOOV2: "Skinny Optimistic Oracle V2",
  ManagedOOV2: "Managed Optimistic Oracle V2",
} as const;

Then comparisons become oracleType === oracleTypes.ManagedOOV2 — autocomplete-friendly and typo-proof.

Bonus: isValidOracleType in util.ts currently does oracleType in oracleTypes, but in on an array checks indices, not values — so it's likely broken today. Switching to an object would fix that for free.

Not necessarily for this PR, but could be a nice follow-up.

[gsteenkamp89]

Nit/suggestion (not a blocker for this PR): The raw string "Managed Optimistic Oracle V2" is now compared in many places across the codebase — this PR adds a few more. A typo in any one of them would silently break.

Would it be worth converting oracleTypes from an array to an as const object? This is already the pattern used by chainsById in the same file:

// shared/constants/oracle.ts
export const oracleTypes = {
  OOV1: "Optimistic Oracle V1",
  OOV2: "Optimistic Oracle V2",
  OOV3: "Optimistic Oracle V3",
  SkinnyOO: "Skinny Optimistic Oracle",
  SkinnyOOV2: "Skinny Optimistic Oracle V2",
  ManagedOOV2: "Managed Optimistic Oracle V2",
} as const;

Then comparisons become oracleType === oracleTypes.ManagedOOV2 — autocomplete-friendly and typo-proof.

Bonus: isValidOracleType in util.ts currently does oracleType in oracleTypes, but in on an array checks indices, not values — so it's likely broken today. Switching to an object would fix that for free.

Not necessarily for this PR, but could be a nice follow-up.

The current oracleTypes is already a readonly tuple and TSC will throw if I make a spelling error. I also get nice intellisense already.

But your 2nd point is definitely a bug. I think, so reduce the diff, I will keep the constant as-is, but just use the correct .includes() check inside isValidOracleType