Skip to main content

Cookie Jars

Current state​

Admin + hooks

Creating, funding, and managing cookie jars works today from the admin dashboard, backed by shared hooks.

Deployment status

Cookie jar contracts are deployed on Arbitrum, and jar creation is indexed. Garden jars are provisioned automatically when a garden is minted, so a garden with no jar was likely minted before cookie jar support; campaign jars are created through the deployer and ops flow, not a per-operator action. Note: per-jar deposit and withdrawal activity is not indexed, so it does not show up in reports.

Target operator flow​

  1. 1

    Create jar

    Define interval, max withdrawal, and eligible members.

  2. 2

    Fund jar

    Deposit supported asset from endowment.

  3. 3

    Operate

    Pause/unpause or update limits as governance decides.

  4. 4

    Audit

    Review withdraw events and policy adherence.

Choose the right cookie-jar policy

If: You want small recurring payouts with low governance overhead

Do: Set short intervals with conservative withdrawal caps.

Then: Review usage monthly and tune limits.

If: You need strict control over endowment outflows

Do: Start with paused jar + explicit operator approvals.

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

If: You need larger strategic allocations

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

Then: Route to Vaults/Endowments or Signal Pools based on governance intent.

Next page

Next best action

Keep momentum by moving to the next high-value step in this journey.

Managing Governance