← All Recipes
Bazantic // Recipe
FINCH_GRAPH_ENS
finch-graph-ens
Given an EVM wallet, trace where its tokenized-stock tokens came from (Finch, Substreams) and resolve every address in the route to an ENS name (The Graph's ENS subgraph).
Recipe inputs
Complete fields before a run.
Output example
Representative published output.
"Perfect! Here are the results:\n\n---\n\n**Summary:**\n`daio.eth` received 0.0117 NVDA, routed through Pons holder-fee distributor `0xe25e9bc31d24bb652fb6e2e466d7c9c89701173e` (no ENS name)\n\n**Routing path:**\n- microduck / NVDA Uniswap V4 pool (Pons Meme Hook) — `0xd5f1afea47b1a9eab414d2ee740cf1d6d039e725` → no ENS name\n- Pons FeeEscrow `0xd3AFEB2a57f70eF218Aa82451c51B2fb0416Ac9e` → no ENS name \n- Pons holder-fee distributor `0xe25e9bc31d24bb652fb6e2e466d7c9c89701173e` → no ENS name\n- Epoch batch distribution → daio.eth + 100 others\n\n---\n\n**Confidence note:** *signal only - not a recommendation*\n\nThis was a Pons fee distribution claim: the NVDA amount represents a holder-fee cut from the microduck token's Uniswap V4 pool, distributed to holders in epoch 975. The unresolved addresses are Robinhood Chain contracts registered with the Pons protocol."