[BIP XXX] Permissions Update Request #9

General Chat Karpatkey Updates
1

PR with payloads

Note: This new permission request was created to accelerate the release of the previously reviewed permissions that remained in PUR#8 (ARB and Gnosis Chain). It covers the requests for Ethereum Mainnet, and no changes were made to the requested permissions beyond clarifications and incorporating feedback for transparency.

Abstract

This proposal requests BalancerDAO’s approval for updates and new actions to the permissions policy governing the kpk-managed treasuries on Ethereum Mainnet.

The proposed changes expand the existing permissions to include new strategies, protocols, swaps, and bridging routes, while removing obsolete or deprecated contracts and interactions. They also streamline kpk’s fee-collection process and revoke the delegation’s permissions from the Zodiac Roles Modifier, as outlined in BIP-890.

The additional permissions focus on strategies that aim to increase the treasury’s risk-adjusted yield without introducing material new risk vectors to the current allocation. These include allocations to Aave Umbrella, Ethena, Spark, Resolv, new markets on Compound as well as kpk-curated vaults on Morpho and curated markets on Gearbox, among others.

Motivation

Treasury management must evolve in line with market conditions and protocol developments, including migrations, new pool launches, and improved access to financial instruments. Protocols and pools previously assessed as too immature or risky for BalancerDAO may become viable over time as they demonstrate reliability, liquidity, and operational robustness.

The proposed additions will allow kpk to implement advanced investment strategies such as delta-neutral stablecoin exposure, curated vaults, and the upgraded version of the Aave safety module, while deprecating outdated or higher-risk contracts.

Changes to the Permissions Policy

This proposal outlines the following modifications to the permissions policy:

Ethereum Mainnet:

  • Aave Umbrella: deposit and withdraw USDC, USDT, WETH, GHO
  • Compound markets: deposit and withdraw ETH, USDT, USDS
  • Ethena: stake, unstake and withdrawal of USDE/sUSDE
  • Spark:
    • Savings: deposit and withdraw of USDC, USDT
    • Markets: deposit and withdraw of USDT, USDC
  • Morpho: deposit and withdraw - kpk EURC, kpk USDC, kpkETH
  • Gearbox: deposit and withdraw of wstETH, ETH
  • Balancer v2: unwinding permissions for USDC/WETH, BAL/WETH, 80BAL/20WETH
  • Gyroscope: revoke GYD and sGYD
  • Merkl rewards claim: GHO and stGHO
  • oETH: whitelist “OETH.rebaseOptIn()” function, related to fee accruing.
  • Swaps (Cow Swap):
    • COW, SYRUP <> USDC, ETH, WETH
    • aETHBAL, aBAL, anyBAL, ETH, WETH <> aETHBAL, aBAL, anyBAL, ETH, WETH
    • USR, stUSR, wstUSR, USDE, sUSDE, stUSD, USDA, DAI, USDT, USDC<> USR, stUSR, wstUSR, USDE, sUSDE, stUSD, USDA, DAI, USDT, USDC
    • EURC, AaveEURC, EURA, stEUR <> EURC, AaveEURC, EURA, stEUR
  • Bridge:
    • Omnibridge:
      • Update and addition of the following bridging routes from Mainnet to Gnosis Chain: USDC, USDT, WBTC, WETH, USDS
  • Roles:
    • Removal of stkAAVE’s delegation permissions
    • Allowance for transferring max. 100k USDC/quarter to kpk treasury for fee payment

Zodiac Roles Modifier Permissions Policy

Permissions page

Ethereum: link here

Permissions diff page

Ethereum: link here

Changes & Clarifications Following Forum Feedback (BIP-909 Thread)

Following feedback raised on the PUR#8 forum discussion (BIP-909), we are incorporating the following clarifications and adjustments in PUR#9:

Tx 0 — Fee Allowance Decimal Clarification

The quarterly allowance for fee payments reflects 100,000 USDC (6 decimals). The raw value has been corrected accordingly.

Tx 10 and 21 — sUSDS Deposit

Spark updated the UI to use a different deposit function for exchanging USDS into sUSDS:

  • Old: deposit(uint256 assets, address receiver)
  • New: deposit(uint256 assets, address receiver, uint16 referral)

That’s why the permission changed accordingly.

Revocations Clarification

Revocations included in this PUR (legacy bridge, sGYD, delegation calls, etc.) reflect cleanup of deprecated or no-longer-used infrastructure and are not tied to new risk concerns.

1 Like