Skip to main content

Managing Payouts

Overview​

Operators manage the financial flows within their garden — from vault deposits and harvest routing to direct gardener payouts through cookie jars. This page covers both the primary vault system and the cookie jar mechanism for recurring, low-overhead distributions.

How It Works​

Vault-Based Payouts​

Garden vaults hold deposited assets in impact-vault positions powered by Octant. Depositor claim value stays flat by design, so operators rely on harvest and split flows plus withdrawals to move funds into payout paths:

  1. 1

    Receive deposits

    Funders deposit supported assets into the garden vault. Track deposits through the vault dashboard.

  2. 2

    Monitor harvest readiness

    Strategies may generate yield over time. Review routed yield, harvest cadence, and current balances rather than depositor share appreciation.

  3. 3

    Distribute funds

    Withdraw principal or distribute harvested yield to fund garden operations, gardener compensation, or community initiatives.

  4. 4

    Report usage

    Maintain transparency by documenting how vault funds support garden operations.

Cookie jars provide a lightweight mechanism for small, recurring payouts to garden members without full governance overhead.

Cookie Jar system

Creation, funding, pause, and withdraw flows are live when the garden has an active cookie jar configured on the selected chain.

  1. 1

    Create jar

    Define interval, max withdrawal amount, and eligible members.

  2. 2

    Fund jar

    Deposit supported assets from the garden endowment.

  3. 3

    Operate

    Pause/unpause or update limits as governance decides.

  4. 4

    Audit

    Review withdrawal events and policy adherence.

Choose the right payout approach

If: You want small recurring payouts with low governance overhead

Do: Set up a cookie jar with short intervals and conservative withdrawal caps.

Then: Review usage monthly and tune limits based on actual withdrawal patterns.

If: You need strict control over endowment outflows

Do: Start with a paused cookie jar + explicit operator approvals for each payout.

Then: Unpause only after policy and monitoring checks are complete.

If: You need larger strategic allocations

Do: Use vault withdrawals or conviction voting flows instead of cookie jars.

Then: Route to the vault dashboard or signal pools based on governance intent.

Best Practices​

  • Set clear payout policies before activating cookie jars — document who can withdraw, how much, and how often
  • Monitor vault health regularly: check principal balances, harvest readiness, routed impact yield, and withdrawal liquidity
  • Use cookie jars for operational expenses (gas sponsorship, small incentives) and vaults for strategic allocations
  • Explain routed-yield semantics in contributor communications so nobody expects depositor share appreciation
  • Maintain transparent records of all payouts for community accountability
  • Review withdrawal patterns monthly to detect unusual activity early

What's Next​

Next page

Next best action

With payouts configured, set up governance mechanisms for community resource allocation.

Managing Governance