Question 1

How do I deploy Balancer frontend v2 to Netlify?

Accepted Answer

Use the Netlify deploy button in the README, which clones the repo and prompts for required API keys like Infura and Alchemy. Ensure you configure environment variables for these keys in Netlify's dashboard post-deployment.

Question 2

Balancer frontend v2 vs v3: what are the key differences?

Accepted Answer

Frontend v2 is deprecated and lacks new features from v3, such as updated UI components and integrations with Balancer's latest protocol changes. V3 is the actively maintained version available at balancer.fi, while v2 is only useful for legacy veBAL access or code reference.

Question 3

Can I still use the veBAL page in frontend v2?

Accepted Answer

Yes, the veBAL page remains accessible at app.balancer.fi/vebal and is maintained until migration to v3. However, other features like token swaps are deprecated and should be avoided for new deployments.

Question 4

Is Balancer frontend v2 secure to self-host for production?

Accepted Answer

No, due to its deprecated status, it may have unpatched security vulnerabilities. For production use, rely on the official v3 frontend or thoroughly audit and update dependencies if forking v2.

Question 5

How to customize the token swap interface in frontend v2?

Accepted Answer

Modify the Vue components in the source code, such as those under src/views, and rebuild using npm run build. Note that changes may require updates to polyfills or API integrations, given the deprecated nature.

Question 6

What alternatives exist for building a custom Balancer UI?

Accepted Answer

Consider forking the active frontend-v3 repo or using Balancer's SDK and smart contracts directly. Other DeFi frontend templates, like Uniswap's interface, might offer more current examples for Ethereum-based swaps.

Balancer

What is Balancer?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions