Skip to main content

Cookie Jar Allocations

Implemented (activation pending indexing)

Overview​

Cookie Jar support is implemented across contracts, shared hooks, and admin Hub components. Arbitrum and Sepolia artifacts have non-zero Cookie Jar module addresses; Celo does not. The remaining readiness gap is dedicated indexer coverage for Cookie Jar module events and per-garden configuration.

Current surfaces​

  • CookieJar.sol owns the contract-side module boundary.
  • Shared hooks cover accessible jars, garden jars, user jars, deposits, withdrawals, and admin operations.
  • Admin Hub components expose deposit, withdraw, manage, and payout panels.
  • Tests exist for the shared hooks and admin modal/payout surfaces.

Builder notes​

  • Gate UI claims on non-zero module addresses, garden eligibility, and chain-specific indexer coverage.
  • Keep deposit/withdraw behavior routed through shared hooks rather than route-local contract calls.
  • Align user-facing status with the community Cookie Jar guide when activation state changes.

Next page

Next best action

Check deployment status before treating Cookie Jar events or payouts as fully active on a chain.

Deployment status