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) 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
- Is a testnet deployment like this something the dev team / Maxis handle directly, or does it need to go through governance?
- Is Arbitrum Sepolia on the roadmap already, and if so is there a rough timeline?
- Is there anything we can do to make this easier to prioritize?
Thanks!