# Why DAMAGE Execution Credits?

Explain the documented role of DAMAGE alongside Bitcoin and Lightning without assuming governance or liquidity guarantees.

Canonical HTML: <https://damagebdd.com/articles/whydamagetoken.html>



<a id="the-role-in-the-implemented-accounting-path"></a>

## The role in the implemented accounting path

DAMAGE is the utility token used to meter and settle execution work in the
documented DamageBDD/Aeternity integration. Feature and report identities
associate that spend with the verification job. Read [tokenomics](../tokenomics.md)
for units, supply policy and contract capabilities.

Lightning can pay for a credit top-up or carry separately agreed BTC
compensation. This is an architectural choice in the documented stack;
Lightning-based software can also implement metering and access control.
There is no claim that a separate token is the only possible design.


<a id="what-follows-from-that-choice"></a>

## What follows from that choice

A deployment using this accounting path must operate its Aeternity connection,
protect keys, confirm transfers and reconcile execution charges. A top-up
listener, a token spend and a contractor payout have different state changes.
The [payment reference](../payments.md) keeps those boundaries explicit.

Token ownership alone does not establish a voting mechanism, immediate Bitcoin
rewards, a buyback obligation or guaranteed liquidity. The stated supply
allocation is policy; the described contract retains owner mint authority.


<a id="evaluate-the-cost-of-the-complete-workflow"></a>

## Evaluate the cost of the complete workflow

Choose a small workload, obtain the estimate and quote, and retain the
execution and payment records. Compare operational cost and failure handling,
including storage and chain dependencies. See [pricing](../pricing.md) and
[the paid-job evaluation](lightning_api_economics.md).