> For the complete documentation index, see [llms.txt](https://docs.ducatprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ducatprotocol.com/trust-assumptions/supply-control.md).

# Supply Control

UNIT uses a Bitcoin Rune, but a generic Rune balance is not the complete Ducat supply model. Ducat's ledger distinguishes **reserve UNIT**, **active UNIT** and burns, and relates active issuance to accepted borrowing actions.

### Reserve and active balances

Reserve UNIT is inventory available for the protocol's issuance flow. An accepted Open or Borrow action activates the borrowed quantity and associates it with vault debt.

Moving reserve Rune units to another address does not automatically make them active UNIT. A wallet or exchange that reads only an ordinary Rune indexer can miss this distinction. A Ducat-aware service must use the protocol's ledger classification.

Active UNIT can move independently of the vault that originally borrowed it. Sending tokens away does not remove that borrower's debt.

### Repayment and liquidation

A repayment reduces vault debt through a linked burn-and-update action. The validator checks the active UNIT burn against the reduction. Reserve UNIT does not qualify as the required active repayment burn.

Repo and Trim transfer debt to the liquidator's vault. They do not reduce the active supply through a burn at takeover. Later repayment is the step that burns active UNIT and clears the assumed obligation.

These are different events:

| Event                            | Debt effect                      | Active UNIT effect                        |
| -------------------------------- | -------------------------------- | ----------------------------------------- |
| Valid Open or Borrow             | Creates or increases vault debt. | Activates the borrowed quantity.          |
| Transfer of existing active UNIT | No change to vault debt.         | Moves the existing active balance.        |
| Repo or Trim                     | Transfers debt between vaults.   | No repayment burn at takeover.            |
| Valid repayment                  | Reduces the repaid debt.         | Burns the active UNIT used for repayment. |

### Rejected actions and observed transactions

A rejected borrowing action must not activate reserve UNIT merely because Rune outputs exist. Conversely, an invalid Ducat action tag does not mean a validator can pretend an already confirmed Bitcoin spend or its Rune allocation never happened.

The ledger tracks actual allocations and eligibility separately from transaction diagnostics. Existing active balances do not become invalid simply because they travel through a transaction with an unrelated rejected protocol action.

Not every economic-policy diagnostic is a rejected action during confirmed replay. See [Validators](https://docs.ducatprotocol.com/how-ducat-works/validators.md) for the difference between strict pre-signing checks and historical indexing.

### Independent verification

Running a validator allows users to reconstruct these classifications against their chosen protocol profile. Using a hosted validator delegates that view to the service.

Neither choice guarantees the market price of UNIT or recovers BTC spent through a valid Bitcoin path. Supply classification and collateral recovery are separate properties.

The published UNIT/USD anchor does not establish an active DUCAT governance asset or vote-counting system. Those should not be included as current supply-validation functions without a separate implemented specification.
