feat: make kong source of truth for oracle apr

[matheus1lva]

Description

This PR replaces the legacy on-chain APR Oracle contract integration for V3 vaults with data sourced directly from Kong's GraphQL API. This establishes Kong as the single source of truth for historical APY and forward-looking oracle APR data, simplifying the architecture and reducing RPC calls.

How to Test

1. Build the Application

Compile the yDaemon binary from the source.

go build -o yDaemon ./cmd

2. Prepare Environment

Ensure your .env file is set up with a valid RPC URL for Mainnet (Chain ID 1).

# Example .env content
RPC_URI_FOR_1=https://eth.llama.rpc.com

3. Run yDaemon

Start the server, filtering for Chain 1 to reduce startup time.

./yDaemon -chains 1

4. Verify APR Data

Open a new terminal and query the API for the USDC V3 vault (0xBe53...). This vault is known to have Oracle APR data.

curl -s http://localhost:8080/1/vaults/0xBe53A109B494E5c9f97b9Cd39Fe969BE68BF6204 | jq .apr.forwardAPR

5. Expected Result

The JSON response should contain a valid netAPR value (non-zero) and the type should be v3:onchainOracle.

{
  "type": "v3:onchainOracle",
  "netAPR": 0.04257556654404793,
  "composite": {
    "v3OracleCurrentAPR": 0.04171087783745296,
    "v3OracleStratRatioAPR": 0
  }
}

[murderteeth]

Review Feedback

Breaking Change Found

File: processes/apr/forward.v3.go:68

The current implementation changes the value assigned to V3OracleCurrentAPR:

// Current PR code
V3OracleCurrentAPR: primaryAPR,

Problem: Downstream clients expect V3OracleCurrentAPR to contain the APY value (matching the previous behavior), not the APR. This change breaks backward compatibility.

Fix required:

V3OracleCurrentAPR: primaryAPY,  // Maintain backward compatibility

---

Other Observations

Redundant branching in strategies.go - Lines 102-116 now have identical logic for V3 and non-V3 (both call GetCurrentStrategyAPR). The if/else could be simplified to a single path.

---

[matheus1lva]

// Current PR code
V3OracleCurrentAPR: primaryAPR,

Yeah that one confused me, i thought it was a typo done in the past. Makes sense now.

tests

• curl http://localhost:8080/1/vaults/0xBe53A109B494E5c9f97b9Cd39Fe969BE68BF6204

• You should see

"forwardAPR": {
"type": "v3:onchainOracle",
"netAPR": 0.06499804259456621,
"composite": {
"boost": null,
"poolAPY": null,
"boostedAPR": null,
"baseAPR": null,
"cvxAPR": null,
"rewardsAPR": null,
"v3OracleCurrentAPR": 0.07222130997657228,
"v3OracleStratRatioAPR": 0.06499804259456621
}
}

Inside the apr.forwardApr

[murderteeth]

did you forget to push a commit?

i realize it looks wrong, but this is how it should be set,

V3OracleCurrentAPR: primaryAPY

tx for the detailed test steps

[matheus1lva]

did you forget to push a commit?

i realize it looks wrong, but this is how it should be set,

V3OracleCurrentAPR: primaryAPY

tx for the detailed test steps

oh yes apparently 🫠

[murderteeth]

build error (lint)

~/git/ydaemon go build -o yDaemon ./cmd
# github.com/yearn/ydaemon/processes/apr
processes/apr/forward.v3.go:59:2: declared and not used: primaryAPR

[matheus1lva]

i forget go has built in linter.

Cleaned up.

6e06  HEAD -> feat/kong-oracle-apy-integration
➜  ydaemon git:(feat/kong-oracle-apy-integration) go build -o yDaemon ./cmd     
➜  ydaemon git:(feat/kong-oracle-apy-integration)