# \[BIP-916\] Set Network Remapping Manager for StakeDAO

**URL:** <https://forum.balancer.fi/t/bip-916-set-network-remapping-manager-for-stakedao/6988>\
**Category:** General Proposal\
**Created:** [March 10, 2026, 11:01am UTC](https://forum.balancer.fi/t/bip-916-set-network-remapping-manager-for-stakedao/6988 "2026-03-10T11:01:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![maxyz.xyz](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/maxyz.xyz/32/3806_2.png) [@maxyz.xyz](https://forum.balancer.fi/u/maxyz.xyz)\
**Post date:** [March 10, 2026, 11:01am UTC](https://forum.balancer.fi/t/bip-916-set-network-remapping-manager-for-stakedao/6988/1 "2026-03-10T11:01:40Z")

</div>

## PR with Payload

> <https://github.com/BalancerMaxis/multisig-ops/pull/2724>
>
> \- Allow StakeDAO to manage cross-chain boost
> \- Forum post link: tbd
> \- See MD f…ile for intent / forum prop draft

## Motivation

StakeDAO is launching their OnlyBoost strategies, which optimally allocate boost between StakeDAO and Aura on sidechains (Base and Arbitrum initially). To enable cross-chain boost for their veBAL position, the StakeDAO multisig needs to be designated as the `NetworkRemappingManager` for their veBAL locker on the [VotingEscrowRemapper](https://etherscan.io/address/0x83e443ef4f9963c77bd860f94500075556668cb8) contract. This grants StakeDAO the ability to call `setNetworkRemapping`, allowing them to manage their own L2 boost addresses.

This follows the same procedure as [BIP-341](https://forum.balancer.fi/t/bip-341-enable-tetu-cross-chain-boost/5007), which enabled cross-chain boost for Tetu.

## Specification

The DAO Multisig `0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f` will execute a single transaction batch on **Ethereum mainnet** :

1. **Grant permission** : Call `grantRole` on the Authorizer (`0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6`) with:

2. **Set remapping manager** : Call `setNetworkRemappingManager` on the VotingEscrowRemapper (`0x83E443EF4f9963C77bd860f94500075556668cb8`) with:

3. **Revoke permission** : Call `revokeRole` on the Authorizer to remove the `setNetworkRemappingManager` permission from the DAO Multisig.

## Risk Assessment

Low risk. The permission is granted and revoked atomically within the same transaction batch, so the DAO Multisig never retains the elevated permission beyond execution. The `setNetworkRemappingManager` function only designates who can manage L2 boost remappings for a specific veBAL locker — it does not grant access to any funds.

---

<div class="post-metadata">

**Author:** ![maxyz.xyz](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/maxyz.xyz/32/3806_2.png) [@maxyz.xyz](https://forum.balancer.fi/u/maxyz.xyz)\
**Post date:** [March 12, 2026, 6:50am UTC](https://forum.balancer.fi/t/bip-916-set-network-remapping-manager-for-stakedao/6988/2 "2026-03-12T06:50:53Z")

</div>

[https://snapshot.org/#/s:balancer.eth/proposal/0xf7f82dbf06343b6f3b77ddc029d6a295f15bbf6a9cae02a6d66e1a5f89746041](https://snapshot.org/#/s:balancer.eth/proposal/0xf7f82dbf06343b6f3b77ddc029d6a295f15bbf6a9cae02a6d66e1a5f89746041)