Repository navigation
fix: migrate remaining yDaemon vault requests to Kong - #259
Merged
Merged
Conversation
|
Deploy preview for y-partners ready!
Deployed with vercel-action |
matheus1lva
marked this pull request as ready for review
October 19, 2026 11:08
engn33r
approved these changes
Oct 19, 2026
engn33r
left a comment
Collaborator
There was a problem hiding this comment.
all lgtm, no ydaemon references remain after these edits
This branch was successfully deployed
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
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.
Description
Replace the four remaining yDaemon requests with Kong REST: selected vault names, vault/strategy detection, the landing-page vault count, and the fee metadata fallback.
meta.kind.New environment variables: none. Public REST requests use
https://kong.yearn.fi/api/rest. ExistingKONG_GRAPHQL_URLstill controls the separate GraphQL metadata client. No Price Service integration is needed for these four calls.Related Issue
Part of the yDaemon migration to Kong and the Yearn Price Service.
Motivation and Context
Remove these runtime yDaemon dependencies while preserving archive-RPC profit and fee accounting. The snapshot already returns both fee fields, so this does not require a Kong API change.
How Has This Been Tested?
Static source and diff review. Live GET requests to the public Kong list and the Ethereum USDT-1 snapshot succeeded; the snapshot returned
meta.kind: "Multi Strategy", management fee0and performance fee1000basis points.A paired live read of that vault returned identical historical net yield (
0.03372622154868998) and TVL (5687466.9223230425) from yDaemon and Kong. yDaemon’s performance fee0.1matches Kong’s1000basis points. These are observations of the API data, not accounting regression tests.Tests, lint, builds and typechecks were not run. This draft needs application and accounting validation before merge.
Resources