FeedProjects
Developers
Settings
🎉 A new chapter begins: Boardroom has joined Agora
Learn more
protocol logo
Explore / Projects
Threshold Network

Insights

Proposals

Discussions

Members

Information

Reports

Create Proposal

Threshold Network

InsightsProposalsDiscussionsMembersInformationReports
Proposal
Back to Proposals
closedEnded 2 years ago · Snapshot (Offchain)

TIP-064: Sunsetting explicit tBTC coverage pool contracts

By 0x8FBC...5c9A71

Threshold’s coverage pool contracts are designed to provide an insurance backstop against potential losses in the Bitcoin collateral backing tBTC. However, it’s clear that T-only coverage pools are a sub-optimal solution given the inherent relationship between tBTC and T. In case of a BTC collateral loss event, it’s likely that T would experience a significant price impact, reducing it’s effectiveness as an insurance backstop.

Far better are coverage pools with exogenous assets that are not correlated with tBTC (i.e. ETH, ETH LSTs, BTC).

However, naively deploying coverage pools with exogenous assets is unlikely to be the best approach. Since coverage pool liquidations are not automated but rather require the intervention of a risk manager (currently the Treasury Guild), it’s unnecessary to deposit those assets into a coverage pool contract. Instead, they can be more deployed into various DeFi strategies to earn yield for the DAO.

With this in mind, I propose sunsetting the explicit coverage pool contracts in favor of moving to an “implicit coverage pool” model where tBTC is backed by the full faith and credit of Threshold DAO (that is, by its treasury assets, which currently include T, ETH, wBTC, tBTC, stablecoins, CVX, veCRV, and associated LP tokens, etc.

These assets are held primarily in three locations:

  • GovernorBravo timelock controller
  • Council multisig
  • Treasury Guild multisig

In the event of a collateral loss event, these assets can be used to cover the loss by the risk manager in an orderly manner.

Continue Reading
Connect Wallet to Add Note
0
Votes 8
VoterCast PowerVote & Rationale
0x593c...F15bB5
291.207M

Approve

0x4f1e...B7aA74
207.443M

Approve

0xcE37...6e22Af
125.53M

Approve

John Packel
125.53M

Approve

0xA05B...353337
36.047M

Approve

SHOW MORE
VOTE POWER
0
Connect Wallet
Proposal Status
  • Tue November 21 2023, 05:17 pmVoting Period Starts
  • Sun November 26 2023, 05:16 pmEnd Voting Period
Current Results

1-Approve

786.635M

99.79%

2-Disapprove

1.621M

0.21%
DocumentationBrandingContact Us