Summary
In recent weeks the DAO has voted to kill stale or inactive gauges in order to clean out the system for active participants to be at the forefront and streamline UX. BIP-515 encompassed this initiative and while Threshold’s 50tBTC/50WETH pool was on this list, they wish to return to be an active participant by providing voting incentives to the ecosystem for their liquidity pool(s). Namely the 50tBTC/50WETH gauge which was activated in BIP-467. All information pertinent typical gauge proposals can be referenced in BIP-467. This proposal is meant to reactivate the gauge for this pool.
tBTC/WETH Pool
Link to Pool: 0x52e281318Fed4eFFfb8E46c0847a8f9B71a461A8
Base Gauge: 0xFA61fB6218378b9f01CA4B2b662B5c4d12915Db9
Mainnet Gauge: 0xF6FA773b5E54F4BD20E09d806AB483d58dD55dcb
References/Useful links:
Link to:
- Website: https://threshold.network
- Documentation: https://docs.threshold.network/
- Github Page: GitHub - keep-network/tbtc-v2: Trustlessly tokenized Bitcoin on Ethereum, version 2
- Forum: https://forum.threshold.network/
- Discord: Threshold Network ✜
- Twitter: https://twitter.com/tBTC_project
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.
Specification:
#1
The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will call grantRole on the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 with the following arguments:
role: 0x076e9815202aa39577192023cfa569d6504b003183b2bc13cd0046523dfa23ea
account: 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f
The role can be verified here . This will give the DAO Multisig the ability to call unkillGauge on a pool’s gauge.
#2
The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptorEntrypoint at 0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA and call performAction using 0xd34fb267 for the data(bytes) argument and 0xf6fa773b5e54f4bd20e09d806ab483d58dd55dcb for the target(address) argument.
#3
The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will call revokeRole on the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 with the following arguments:
role: 0x076e9815202aa39577192023cfa569d6504b003183b2bc13cd0046523dfa23ea
account: 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f