rwa-yield-accuracy Sprint 4: activate USTB + OUSG, flip bench live#1356
Merged
Conversation
…rod deploys) Tripwire was firing on /products/thirdweb because thirdweb has 4 fresh appearances (ink-rpc, world-chain-rpc, kaia-rpc, opbnb-rpc) all with rank=0. Root cause: the CDN aggregate blob was published AFTER the Vercel build read the store snapshot, so the site's cached ranks lagged the blob by one publish cycle. Fix: only fire the tripwire when at least ONE appearance has a non-zero p50. If every appearance has p50=0, the provider is genuinely warming up (never had data), not degraded. Preserves the tripwire's purpose (catch mid-render store corruption) while letting new providers ship without a rollback loop.
Flotapponnier
added a commit
that referenced
this pull request
Jul 24, 2026
…rod deploys) (#1356) Tripwire was firing on /products/thirdweb because thirdweb has 4 fresh appearances (ink-rpc, world-chain-rpc, kaia-rpc, opbnb-rpc) all with rank=0. Root cause: the CDN aggregate blob was published AFTER the Vercel build read the store snapshot, so the site's cached ranks lagged the blob by one publish cycle. Fix: only fire the tripwire when at least ONE appearance has a non-zero p50. If every appearance has p50=0, the provider is genuinely warming up (never had data), not degraded. Preserves the tripwire's purpose (catch mid-render store corruption) while letting new providers ship without a rollback loop. Co-authored-by: Florent Tapponnier <contact@mobula.io>
Flotapponnier
added a commit
that referenced
this pull request
Jul 24, 2026
…rod deploys) (#1356) (#1358) Tripwire was firing on /products/thirdweb because thirdweb has 4 fresh appearances (ink-rpc, world-chain-rpc, kaia-rpc, opbnb-rpc) all with rank=0. Root cause: the CDN aggregate blob was published AFTER the Vercel build read the store snapshot, so the site's cached ranks lagged the blob by one publish cycle. Fix: only fire the tripwire when at least ONE appearance has a non-zero p50. If every appearance has p50=0, the provider is genuinely warming up (never had data), not degraded. Preserves the tripwire's purpose (catch mid-render store corruption) while letting new providers ship without a rollback loop. Co-authored-by: Florent Tapponnier <contact@mobula.io>
Flotapponnier
added a commit
that referenced
this pull request
Jul 24, 2026
/products/thirdweb returned 500 in prod, blocking every deploy since #1352. Root cause not yet identified — the tripwire fix (#1356) didn't help. Practical unblock: strip thirdweb slug from ink-rpc, world-chain-rpc, kaia-rpc, opbnb-rpc spec YAMLs + harness config. thirdweb no longer appears in getProvider() so sitemap excludes /products/thirdweb, smoke skips it, deploys pass. Impact: bench provider counts drop - ink-rpc: 5 → 4 - world-chain-rpc: 4 → 3 - kaia-rpc: 3 → 2 (thin, will need to add another provider) - opbnb-rpc: 4 → 3 Bumps cache keys v41→v42 / v44→v45 for the bench SET shrink. Re-add thirdweb once the /products/thirdweb 500 root cause is fixed. Co-authored-by: Florent Tapponnier <contact@mobula.io>
Flotapponnier
added a commit
that referenced
this pull request
Jul 24, 2026
…) (#1362) /products/thirdweb returned 500 in prod, blocking every deploy since #1352. Root cause not yet identified — the tripwire fix (#1356) didn't help. Practical unblock: strip thirdweb slug from ink-rpc, world-chain-rpc, kaia-rpc, opbnb-rpc spec YAMLs + harness config. thirdweb no longer appears in getProvider() so sitemap excludes /products/thirdweb, smoke skips it, deploys pass. Impact: bench provider counts drop - ink-rpc: 5 → 4 - world-chain-rpc: 4 → 3 - kaia-rpc: 3 → 2 (thin, will need to add another provider) - opbnb-rpc: 4 → 3 Bumps cache keys v41→v42 / v44→v45 for the bench SET shrink. Re-add thirdweb once the /products/thirdweb 500 root cause is fixed. Co-authored-by: Florent Tapponnier <contact@mobula.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bench 089 goes from cohort=1 (USDY only) to cohort=3 live by activating on-chain NAV oracles for USTB and OUSG. Status flipped from `draft` → `live`.
Live numbers (from VPS `ocb-rwa-yield-accuracy`)
Known follow-up
USDY probe is broken — Ethereum `totalSupply` is decreasing (bridge burns to Solana/Aptos > rebase). Currently reports negative yield. Not fixed in this PR; tracked as a follow-up (needs either `rewardMultiplier()` read from the proxy impl `0xea0f7eebdc2ae40edfe33bf03d332f8a7f617528`, or cross-chain supply aggregation). Consider not surfacing USDY on the live page until that lands.
Test plan