# Request: Canonical Balancer V3 deployment on Arbitrum Sepolia (testnet)

**URL:** <https://forum.balancer.fi/t/request-canonical-balancer-v3-deployment-on-arbitrum-sepolia-testnet/7086>\
**Category:** General Proposal\
**Created:** [June 25, 2026, 6:11pm UTC](https://forum.balancer.fi/t/request-canonical-balancer-v3-deployment-on-arbitrum-sepolia-testnet/7086 "2026-06-25T18:11:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![zbam](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/zbam/32/3813_2.png) [@zbam](https://forum.balancer.fi/u/zbam)\
**Post date:** [June 25, 2026, 6:11pm UTC](https://forum.balancer.fi/t/request-canonical-balancer-v3-deployment-on-arbitrum-sepolia-testnet/7086/1 "2026-06-25T18:11:27Z")

</div>

## **Summary**

We’d like to request a canonical Balancer V3 core deployment (Vault, Router, and the Weighted Pool factory) on **Arbitrum Sepolia**. Balancer V3 is already live on Arbitrum One (via [BIP-761](https://forum.balancer.fi/t/bip-761-deployment-of-balancer-v3-on-arbitrum-one/6294)) and on Ethereum Sepolia, but there is currently no deployment on Arbitrum’s testnet, which leaves teams building on Arbitrum + Balancer V3 without a way to integration-test on the same L2 they ship to.

## **Who we are**

We’re building **deCDN** , a decentralized CDN where nodes serve content-addressed data and are paid in USDC over off-chain payment channels. Our protocol token uses a Balancer V3 **80/20 weighted pool** as protocol-owned liquidity: a share of protocol fees is routed on-chain into a USDC→TOKEN buyback that is then burned. We chose Balancer V3 80/20 specifically for the lower seed-capital and reduced-IL profile of a token-heavy weighted pool over a 50/50 constant-product pair.

Our network deploys to **Arbitrum** — testnet on Arbitrum Sepolia, production on Arbitrum One (where V3 already exists).

## **The problem**

Our on-chain buyback contract integrates the V3 Vault/Router/weighted-pool interfaces directly. We can:

- **Fork-test against Arbitrum One** — validates our integration against real V3 bytecode, but gives no live testnet rehearsal of the keeper, fee routing, and end-to-end flow.
- **Use Ethereum Sepolia** — V3 is there, but it’s a different chain from the rest of our testnet node infrastructure, so it’s not a faithful rehearsal of our Arbitrum deployment.
- **Self-deploy the V3 stack on Arbitrum Sepolia** — possible, but a non-canonical deployment isn’t covered by the Balancer SDK, subgraph, or tooling, and doesn’t give us confidence that what we test matches what we ship.

A canonical Balancer V3 deployment on Arbitrum Sepolia would let us (and any other team building on Arbitrum + V3) test against the same contracts, addresses, and tooling we use in production.

## **The ask**

A canonical, registered Balancer V3 deployment on Arbitrum Sepolia — minimally the **Vault** , a **Router** (`swapSingleTokenExactIn` path), and the **Weighted Pool factory** — published in `balancer-deployments` so addresses and ABIs flow through the standard SDK/subgraph tooling.

Since V3 testnet contracts are already maintained for Ethereum Sepolia, extending the same set to Arbitrum Sepolia should be largely incremental rather than net-new work.

## **Ecosystem benefit**

Arbitrum is one of Balancer V3’s largest L2 deployments. A testnet counterpart lowers the integration barrier for every team building V3-based products on Arbitrum — pool creators, aggregators, and protocols (like ours) that wire V3 into their own contracts — without each having to stand up and trust a private deployment.

## **How we can help**

We’re happy to help test the deployment, file any issues we hit against `balancer-v3-monorepo` / `balancer-deployments`, and share our integration as a real-world test case. Glad to provide more detail on our use of the 80/20 weighted pool if useful.

## **Questions for the team**

1. Is a testnet deployment like this something the dev team / Maxis handle directly, or does it need to go through governance?
2. Is Arbitrum Sepolia on the roadmap already, and if so is there a rough timeline?
3. Is there anything we can do to make this easier to prioritize?

Thanks!

---

<div class="post-metadata">

**Author:** ![0xDanko](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/0xdanko/32/1376_2.png) [@0xDanko](https://forum.balancer.fi/u/0xDanko)\
**Post date:** [July 3, 2026, 1:42pm UTC](https://forum.balancer.fi/t/request-canonical-balancer-v3-deployment-on-arbitrum-sepolia-testnet/7086/2 "2026-07-03T13:42:56Z")

</div>

Hey @zbam thank you for reaching out. A governance vote shouldn’t be needed. The team is taking a look and will get back to you soon. Please bear with us! TY.

---

<div class="post-metadata">

**Author:** ![endymionjkb](https://avatars.discourse-cdn.com/v4/letter/e/e99b99/32.png) [@endymionjkb](https://forum.balancer.fi/u/endymionjkb)\
**Post date:** [July 4, 2026, 2:51pm UTC](https://forum.balancer.fi/t/request-canonical-balancer-v3-deployment-on-arbitrum-sepolia-testnet/7086/3 "2026-07-04T14:51:21Z")

</div>

Sure @zbam . It wasn’t on the roadmap, but we’re happy to do it.

I’ll put it on my list, and it should be done within a couple weeks at most.

---

<div class="post-metadata">

**Author:** ![zbam](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/zbam/32/3813_2.png) [@zbam](https://forum.balancer.fi/u/zbam)\
**Post date:** [August 4, 2026, 11:50am UTC](https://forum.balancer.fi/t/request-canonical-balancer-v3-deployment-on-arbitrum-sepolia-testnet/7086/4 "2026-08-04T11:50:14Z")

</div>

Thanks again @endymionjkb and @0xDanko, just checking in on this. It’s been a few weeks since, is there anything we can do to help move it along?

---

<div class="post-metadata">

**Author:** ![endymionjkb](https://avatars.discourse-cdn.com/v4/letter/e/e99b99/32.png) [@endymionjkb](https://forum.balancer.fi/u/endymionjkb)\
**Post date:** [August 4, 2026, 1:39pm UTC](https://forum.balancer.fi/t/request-canonical-balancer-v3-deployment-on-arbitrum-sepolia-testnet/7086/5 "2026-08-04T13:39:34Z")

</div>

I’m going to push and try to get it done this week. Sorry it’s taken so long: very small team (of one for this project: only I have the Vault key), and too much going on.

---

<div class="post-metadata">

**Author:** ![endymionjkb](https://avatars.discourse-cdn.com/v4/letter/e/e99b99/32.png) [@endymionjkb](https://forum.balancer.fi/u/endymionjkb)\
**Post date:** [August 11, 2026, 1:43pm UTC](https://forum.balancer.fi/t/request-canonical-balancer-v3-deployment-on-arbitrum-sepolia-testnet/7086/6 "2026-08-11T13:43:14Z")

</div>

Contracts are now deployed on Arbitrum Sepolia. Just the basics: Vault, core pool types and basic Router. Sorry once more for the delay; let me know if you need anything else!
