Executed

Claim tBTC from Bridge Fees (Routine Execution) ## tl;dr Claim ~1.61776434 tBTC (161,776,434 sats) from accumulated tBTC Bridge fees and transfer it to the Threshold Committee treasury multisig. ## Background Threshold DAO accrues protocol fees from tBTC Bridge activity as a Bank balance credited to the Governor timelock. Depending on active DAO-approved fee parameters, Bridge fees can relate to mint/deposit and redemption flows. Periodic claims convert the timelock's Bank balance into tBTC via TBTCVault and transfer it to the Threshold Committee treasury multisig for DAO-directed treasury operations. This proposal follows the same operational pattern as the latest executed routine fee claim, Claim tBTC from Bridge Redemption Fees (Routine Execution), which executed at block `24580626` and claimed `190,688,808` sats (~1.90688808 tBTC). This execution uses the current accrued fee amount. ## Proposal Execute the standard 3-step fee claim: 1. Increase the timelock's Bank balance allowance for TBTCVault 2. Mint the corresponding tBTC from TBTCVault 3. Transfer the minted tBTC to the Threshold Committee treasury multisig ## Parameters * Amount: `161,776,434` sats (~1.61776434 tBTC) * Recipient: `0x71E47a4429d35827E0312Aa13162197C23287546` * Balance source: `Bank.balanceOf(Governor timelock)` checked at Ethereum block `25210546` ## Notes * No new permissions or contracts. * Same execution pattern as TIP-107; this is a maintenance sweep of accumulated tBTC Bridge fees. * Given fee claim is a recurring process the Committee plans to execute every few months (more often as substantial fees accrue faster), we will queue the proposal same day as this Forum post, and voting will begin after ~13,000 blocks (approximately 2 days)


Proposal ID

229388...3452

Proposed

Jun 1st, 2026

Result details
Final Votes

Quorum

364.37M of 150M

Majority support

Yes

For

364.37M

Against

0

Abstain

0

Actions

Type

Address

Details

Custom

0x65Fb...9Fc6

increaseBalanceAllowance(..)

Custom

Account

0x65Fb...9Fc6

Method

increaseBalanceAllowance(..)

Custom

0x9C07...E3CD

mint(..)

Custom

Account

0x9C07...E3CD

Method

mint(..)

Custom

0x1808...3a88

transfer(..)

Custom

Account

0x1808...3a88

Method

transfer(..)

Proposal

Claim tBTC from Bridge Fees (Routine Execution) ## tl;dr Claim ~1.61776434 tBTC (161,776,434 sats) from accumulated tBTC Bridge fees and transfer it to the Threshold Committee treasury multisig. ## Background Threshold DAO accrues protocol fees from tBTC Bridge activity as a Bank balance credited to the Governor timelock. Depending on active DAO-approved fee parameters, Bridge fees can relate to mint/deposit and redemption flows. Periodic claims convert the timelock's Bank balance into tBTC via TBTCVault and transfer it to the Threshold Committee treasury multisig for DAO-directed treasury operations. This proposal follows the same operational pattern as the latest executed routine fee claim, Claim tBTC from Bridge Redemption Fees (Routine Execution), which executed at block 24580626 and claimed 190,688,808 sats (~1.90688808 tBTC). This execution uses the current accrued fee amount. ## Proposal Execute the standard 3-step fee claim: 1. Increase the timelock's Bank balance allowance for TBTCVault 2. Mint the corresponding tBTC from TBTCVault 3. Transfer the minted tBTC to the Threshold Committee treasury multisig ## Parameters * Amount: 161,776,434 sats (~1.61776434 tBTC) * Recipient: 0x71E47a4429d35827E0312Aa13162197C23287546 * Balance source: Bank.balanceOf(Governor timelock) checked at Ethereum block 25210546 ## Notes * No new permissions or contracts. * Same execution pattern as TIP-107; this is a maintenance sweep of accumulated tBTC Bridge fees. * Given fee claim is a recurring process the Committee plans to execute every few months (more often as substantial fees accrue faster), we will queue the proposal same day as this Forum post, and voting will begin after ~13,000 blocks (approximately 2 days)

Final Votes

Quorum

364.37M of 150M

Majority support

Yes

For

364.37M

Against

0

Abstain

0

Final Votes
Status

Mon Jun 1, 09:07 am

Published onchain

Wed Jun 3, 05:36 am

Voting period started

Wed Jun 10, 05:00 am

Voting period ended

Wed Jun 10, 08:53 am

Proposal queued

Mon Jun 15, 09:47 pm

Proposal executed