A named pool of funds
The design identifies the treasury as its own object, making it possible to distinguish organizational funds from an individual signer’s balance.
The treasury protocol design
A shared balance deserves shared rules.
Sigil’s treasury design connects a pooled balance with withdrawal permissions and explicit revenue-distribution policies.
Programmable TreasuriesIllustrated study
Agreement / evidence / terms
Settlement remains subject to terms and verification.
01 / Built for a purpose
Describe how the money should move.
Organizations, grant programs, and contributor pools need more than a shared address. The treasury design gives a pool of funds an access policy and a distribution policy so its purpose can be expressed directly.
Withdrawal authority
An access policy describes which actors should be allowed to move funds and under what conditions.
Distribution instructions
A revenue policy describes intended recipients and shares. It is a separate concept from permission to initiate a withdrawal.
Identity-aware recipients
The wider Sigil identity model can provide the context for recipient checks. A complete integration must connect those checks to an activated settlement path.
The details matterGood questions.
Good questions.
Clear answers.
Can I create one through public transactions now?
No. The direct treasury lifecycle is gated in the current release. This page describes the intended primitive, not an available custody service.
What can I use for a current application?
Evaluate the supported transfer, escrow, and contract operations for the specific workflow. A reference multisig contract is a different capability from the planned native treasury lifecycle.
Keep exploringOne capability.