Thanks for the intro @0xMaki. Addressing the relevant technical points here.
My question remains regarding the autonomy of the Aura contracts. - @LongJuanSilverado
Good topic here ser. Yes, we are also concerned about the centralisation/opacity of the Convex governance. To solve this, we have done the following:
- supported ERC1271 to allow snapshot votes to be made to the Balancer snapshot on chain
- added vote delegation on chain to our vlAURA contract
- composed 2 multisigs (treasury: 3 of 5 and dao: 4 of 7) comprised of known DeFi industry professionals, and will look to fill 2 of the 7 initial dao multisig spots with Balancer ecosystem participants (e.g. Ballers)
Initially, the voting on Aura will be done on a snapshot, and forwarded via the dao multisig. However, with support of the delegation and ERC1271, we will transition both Aura internal governance and Balancer vote forwarding to on chain solutions as soon as is reasonable (~3-4 months).
I’d like to caution against bringing a Snapshot vote for making additions to the allowlist before the relevant contracts have been open sourced and deployed - @TomFrench
Totally agree. To address this, the contract proposed to be whitelisted should be deployed and posted here before the snapshot proposal takes place. In addition, once the vote has been concluded, all solidity files relevant to the Aura protocol will be open sourced and posted on both codearena and immunefi for a week before they are deployed.
If the smart contracts are not yet ready and the team needs funding to get them across the finish line, I would support some arrangement that provides the team with those funds - @markus
The contracts are ready. As stated in Makis post, this $$$ would be used to reimburse the Aura core contributors for significant out of pocket expenses made booking audits. This cost would cover the 2 audits (1 finished, 1 upcoming) and allow $$$ for an initial bug bounty(s).
This is the era of Balancer battle. LFG - @totojack
LFG 