[BIP-235] Enable TEMPLE/DAI 50/50 Gauge with 10% emissions cap [Ethereum]

PR with payload

SUMMARY:

This proposal aims to add a new veBAL gauge for a new TEMPLE/DAI 50/50 weighted pool on Ethereum.

PROTOCOL DESCRIPTION:

TEMPLE is a Treasury value backed token. We chose Balancer to deploy our AMO-styled price defense contract (RAMOS) which paired TEMPLE token to approximately $9mm USD worth of stables initially held in the Balancer USD (bb-a-USD) liquidity pool. The RAMOS contract protected TEMPLE token price from falling below the Treasury stable value backing each token.

References/Useful links:

Website: templedao.link

Github Page: github.com/TempleDAO/TempleDAO

Communities: discord.gg/templedao / Twitter: @templedao

MOTIVATION:

In February of 2023, Balancer Team uncovered a reentrancy vulnerability for the boosted pools and stopped collecting protocol fees for bb-a-USD. Instead of redeploying a fixed bb-a-USD pool using AAVE v2, Balancer Team chose to push for a new boosted pool (bb-e-USD) that deposited stables into Euler.

At the same time, Temple Protocol was asked by the Balancer Team to switch our token pairing to Euler USD. Wanting to be a good ecosystem partner, we switched TEMPLE to pair against the new bb-e-USD which was subsequently affected in the Euler attack. Since trading was paused in the Euler USD pool, we have been unable to resume TEMPLE trading on Balancer nor reactivate RAMOS.

This proposal aims to add a veBAL gauge for the new TEMPLE/DAI 50/50 weighted pool which will become TEMPLE’s primary LP once Euler restores lost funds to Temple. A new TEMPLE/DAI trading pair would bring significant TEMPLE trading volume to the Balancer platform. In the first two weeks of March before the Euler exploit occurred, the TEMPLE/bb-e-USD LP had generated over $800K in volume. Platform BAL incentives for the new pool would further enhance TEMPLE liquidity to facilitate more transaction volume.

TempleDAO plans to be active participants in Balancer governance as not only are we big fans of the technology, but also share a common vision of reducing price volatility, deep liquidity, and customizable asset exposure.

GOVERNANCE:

TempleDAO current team has been almost entirely sourced from the community contributors. We started with a top-down nomination system for promotion and are currently in the early stages of implementing a Discord-integrated election system for promoting and demoting team members which will eventually lead to more decentralization.

ORACLES:

TempleDAO does not rely on any external oracles. Prior to switching to Balancer, our custom Uni v2 AMM had handled over $300M in transaction volume without any issues. The intrinsic value backing per token against which the token price is indexed is coded into the contract: 0xae8a796bd9437Bd266664e8e9B8428B25A7D2477.

Similarly, after deploying RAMOS to automatically manage the Balancer liquidity, our bot has rebalanced the pool dozens of times to enforce the TEMPLE price floor, which is also coded into the RAMOS contract: 0xa2eac1df5e89ca694c78626dd862d9398dbba6ef.

AUDITS:

TempleDAO contracts have been fully audited by Peckshield. We also have a generous and on-going bug bounty system at hats.finance funded with $400K USD in TEMPLE rewards.

CENTRALIZATION VECTORS:

The TEMPLE token is not upgradeable nor pausable.
The owner has limited minting capabilities and cannot blacklist the contract.
The community contributors behind the Temple protocol have shown the highest integrity and they have never abused their power, nor committed any actions that would harm the community nor DeFi at large.

MARKET HISTORY:

TEMPLE initiated its token presale in October of 2021 and public trading began on its own custom AMM on December 19, 2021. It currently has strategic partnerships with major protocols like Convex, Yearn, Aura, Frax, and Balancer.

VALUE STATEMENT AND CONCLUSION:

The TempleDAO Team has been a major adopter of Balancer technology. Our protocol has generated significant volume on the Balancer platform through TEMPLE swaps as well through our previous LBP events. TempleDAO has also been a significant revenue provider for veBAL and vlAURA holders by incentivizing emissions through Redacted Cartel’s Hidden Hand platform to accelerate and deepen our liquidity pool. Should the 50/50 TEMPLE/DAI pool become whitelisted for BAL rewards, our bribe incentives program would continue to promote trading, bribing, LP farming activity on Balancer, and in particular DAI liquidity paired against TEMPLE.

TEMPLE/DAI 50/50 Weighted Pool Gauge Address:

0xF17F1E67bc384E43b4acf69cc032AD086f15f262

Zapper bundle for TempleDAO Treasury:

https://zapper.xyz/bundle/0x5c8898f8e0f9468d4a677887bc03ee2659321012,0x22c2fe05f55f81bf32310acd9a7c51c4d7b4e443,0x8a5058100e60e8f7c42305eb505b12785bba3bca,0x6021444f1706f15465bee85463bcc7d7cc17fc03,0x4ce17ae9fb4aa0178ec2f8eea3f6167ae511f14c,0xb1BD5762fAf7D6F86f965a3fF324BD81bB746d00,0xE97CB3a6A0fb5DA228976F3F2B8c37B6984e7915

2 Likes

Could you please add the gauge address if it already exists to the specifications? Thanks

Hello here is the relevant information and specifications
Pool address: 0x8Bd4A1E74A27182D23B98c10Fd21D4FbB0eD4BA0
Gauge address: 0xF17F1E67bc384E43b4acf69cc032AD086f15f262

Transaction: The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptor at 0x8F42aDBbA1B16EaAE3BB5754915E0D06059aDd75 and call performAction with the GaugeController at 0xC128468b7Ce63eA702C1f104D55A2566b13D3ABD for the target(address) argument and using 0x3a04f900 followed by the gauge address 0xF17F1E67bc384E43b4acf69cc032AD086f15f262 and the corresponding gauge type for the data(bytes) argument.

data(bytes) : 0x3a04f900000000000000000000000000F17F1E67bc384E43b4acf69cc032AD086f15f2620000000000000000000000000000000000000000000000000000000000000002

3 Likes

Thank you ser. Happy to answer further questions, but if there has been enough public discussion on this matter, I would like to request an official BIP number for this proposal and move to Snapshot.

https://snapshot.org/#/balancer.eth/proposal/0x80f4a0f101ddcfe1b7098f0652a194aa741cc43c0dfccccd714e977cdc8f1150