Karpatkey Delegate Thread

Voting Actions - July 21st - 25th

Proposal: [BIP-860] Ecosystem ONsite Proposal Q4 2025

Vote: Yes, let’s do it
Reasoning: Real-life gatherings are beneficial for enhancing alignment and boosting the team’s productivity.


Proposal: [BIP-861] Grant Permissions to the Balancer Registry Initializer

Vote: Yes, let’s do it
Reasoning: Technical vote to grant permission on additional chains (Avalanche, Optimism, and HyperEVM).


Proposal: [BIP-862] Deploy Balancer v3 on HyperEVM

Vote: Yes, let’s do it
Reasoning: We support the multi-stage approach for the expansion to a new chain.

Voting Actions - July 28th - Aug 1st

Proposal: [BIP-863] Incorporation of a legal structure for Balancer Treasury and Finance Operations

Vote: Yes, let’s do it

Reasoning: We support this proposal. The reasoning can be found here.

Voting Actions - August 4th - 8th

Proposal: [BIP-864] Enable RZR/wstETH 80/20 Gauge on Balancer v3 Ethereum

Vote: Yes, let’s do it.
Reasoning: We support this proposal. The team has seeded the pool, and it will be the primary source of liquidity.

Voting Actions - August 11th - 15th

Proposal: [BIP-865] Grant Emergency subDAO Missing v3 Pool Factory Disable Permissions

Vote: Yes, let’s do it.
Reasoning: We support granting these permissions. This request is a result of cross-checking existing permissions against required v3 factory disable permissions.


Proposal: [BIP-866] Enable TREE/WETH 80/20 Pool Gauge on Balancer v3 Ethereum with a 5% cap

Vote: Yes, let’s do it.
Reasoning: The protocol will incentivise liquidity for the pool, which will serve as its primary liquidity source.

Voting Actions - August 18th - 22nd

Proposal: [BIP-867] Grant Universal Gauge Management Permissions

Vote: Yes, let’s do it.
Reasoning: We support this change. It will reduce the complexity but will keep the final decision to governance.


Proposal: [BIP-868] Enable EURe/USDC gauge on Arbitrum (uncapped)

Vote: Yes, let’s do it.
Reasoning: We support gauges for stablecoins pools, as they can potentially increase fees revenue and trading volume for the protocol.

Voting Actions - August 25th - 29th

Proposal: [BIP-869] Enable AAVE/WETH reCLAMM Gauge on Balancer v3 Ethereum and Arbitrum

Vote: Yes, let’s do it.
Reasoning: We support this proposal, as it will help this pool to unlock its full potential and highlight the benefits of the reCLAMM technology.


Proposal: [BIP-870] Enable tAVAX-waAvaSAVAX Pool Gauge on Balancer v3 Avalanche with a 5% cap

Vote: Yes, let’s do it.
Reasoning: We support LST/LRTs gauges as a general rule, as it improves Balancer’s revenue.

Voting Actions - September 1st - 5th

Proposal: [BIP-871] Balancer ↔ QuantAMM Protocol Fee Framework

Vote: Yes, let’s do it
Reasoning: We are supportive of this proposal. The fee framework outlined here strikes a fair balance between Balancer DAO and QuantAMM, ensuring aligned incentives for both sides. By following the principles of BIP-734, the agreement maintains consistency with Balancer’s broader protocol fee structure while accommodating the specific dynamics of QuantAMM pools.

Voting Actions - September 8th - 12th

Proposal: [BIP-872] Enable FYNI/waBasUSDC 70/30 Pool Gauge on Balancer v3 (Base) with a 2% Cap

Vote: Yes, let’s do it
Reasoning: We support this proposal. The protocol will make it the primary liquidity source for the token and will incentivise the pool.

Voting Actions - September 15th - 19th

Proposal: [BIP-873] Balancer Ecosystem Roadmap Proposal and Funding

Vote: Yes, let’s do it
Reasoning: We support this proposal, and you can see the reasoning here.


Proposal: [BIP-874] Urgent Proposal: Deploy Balancer v3 on Plasma

Vote: Yes, let’s do it
Reasoning: We support this proposal, as it is strategically important to be deployed at launch.

Voting Actions - September 29th - October 3rd

Proposal: [BIP-875] Implement EZKL Dynamic Fee Control for Balancer Pools

Vote: Yes, let’s do it
Reasoning: Dynamic fee adjustment has demonstrated strong potential to increase protocol and LP revenue, as evidenced by the production tests showing up to 10–30% higher fee performance compared to static configurations.

We look forward to the results of the 3-month trial and support expanding the model if the data confirms its impact.


Proposal: [BIP-876] Enable Gauge for USDp/USDC Stable Pool with a 2% cap (Base)

Vote: Yes, let’s do it
Reasoning: We support this proposal. Enabling the gauge will enhance liquidity for USDp. The pool’s adaptive fee design enhances capital efficiency and DAO revenue, while the 2% cap ensures a balanced and low-risk rollout.


Proposal: [BIP-877] Kill Stale Gauges Q3 2025

Vote: Yes, let’s do it
Reasoning: We support this housekeeping item.


Proposal: [BIP-878] Enable Gauge for USDp/frxUSD Stable Pool with a 2% cap (Base)

Vote: Yes, let’s do it
Reasoning: We support this proposal. Enabling the gauge will enhance liquidity for USDp. The pool’s adaptive fee design enhances capital efficiency and DAO revenue, while the 2% cap ensures a balanced and low-risk rollout.

Voting Actions - October 6th - 10th

Proposal: [BIP-879] Deploy Balancer v3 on X Layer - OKX chain

Vote: Yes, let’s do it
Reasoning: We support deploying Balancer v3 on X Layer as a strategic, low-risk expansion that positions the protocol early in a promising new ecosystem. With Aave confirmed as a launch partner and OKX driving user and liquidity growth, Balancer’s presence from day one can secure its role as the core liquidity layer for DeFi and payments on X Layer.

The phased approach with measurable checkpoints ensures accountability — we scale only if the deployment meets clear TVL, utilization, and revenue milestones. This mitigates risk while keeping the DAO flexible to adapt or pause if conditions change.

Importantly, this proposal requires no direct treasury spend, leverages audited contracts, and aligns with our broader multi-chain strategy of anchoring where Aave and other key partners expand.

Overall, it’s a prudent, opportunity-driven move that balances growth potential with strong operational safeguards.

Voting Actions - October 13th - 17th

Proposal: [[BIP-880] Enable Gauge for USDp/mevUSDC Stable Pool with a 2% cap (Avalanche)(https://snapshot.org/#/s:balancer.eth/proposal/0xeb5fd1093eadbc52ffcf82e4e879f6c9ee3de70ff9922f8f0d8087f7bef2e298)

Vote: Yes, let’s do it
Reasoning: We support the proposal. The pool will serve as a key route for arbitrage and on-chain liquidity, strengthening USDp’s market depth. We are generally supportive of stablecoin and yield-bearing asset pools that have the potential to enhance Balancer’s revenue.

Voting Actions - October 20th - 24th

Proposal: [BIP-881] Enable Gauges for xusd/mevUSDC + xbtc/mevBTC Stable Pool (Avax), xusd/USDC Varlamore Growth Stable Pool (Arbitrum), xusd/vgUSDC Stable Pool (Mainnet); all with a 2% cap

Vote: Yes, let’s do it.
Reasoning: We generally support stable, yield-bearing asset pools that expand on-chain liquidity and promote sustainable revenue for Balancer.

Voting Actions - October 27th - 31st

Proposal: [BIP-882] Transitioning Onchain Operations of the Balancer DAO to Balancer Onchain Limited

Vote: Yes, let’s do it
Reasoning: The reasoning can be found here.


Proposal: [BIP-883] Emergency Safe Governance Improvements Q4 2025

Vote: Yes, let’s do it
Reasoning: From a governance and operational risk perspective, both changes are aligned with good practice.

  • The adjustment from 4/7 to 3/7 improves the execution reliability of emergency actions without eroding checks and balances, as a majority of independent entities is still required.
  • The removal of disableQueryPermanently() removes an unnecessary and high-impact permission, reducing the governance blast radius in the event of key compromise.

Proposal: [BIP-884] Wire Up BAL Token on Plasma Chain

Vote: Yes, let’s do it
Reasoning: Plasma hit the required checkpoints and has demonstrated real traction. The proposal enables the cross-chain comms needed for veBAL + BAL emissions on Plasma, unlocking the next layer of incentives and governance integration for that deployment.


Proposal: [BIP-885] Permissions Update Request #7

Vote: Yes, let’s do it
Reasoning: We support this proposal as it grants the necessary permissions to handle new assets and delegate voting power to Balancer’s platform at Polygon.


Proposal: [BIP-886] Enable Gauge for Nerite Surge eeUSDC-yUSND Stable Pool with 2% Cap on Arbitrum

Vote: Yes, let’s do it
Reasoning: The pool is already live, both assets are yield-bearing stables, and the protocol is committing bribes to bootstrap initial liquidity — so the incentives alignment is there. From a Balancer ecosystem standpoint, this adds depth to stablecoin routing on Arbitrum and is consistent with how we’ve been scaling v3 liquidity across chains.

Voting Actions November 10th - 14th

Proposal: [BIP-887] Transitioning to Balancer v3: Disabling v2 Pool Factories

Vote: Yes, let’s do it
Reasoning: We support this proposal. Fully disabling the remaining v2 pool factories is a necessary and responsible step now that Balancer v3 offers a more secure, resilient, and operationally efficient architecture.


Proposal: [BIP-888] Migrate mainnet rETH Gauge

Vote: Yes, let´s do it
Reasoning: We support this proposal. The v2 rETH/WETH pool has already been deprecated due to a security concern, so migrating incentives to the new v3 rETH-waEthWETH pool helps to preserve efficient rETH liquidity on Balancer.

Voting Actions November 17th - 21st

Proposal: [BIP-889] Deploy Balancer v3 on Monad

Vote: Yes, let’s do it
Reasoning: We support this proposal. The phased approach has proven itself to be a great strategy, and the monad mainnet launch is attracting great interest.


Proposal: [BIP-890] Revoke Delegation of Governance Tokens in Treasury

Vote: Abstain
Reasoning: We abstain from this vote, as it is related to a delegation granted to kpk.

Voting Actions November 24th - 28th

Proposal: [BIP-891] Increase Gauge Cap for GOLD/st-yETH Pool to 15%

Vote: No, that is not the way
Reasoning: yETH was hacked.

Voting Actions December 8th - 12th

Proposal: [BIP-892] Distribution of Rescued Funds from Balancer v2 November 3rd 2025 Attacks

Vote: Yes, let’s do it.
Reasoning: We support BIP-892 as it operationalises the intent of BIP-726 by establishing a clear, compliant, and non-retainable whitehat reward framework while ensuring LPs are reimbursed on a per-pool, per-network, non-socialised basis. Paying bounties in-kind (10% of the rescued token, capped at $1M, non-retainable) eliminates pricing volatility, simplifies multi-network settlements, and preserves accounting clarity for the DAO. Excluding the internal Certora-coordinated rescue from Safe Harbor bounties is correct, as it maintains the agreement’s original purpose—incentivizing external whitehats, not compensating existing service relationships.

The pro-rata BPT snapshot methodology and Payment-in-Kind LP reimbursement protect against socialised losses and align distribution with verifiable ownership before exploit execution. The proposed 180-day claim window and dormant-asset follow-up process strike a reasonable balance between user agency, process fairness, and governance accountability.


Proposal: [BIP-893] Reconfigure the Protocol Swap Fee for the ReCLAMM Pool Type

Vote: Yes, let’s do it.
Reasoning: We support this proposal because the current 50% protocol swap-fee retention is demonstrably impairing the economics of ReCLAMM pools, creating excessive drag on LP positions, particularly in volatile pairs, and validated simulations and live-pool data both indicate that fee extraction at this level can approach unsustainable annualized costs, undermining liquidity incentives and the long-term viability of the pool type. Reducing the protocol swap fee to a more balanced 25%—a data-backed yet cautious adjustment—directly addresses this misalignment, improves LP profitability, preserves a sustainable protocol-fee stream, and enables a healthier feedback loop between liquidity provision and pool growth, while ongoing monitoring post-implementation ensures governance retains flexibility to recalibrate if needed.


Proposal: [BIP-894] Kill Stream Gauges

Vote: Yes, let’s do it.
Reasoning: We support this proposal because the Stream Finance incident has left the underlying assets depegged and illiquid, and recent data shows the affected gauges direct emissions to pools with no productive use or trading volume. Killing these Stream gauges is a necessary governance step to stop incentive misallocation and preserve the integrity of the DAO’s emissions framework.


Proposal: [BIP-895] QuantAMM Retroactive Fee Allocation

Vote: Yes, let’s do it.
Reasoning: We support this proposal because it corrects a clear fee-routing error under an already-approved agreement (BIP-871), ensuring QuantAMM contributors receive the fees they were entitled to while maintaining fairness for veBAL holders through a transparent, one-time adjustment in the next distribution, without requiring clawbacks or setting a harmful precedent.

Voting Actions December 15th - 19th

Proposal: [BIP-896] Rocket Pool Balancer Alliance Addendum

Vote: Yes, let’s do it
Reasoning: We support this proposal because extending the BIP-822 grandfathered revenue-sharing treatment to the new v3 rETH/WETH pool preserves the integrity of an existing alliance, maintains continuity after a necessary v2 deprecation due to security risks, and protects liquidity incentives while Rocket Pool scales toward meeting standard revenue-sharing criteria.


Proposal: [BIP-897] Gauge proposal for iUSD-msUSD with 5% cap

Vote: Yes, let’s do it
Reasoning: We support this proposal because the iUSD-msUSD Composable Stable pool will serve as essential liquidity infrastructure for upcoming Odyssey looping vaults, enabling efficient entry/exit swaps and healthy liquidation flows, while the 5% emissions cap adds prudent risk control and ensures incentives remain proportionate as the ecosystem scales.

Voting Actions January 5th - 9th

Proposal: [BIP-898] Migrate mainnet ALCX/ETH 80/20 gauge and Core Pool status to new v3 pool

Vote: Yes, let’s do it
Reasoning: We support BIP-898, as migrating the ALCX/ETH 80/20 gauge and Core Pool status from the deprecated v2 pool to the new v3 pool aligns with Balancer’s broader transition to v3 infrastructure. The proposal preserves existing parameters while ensuring LPs benefit from the more resilient v3 design, maintaining continuity of incentives and fee routing without introducing additional risk or emissions changes.


Proposal: [BIP-899] Gauge proposal for msUSD/USDC & msUSD/msY

Vote: Yes, let’s do it
Reasoning: These gauges should improve msUSD price stability, routing, and on-chain usability while creating a clear venue for msUSD↔msY flows, and the modest 2% caps appropriately limit risk while allowing veBAL voters to allocate incentives based on real usage and fee generation.


Proposal: [BIP-900] Enable Gauge for 60GOLD/40wstETH Pool at 10% cap

Vote: Yes, let’s do it
Reasoning: Pairing GOLD with wstETH materially improves the risk profile while preserving Ethereum liquidity for the GOLD ecosystem, and a 10% cap provides sufficient room for veBAL voters to support this strategic pool without overcommitting emissions.


Proposal: [BIP-901] Increase Gauge Cap for TETU/USDC 80/20 Pool to 5%

Vote: Yes, let’s do it
Reasoning: The higher cap does not mandate additional emissions but gives veBAL voters flexibility to direct incentives, while supporting deeper, more resilient liquidity paired with a stable asset and a fully circulating token.


Proposal: [BIP-902] Enable Gauge For 25% Bal / 25% Aura / 50% wabasUSDC

Vote: Yes, let’s do it
Reasoning: Enabling this gauge helps bootstrap meaningful BAL/AURA liquidity on Base while integrating yield-bearing waBasUSDC, which should improve capital efficiency for LPs and routing quality for traders.


Proposal: [BIP-903] Transition Core Pool Incentive Program to Stake DAO’s Votemarket v2

Vote: Yes, let’s do it
Reasoning: Consolidating both Balancer and Aura incentives on a single, well-understood platform reduces operational complexity while preserving the existing mechanics and alignment established by BIP-19 and BIP-457.


Proposal: [BIP-904] Balancer V3 Hypernative Pause Module Enablement

Vote: Yes, let’s do it
Reasoning: We support this proposal, as it strengthens Balancer V3’s real-time defenses with a proven, automated last line of protection against exploits. Following the recent V2 incident, giving the Emergency subDAO a pre-approved, rapidly executable mechanism to pause affected pools or vaults across all V3 networks is a prudent risk mitigation step that meaningfully reduces potential damage while still remaining under multisig oversight