Kumbaya: docs cross-links, env deployments, integrator-kit contracts, TimeCurve purchase path (ETH/USDM → CHARM/CL8Y) #46
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:open_issues
agents
agent:security_audit
agent:verify
area
timecurve
arena
arena-v2
audit
block:feature_review
block:security
bug
contracts
design
devops
docs
documentation
enhancement
epic
feature
frontend
indexer
low priority
megaeth
operations
ops
performance
QA
qa checklist
referrals
removal
security
smart-contracts
tech-debt
testing
time-arena
timecurve
visual-qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
code/yieldomega#46
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Improve how we document, deploy, and integrate Kumbaya so Yieldomega stays aligned with upstream guidance and gives users a clearer path to acquire CHARM (including CL8Y / TimeCurve-relevant flows) using ETH and USDM where the protocol allows.
Documentation & cross-linking
Deployment process by environment
Define and document a repeatable process for:
For testnet and mainnet, use Kumbaya’s official contract references and artifacts from their integrator kit rather than ad-hoc copies:
Deliverables should include where in our repo we pin or reference those addresses/ABIs (or a single source of truth doc) so drift is obvious.
Product / integration refactor (where possible)
Acceptance criteria
Notes
Assignee note: Requested assignee
plasticdigtiswas not found on GitLab; assigned @PlasticDigits instead (project namespace owner). If a different username was intended, please reassign.assigned to @PlasticDigits
mentioned in issue #41
mentioned in commit
94c990948a@brouie Please verify the GitLab #46 deliverable merged to
main(commit `93ad90f` on `main`).What shipped
Checklist for you
Worktree `fix/gitlab-46-kumbaya-docs` was merged and removed locally after push.
@PlasticDigits verified on
dec166e/ merge93ad90f. All 5 required checklist items confirmed:Item 1 — Terminology: PASS
Read
docs/integrations/kumbaya.md(85 lines). The doc clearly distinguishes the code labelusdm(lowercase, thePayWithAsset/VITE_KUMBAYA_USDMenv key) from the actual token symbol USDm (MegaUSD per default-token-list on mainnet). Terminology section reads cleanly for an operator briefing.Item 2 — Address parity: PASS
Spot-check against upstream integrator-kit addresses/megaETH-{mainnet,testnet}.json:
Mainnet 4326:
0x4200000000000000000000000000000000000006✅0xE5BbEF8De2DB447a7432A47EBa58924d94eE470e✅0x1F1a8dC7E138C34b503Ca080962aC10B75384a27✅Testnet 6343:
0x4200000000000000000000000000000000000006✅0x8268DC930BA98759E916DEd4c9F367A844814023✅0xfb230b93803F90238cB03f254452bA3a3b0Ec38d✅Item 3 — USDm match: PASS
default-token-list src/tokens/megaeth.json has USDm (MegaUSD) at
0xFAfDdbb3FC7688494971a79cc65DCa3EF82079E7on chainId 4326 — exact match withkumbayaRoutes.tsline 85.Item 4 — Testnet USDM fail-closed: PASS
Traced the path: on 6343,
defaults.usdmis undefined (line 71-77 omits usdm key),usdm = envAddr('VITE_KUMBAYA_USDM') ?? defaults.usdmresolves to undefined, falls toZEROat line 142. Then at line 203-209 the route builder for payWith='usdm' hitsisZeroAddr(config.usdm)and returns{ ok: false, reason: 'missing_usdm', message: 'USDM is not configured for this chain.' }. No silent fallback, no partial execution. Correct fail-closed.Item 5 — Unit tests: PASS
cd frontend && npm test -- --run src/lib/kumbayaRoutes.test.ts→ 13/13 passing, 975ms.Item 6 — Optional testnet smoke: skipped
Not attempted this session. Can be added as a separate verification pass once real USDM pools are deployed and
VITE_KUMBAYA_USDMis configured on a testnet build — at that point the full quote → swap → buy path becomes live-testable. For now the code + unit coverage + address parity is comprehensive.Doc quality notes
docs/integrations/kumbaya.mdsections on upstream refs, naming, product flow, invariants, and env runbooks are well-structured for future contributors.Closing as verified.
mentioned in issue #65
mentioned in issue #206
mentioned in issue #207