PR with Payload
Summary:
This is a proposal to enable the root gauge
0x5fAa5dbE07E4473819D22bB6F5d8179817305d71on Ethereum, [which redirects rewards to the child gauge0xA6254D290344092433263308072C210a101fbD7aonBase,] for the pool0xdd5e47ab9bdb0601e35055bd39a66d5f07aaff8e(30waBasUSDC-70FYNI).This proposal seeks to onboard a 70/30 FYNI/waBasUSDC pool on Balancer v3 (Base) with a 2% emissions cap.
FYNI is a newly launched financial AI agent token on Base, supported by strong community traction and trading activity. A 2% cap will allow FYNI liquidity to scale efficiently while ensuring emissions remain within sustainable guardrails.
References/Useful links:
Link to:
• Website - https://fyni.ai
• Whitepaper - https://fyni.ai/whitepaper.pdf
• Communities - TG - https://t.me/FyniAI
• Other useful links? - X/Twitter: https://x.com/fyniai
Protocol Description:
Meet Fyni — the first-ever Hyper Personalized Financial AI Agent with a complete view of user portfolios across CeFi and DeFi Powered by KryptosConnect, Fyni taps into 5000+ integrations spanning exchanges, wallets, and on/off-chain protocols, giving it the richest financial context of any AI agent.
Fyni is launched using the Genesis Launchpad on Virtuals Protocol.
Use Case: Utility/governance token for Fyni’s agent ecosystem, incentives, and partner integrations.
About Kryptos:
Fyni is powered by Kryptos, the team building Crypto Financial Data Standardization Protocol. Backed by YZi Labs, Gate Labs, Virtuals Ventures and other leading investors — Kryptos recently raised funding at a $35M FDV.
Historic Prices:
We have mainly 2 pools at the moment, one was created on Uniswap during the bonding process of the launch which has the most liquidity and the other one was added on Aerodrome later.
We have put in a $25k liquidity on Balancer now and plan to add more liquidity as we get more tokens unlocked in 3 weeks in accordance with the vesting schedules.
Coingecko: https://coingecko.com/en/coins/fyni-ai
Motivation:
Establish deep FYNI/waBasUSDC on-chain liquidity on Base using Balancer’s weighted pool design. This reduces slippage for trading and routing volume while anchoring FYNI’s price discovery through Balancer. Also this allows liquidity providers to earn yield on their USDC thus making it attractive.
Specifications:
-
Governance: FYNI was deployed via the Virtuals Genesis launchpad (contract: 0x22c0a2e55AeD8B317A285ccbd4f3D8eE24C9e5e3), which has been widely used for secure and transparent launches on Base. The token contract is a standard ERC-20 with no custom mint/burn logic.
-
Oracles: FYNI does not rely on external oracles; all price discovery occurs natively on-chain via AMM pools.
-
Audits: Virtuals launchpad contracts have undergone independent audits and are used by multiple ecosystem projects. FYNI itself inherits these battle-tested deployments.
-
Centralization vectors: FYNI was launched via the Virtuals Genesis platform, which enforces transparent tokenomics and vesting schedules. Full details are published and verifiable here: Virtuals Genesis Dashboard
-
Market History: FYNI has shown normal early-stage volatility but no structural issues. Current market data (source: Coingecko) shows an average daily trading volume of around $250k. The proposed Balancer pool will be a 70/30 FYNI/waBasUSDC, with pool address:
0xdd5e47ab9bdb0601e35055bd39a66d5f07aaff8eand child gauge address on Base:0xA6254D290344092433263308072C210a101fbD7a. For now, we have added $25k in liquidity and plan to add more over the next 3 weeks as new tokens for liquidity unlocks. -
Value: This pool will be the primary weighted FYNI/waBasUSDC liquidity venue on Balancer (Base). We want to make it our primary liquidity pool as well, as it offers advantages to liquidity providers by generating additional yield on USDC. The existing markets have already generated more than $10k in LP fees since the launch on September 4th, so we expect this pool to perform in the same fashion.
Technical Specifications
The Balancer Maxi LM Multisig 0xc38c5f97B34E175FFd35407fc91a937300E33860 will interact with the GaugeAdderv4 at 0x5DbAd78818D4c8958EfF2d5b95b28385A22113Cd and call the addGauge function with the following arguments: gauge(address):0x5fAa5dbE07E4473819D22bB6F5d8179817305d71
gaugeType(string): Base