Skip to content

A treasury operations layer for Stellar-based organizations

Budget categories, spend caps, and approval thresholds enforced on-chain, instead of a bare multisig.

Approval threshold

3 of 5 approvals

A release executes only once the category's required approvals are collected on-chain.

Organizations already run treasuries worth hundreds of millions — sometimes billions — on-chain.

$4.8B

Uniswap

$200M+

Optimism

$40M–$200M

Arbitrum

Publicly reported DAO treasuries · illustrative

Today that money is tracked with after-the-fact reporting — not policy enforced at the moment funds move.

How Charter works

From deploying a treasury to releasing funds, every step is a contract call authorized by your own wallet.

  1. Deploy a treasury

    Spin up a policy-governed treasury through the Charter factory contract — your wallet keeps custody the whole time.

  2. Set budget categories

    Divide the treasury into budget categories, each with its own spend limit and approval threshold.

  3. Deposit funds

    Move tokens into the treasury contract. Balances live on-chain, not in a spreadsheet.

  4. Request a spend

    A member raises a request to move funds out of a category. It stays pending until it clears policy.

  1. Collect approvals

    Approvers sign off until the category's approval threshold is met — checked by the contract, not by convention.

  2. Release funds

    With the threshold met, the transfer executes on-chain. Below it, nothing moves.

Approval threshold

5 of 5 approvals

Threshold met — the release executes on-chain.

Runs on Stellar testnet. Unaudited. Experimental.

See it on-chain

The factory every treasury is deployed through is public on Stellar testnet — verify the deployment in a block explorer, not a screenshot.

Factory contract

CCUQBFFRGR4RUWHKLWSRWKBL3WORHNTHFLTKMHTNUZL4T5733ODN5WD4 (view on Stellar Expert, opens in a new tab)

Open it on Stellar Expert to inspect every treasury this factory has deployed.

Example policy state

5 of 5 approvals

Illustrative — real approval thresholds are set per category on the contract itself.

Built in the open

Charter is developed in the open, maintained by @fadesany. The application layer and the Soroban contracts live in separate repos.