As the gauge deployer address = manager is the only one who can set token and distributor, if somebody outside is deploying the gauge, pool need to be deployed. On L2 deployment is almost free and has been available in the front end for some time , so this happens
We had this situation several times:
- it generates FE pollution (on re-deploy)
- it generates support request
solution: on deploy of the pool we should also deploy the gauge!
As the gauge deployer address = manager is the only one who can set token and distributor, if somebody outside is deploying the gauge, pool need to be deployed. On L2 deployment is almost free and has been available in the front end for some time , so this happens
We had this situation several times:
solution: on deploy of the pool we should also deploy the gauge!