THE DECREE FIELD GUIDE
Markets, with
a mandate.
A practical introduction to the infrastructure that gives market revenue a direction.
01The idea
Pons launches markets. DECREE is designed to give those markets an economic policy: a set of rules for allocating future creator fees across a market’s priorities.
A project keeps its token and existing liquidity. Its fee flow can be directed to an isolated vault, where a policy determines how capital is allocated. The allocation is explicit; the resulting execution can be inspected.
The site includes interactive product previews. Demo allocations, projections, and example executions are illustrations, not reported financial results.
02Sovereign vaults
Each market has its own vault. Balances, policy, accounting, and receipts stay separate from other projects. Sharing execution infrastructure does not mean sharing a pool of capital.
Fee collection must be connected to the appropriate source. A vault alone does not redirect an existing fee stream; activation and fee routing are separate steps.
03Capital routes
The product vision includes five policy routes. Availability depends on the deployed vault and adapters. The current interface distinguishes existing routes from capabilities still planned.
Treasury
Allocate a share to the treasury destination configured by the project.
Buybacks
Use the configured swap route to acquire the project token, subject to execution limits.
Buy + Burn
Acquire project tokens and route them through the burn path. Verify the outcome in the execution receipt.
Permanent Liquidity
Intended to deepen market liquidity. The current activation interface keeps this allocation at zero.
Stock Token Reserves
Part of the product vision. The existing interface exposes a same-asset reserve route; it does not establish a working stock-token acquisition integration.
Allocation weights must total 100%. The marketing configurator can illustrate the complete five-route model, while the connected application must respect the capabilities of its actual deployment.
04Execution rules
A policy describes where capital should go. Execution constraints determine when an action may happen. Eligibility is not a promise of execution at a particular time or price.
- Minimum tranche
- The minimum amount required before the configured action becomes eligible.
- Slippage limit
- A bound on the acceptable price difference during a swap. Basis points express the limit: 100 bps equals 1%.
- Cooldown
- A minimum interval between eligible actions, as configured for the vault.
- Adapter checks
- Quote freshness, market depth, and deadlines depend on the connected adapter. Preview indicators are not evidence that those checks are live.
When conditions are not met, an action may remain queued or be skipped. Those states are different from a confirmed outcome.
05Public proof
Proof begins with an emitted onchain event. A receipt identifies the vault, action, amounts, and transaction. Queued events are shown separately because intent is not settlement.
- Confirmed
- An execution receipt has been recorded. Inspect its transaction to verify the underlying event.
- Queued / skipped
- The action has not completed. Read the reason rather than counting it as capital processed.
- Demo / unavailable
- A preview or missing source. Neither state establishes a transaction or financial outcome.
06Getting started
Start in the simulator. Choose a fee amount and allocation, then compare how different policies distribute that amount. The result is an arithmetic illustration; it does not account for market returns or guarantee execution.
When a deployment is available, activation connects a project token, fee asset, fee source, swap adapter, and policy. Management belongs to the project owner. Review every destination and execution constraint before approving any transaction.
Current integration status: the repository supports a local deployment flow with mock fee and swap adapters. A production Pons fee adapter and market swap integration require separate validation. Ecosystem prices or explorer activity do not imply an active DECREE integration.