[BIP-84] Revoke Hexagon’s Friendly Fork Status

---

title: [BIP-84] Revoke Hexagon’s Friendly Fork Status status: RFC, then proposed author: @gerg created: 22-07-2022

---

Motivation

The Balancer Friendly Fork framework came about to encourage teams to deploy Balancer V2 contracts, subgraph, and a frontend for chains on which the Balancer DAO has not prioritized. The framework is meant to benefit the deploying teams with a seal of approval and the Balancer DAO with a revenue/token split. Ensuring benefits of a friendly fork should be a high priority for the DAO.

The governance vote approving Hexagon passed approximately seven months ago. Immediately following, Symmetric was denied FF status on the grounds of not yet having a product/deployment to show; Hexagon was not revoked at this time out of respect for governance’s decision. In those ~7 months since Hexagon got their FF status, they have still delivered nothing and communicated nearly nothing other than what was said in this forum thread.

Proposal

• Revoke the Hexagon Friendly Fork existing designation, but do not bar Hexagon from re-applying when/if they have a delivered a full deployment
• Formalize the requirement that teams applying for FF status must have a functional deployment consisting of core contracts (w/ identical bytecode), subgraph, and frontend before applying

Core contracts include:

• Vault, (Timelock) Authorizer
• Weighted Pools
• Composable Stable Pools
• LBPs
• Linear Pools (if appropriate external protocols exist on that chain)
• Boosted Pools (if linear pools are deployed)

Implementation

Since Friendly Forks are social agreements, no on-chain actions are required

Specification

Again, no on-chain actions are required

Disclaimer

All opinions my own