Skip to content

feat(rwa-yield-accuracy): Sprint 3 — restrict V1 to USDY, mark draft - #1326

Merged
Flotapponnier merged 1 commit into
devfrom
feat/rwa-yield-accuracy-sprint3-staging
Jul 23, 2026
Merged

feat(rwa-yield-accuracy): Sprint 3 — restrict V1 to USDY, mark draft#1326
Flotapponnier merged 1 commit into
devfrom
feat/rwa-yield-accuracy-sprint3-staging

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Sprint 3 of the rwa-yield-accuracy bench. Reality-check pass via WebFetch against Etherscan + issuer sites revealed two blockers for shipping the full 5-token cohort live:

  1. BUIDL, USTB treasury wallet addresses are not visible on the public Etherscan token page. Shipping the dividend probes without verified treasuries would count zero USDC transfers and report -350 bps deviation, entirely an artefact.
  2. BENJI, OUSG NAV JSON endpoints as guessed return HTTP failures (Franklin loads NAV via JS render; Ondo endpoint at guessed path does not exist).

What ships now (V1 = USDY only)

  • Bench spec marked status: draft (tracked in repo, not surfaced on public site)
  • Active cohort in main.go = {USDY}
  • Other 4 probes stay in the repo, fully implemented, dormant. Activate one by one as each treasury / NAV endpoint gets verified.
  • promised-yields.yml updated with real values pulled from issuer dashboards (USDY 3.55%, USTB 3.52%, others best-estimate — 2024 rates before Fed cuts were 5.30-5.40%).

Verification results

Token Confirmed Blocker
USDY ✅ Contract 0x96F6...5C, rebase model, current APY 3.55%
BUIDL ✅ Contract 0x7712...ec, 6 decimals, 59 holders Treasury wallet address needed
USTB ⚠️ Partial contract 0x4341...4e Full contract + treasury wallet needed
BENJI ❌ Ethereum wrapper unknown, NAV endpoint returned JS-only page Contract + JSON endpoint needed
OUSG ✅ Contract 0x1B19...92 NAV JSON endpoint needed (Ondo API not at guessed path)

Path to full V1

Once each item above is verified against the issuer's official documentation, un-comment the corresponding NewXProbe() in main.go and flip the bench to status: live.

Test plan

  • bun run validate — 76 specs valid
  • go build clean
  • go vet clean
  • Deploy to VPS ocb-par-main (Sprint 4)
  • Cross-check USDY 30d delivered vs Ondo dashboard after 30 days of harness uptime

…draft

Cross-check pass via WebFetch revealed two blockers for shipping the
full 5-token cohort live:

  1. BUIDL and USTB treasury wallet addresses are not visible on the
     public Etherscan token page. Shipping the dividend probes without
     verified treasury addresses would count zero USDC transfers and
     report a delivered yield of 0 bps against a promised 350 bps -
     a -350 bps deviation that would look catastrophic and be entirely
     an artefact.

  2. BENJI and OUSG NAV JSON endpoints as guessed (franklintempleton
     .com/api/... and api.ondo.finance/v1/...) return HTTP failures.
     Franklin loads NAV via JS render; Ondo's endpoint does not exist
     at the guessed path. Shipping the NAV probes without verified
     endpoints would report nav_source_err on every tick.

Rather than pollute the bench with placeholder data, V1 restricts
the active cohort to USDY, whose rebase mechanism is fully verifiable
on-chain (single ERC-20 contract, totalSupply growth). The other 4
probes stay in the repo (buidl.go, ustb.go, benji.go, ousg.go), fully
implemented and dormant. They activate one by one as each treasury
address or NAV endpoint gets verified against the issuer's own docs.

Also updates promised-yields.yml with values pulled directly from
issuer dashboards (USDY 3.55%, USTB 3.52%, others best-estimate).
Prior values (5.30-5.40%) reflected 2024 rates before Fed cuts.

The bench spec is marked status: draft so it's tracked in the repo
but doesn't surface on the public site until USDY has run long
enough to publish a defensible 30-day delivered yield.
@Flotapponnier
Flotapponnier merged commit 292a761 into dev Jul 23, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant