Cookie Jars

Implemented (activation pending deployment)

Current state

Admin + hooks

Implemented (activation pending deployment)

Creation/admin/deposit/withdraw hooks are implemented and exported in shared package.

Deployment readiness

Implemented (activation pending deployment)

`cookieJarModule` remains zero-address in latest deployment artifacts and indexer config.

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 best action

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

Managing Governance

• Troubleshooting