[BIP-297] Enable tBTC/WBTC [Arbitrum]

Summary:

Proposal to add gauge support for 50/50 tBTC/WBTC pool on Arbitrum.

Link to pool: 0x542F16DA0efB162D20bF4358EfA095B70A100f9E
Link to gauge: 0xc4b6cc9A444337b1Cb8cBbDD9de4d983f609C391

References/Useful links:

Link to:
Website
Documentation
Github Page
Communities
Discord
Twitter

Protocol Description:

tBTC is a decentralized wrapped Bitcoin, that is 1:1 backed by mainnet BTC.

Unlike other wrapped Bitcoins, the BTC that backs tBTC is not held by a central intermediary, but is instead held by a decentralized network of nodes using threshold cryptography. tBTC is trust minimised and redeemable for mainnet BTC without a centralized custodian.

tBTC is built with Threshold Network’s decentralized infrastructure, and Ethereum.

Motivation:

This proposal aims to add a veBAL gauge for the Balancer tBTC/WBTC pool on Arbitrum.

Threshold DAO has recently launched a L2 growth campaign with Wormhole, which has enabled a canonical tBTC bridge to Arbitrum.

The DAO has budgeted T token bribes to incentivise this tBTC/WBTC pool, with the goal to attract liquidity to the pool and Balancer. Threshold DAO intends tBTC to become a core component of Balancer BTC liquidity on Arbitrum.

These pools are part of the tBTC launch promotion on Arbitrum which will commence next week and feature Balancer as a liquidity target and collaborator. There is currently another proposal in the forum to enable the tBTC/ETH gauge.

Specifications:

  1. Governance: tBTC operates on Threshold DAO’s decentralized threshold encryption protocol. Threshold DAO is governed by the network’s work token, T. T token holders govern the DAO via proposals raised to the Threshold forum, which can be raised to a vote via Snapshot, as well as the on-chain Governor Bravo module.

  2. Oracles: tBTC does not rely on an oracle price feed.

  3. Audits:
    Least Authority
    Chainsecurity
    Certik
    Immunefi Bug Bounty

  4. Centralization vectors: Threshold Network governance is decentralized, and updates are ratified by the DAO via token holder vote. tBTC contract updates are currently managed by the Council multi-sig, with plans to migrate control to the DAO once cross-chain deployment is complete.

  5. Market History: tBTC is a wrapped BTC token, and is pegged to the price of BTC. Since launch, tBTC’s price has not significantly diverged from that of BTC. tBTC launched in January of 2023, and currently has ~700 BTC to collateralize the ~700 tBTC.

  6. Value: The Arbitrum tBTC/WBTC pool is intended to be a lynchpin of BTC liquidity on Arbitrum.

    Threshold DAO has allocated a portion of its incentives budget to bribe the tBTC/WBTC pool using Paladin. This will incentivise veBAL holders to vote on our gauge to direct protocol emissions and attract TVL as part of the Arbitrum tBTC growth strategy.

    Furthermore, Balancer will feature featuring in the Arbitrum launch promotion that Threshold DAO will commence next week. Lastly, Balancer will benefit by attracting additional BTC liquidity to Arbitrum.

Specification

The Balancer Maxi LM Multisig eth:0xc38c5f97B34E175FFd35407fc91a937300E33860 will interact with the GaugeAdderv3 at 0x5efBb12F01f27F0E020565866effC1dA491E91A4 and call the addArbitrumGauge function with the following argument:

0xc4b6cc9A444337b1Cb8cBbDD9de4d983f609C391 which corresponds to the uncapped gauge for this pool.

1 Like

Wondering why there is no discussion phase for this and the other one BIP-298, as required by the governance procedure, before they got assigned a BIP number for snapshot.

I don’t see any requirement of a discussion phase in those docs or the BIP that they’re based on.

It is advised, yes. Not required. Most BIPs get zero discussion as you know I’m sure.

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