# Symmetric Balancer Friendly Fork Proposal **URL:** \ **Category:** General Proposal\ **Created:** [March 22, 2022, 3:26pm UTC](https://forum.balancer.fi/t/symmetric-balancer-friendly-fork-proposal/2634 "2022-03-22T15:26:22Z")\ **Posts on this page:** 1\ **Showing post:** 14
**Author:** ![gerg](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.balancer.fi/gerg/32/200_2.png) [@gerg](https://forum.balancer.fi/u/gerg)\ **Post date:** [March 22, 2022, 7:54pm UTC](https://forum.balancer.fi/t/symmetric-balancer-friendly-fork-proposal/2634/14 "2022-03-22T19:54:47Z")
This comment isn’t directed at the Symmetric team, but rather to the DAO/community that votes on Friendly Fork proposals. It is not intended in any way meant to accuse anyone of ill-intent, but is instead a proposition to the community not to blindly approve a fork without solid, trustless verification. There is undoubtedly a huge amount of work that goes into getting a Friendly Fork off the ground from market/chain identification, to finding a team, to getting all of the many, many the parts together. I do not want to belittle the work on the BalancerDAO side and the forking team side. What I do want to say though is that it’s a massive reputation risk on Balancer to approve any FF that comes along. Especially when teams are anonymous/pseudonymous/etc, there is an even greater risk that something bad could happen. I would therefore like to propose that having deployed, verifiably identical bytecode of the core contracts is an _ **absolute precondition to a FF even being considered** _. I have high hopes for the Hexagon project, for example, but have a really bad taste in my mouth that that vote went through so easily and there are no contracts anywhere to be found. --- _[View the full topic](https://forum.balancer.fi/t/symmetric-balancer-friendly-fork-proposal/2634)._