[BIP-205] Enable relayers on gnosis chain and add other missing permissions
Vote: Yes
Rationale: This is a necessary fix to enable Gnosis chain.
[BIP-206] Deploy Balancer to Avalanche
Vote: Yes
Rationale: The deployment to Avalanche opens up a number of possibilities for further expansion of the Balancer ecosystem.
[BIP-207] Grant Balancer Maxis the authorisation to register protocolIds for LinearPools
Vote: Yes
Rationale: As the ecosystem grows it is important to maintain a logical means of tracking and recording that growth. From the proposal: Creating a boosted pool is permissionless. Therefore a process to register protocols is required to allow data-consumers to distinguish which pool belongs to which protocol, even if the pool has been created from the same factory
[BIP-208] Enable Overnight Pulse Gauge [Arbitrum]
Vote: Yes
Rationale: Overnight.fi was very successful on Optimism and the expansion to Arbitrum has a lot of potential.
[BIP-209] Enable ALCX/ETH (80/20) Gauge on Ethereum
Vote: Yes
Rationale: Alchemix has been a long time supporter of balancer and has recently demonstrated further commitment to the Aura ecosystem. The Aura delegates are in support of this pool with a 2% emissions cap.
[BIP-210] Deprecate Old Stargate Gauges & Add Gauges for STG v2
Vote: Yes
Rationale: As this was initially requested by the Stargate group to enable their migration to v2 of their token, the Aura delegates voted in support of this BIP. The decision not to implement BIP 210 as a result of actions from Alameda and recommendations from the Stargsate foundation, was made clear after the vote was executed.
[BIP-211] Kill Euler Boosted Pool Gauges
Vote: Yes
Rationale: The unfortunate events surrounding the exploit of Euler have made this BIP a necessity.
[BIP-212] Deploy Balancer to zkSync
Vote: Yes
Rationale: zkSync is one of many very promising options in the zkEVM space and is currently supported by an array of other protocols. A Balancer deployment here has extensive upside potential with opportunities for Aura to become involved as described in the forum discussion. The Aura delegates are in support of this proposal.
[BIP-213] Whitelist Yearn’s yBAL Voter Contract for veBAL
Vote Abstain
Rationale: While the delegates feel that the creation of another wrapper very similar to the one created by StakeDAO does not bring a whole lot of value to the ecosystem, they do not wish to stand in the way if other stakeholders wish this to be added, and have chosen to abstain for this vote. They note the decision to propose the gauge vote with a 2% cap limits any potential issues during launch.
[BIP-214] Enable Permissions for BatchRelayer v5
Vote: Yes
Rationale: This upgrade will provide for greater efficiency.
[BIP - 215] Messari reporting 2023 (second vote)
Vote: Abstain
Rationale: The Aura delegates appreciated the frank and open discussions with the Messari authors for this BIP. In the end, the delegates felt that the cost to benefit ratio was not in the interests of the DAO and so decided to abstain.