Fund the Program Vault and rehearse the first Hack Juno epoch #37

Goal

Make the deployed gauge economically operable using an approved non-agent funding source, then verify one bounded epoch end to end.

Depends on

• Add gauge epoch discovery and weighted preference voting #36 for user-facing dogfood; funding-package preparation may proceed independently.

Current state

The Program Vault and gauge are deployed but unfunded. The prepared target is 1,000 JUNO. Agent funds must not be used.

Scope

• Validate the exact governance/community-pool funding message, recipient, amount, deposit, fees, proposer authority, and current chain parameters.
• Obtain separate approvals for proposal submission, deposit source, signing, broadcast, and any follow-up transaction.
• Confirm Vault balance and gauge budget policy after execution.
• Open a bounded epoch, place/revise sample preferences, execute at close, and verify allocations/bank sends or retained-value outcome.
• Record transaction hashes, heights, balances, and canonical contract queries.

Acceptance

• The Vault receives exactly the approved amount from a non-agent source.
• No transaction is signed or broadcast without its explicit gate.
• A full epoch rehearsal confirms snapshot power, option set, turnout math, caps, rounding, execution, and final balances.
• Public docs distinguish deployed, funded, open, executed, and distributable states.

Stop conditions

Stop on changed account sequence, recipient/contract mismatch, fee-cap increase, checksum mismatch, unexpected live state, or failed transaction.