Create operating fund for timed vault contracts

[whoabuddy]

After exploring the design of the timed vault and in consideration of:

• Verify default and range limits for timed-vault contracts #55
• Gate core proposals by unique action proposal voters #54
• Gate core proposals by executed action proposals #52
• Increase core proposal start delay #39 (comment)
• Add operations fund to locked supply calculation #49

If we freeze core proposals for at least a year then we need to make sure action contracts have strong actions.

Recap on the timed vault:

• it is empty and inactive when deployed
• the DAO configures it through an action proposal that:
  • sets the accountHolder → address that can withdraw funds
  • sets the withdrawalAmount → amount that can be withdrawn
  • sets the withdrawalPeriod → how often amount can be withdrawn (in BTC blocks)

The original thought was to allocate a small % of the total supply to the timed vault, so that DAOs can operate with it to start and eventually core proposals open up more options.

With the longer delay, we asked why not deploy multiple timed vaults per DAO?

The catch there is we need a way to fund them and we don't want to fund them before they are used.

In comes the new operating fund

• 75% total supply → Main Treasury
• 5% 2% total supply → New Operating Fund (updated 2025/04/22)

Then we modify the timed vault so it can withdraw up to 1% one time when it's first configured.

Why It’s Smarter

• No pre-funded vaults — reduces attack surface
• Operating fund = one pot — easier to audit, simpler logic

Optional Enhancements

• Add isWithdrawn flag per vault to prevent multiple taps
• Track total withdrawn from operating fund for upper-bound audit
• Allow replenishment by proposal if DAO votes for it

[biwasxyz]

This repository has been superseded by agent-contracts. If this issue is still relevant, please re-open it there. This repo will be archived soon.