TYPE 0x0802 · GOVERNANCE FAMILY
WEIGHT_LIMIT
Maximum transaction weight constraint. Prevents this UTXO from being spent in transactions that exceed a specified weight in weight units (WU). No Tapscript equivalent.
Governance InvertibleLadder Diagram
Fields
| Field | Data Type | Size | Side | Description |
|---|---|---|---|---|
| max_weight | NUMERIC | 1-4 B | Conditions | Maximum allowed transaction weight in weight units. Must be > 0. Standard max is 400,000 WU. |
Wire Format Breakdown
0x0802
0
1
NUMERIC · 4B
Conditions = 9 bytes
0x0802
0
0
Witness = 4 bytes
Total
13 bytes
Evaluation Logic
1.Locate the conditions NUMERIC field. Missing → ERROR. ReadNumeric as
max_weight; undecodable or ≤ 0 → ERROR2.Require
ctx.tx_weight > 0; missing or ≤ 0 → ERROR (fail-closed; the evaluator does not compute weight from the tx — the caller pre-computes it).3.If
ctx.tx_weight ≤ max_weight → SATISFIED; else → UNSATISFIEDJSON Wire Format
{
"type": "WEIGHT_LIMIT",
"inverted": false,
"fields": [
{ "type": "NUMERIC", "value": 100000 }
]
}Use Cases
Anti-Batching Constraint
Force this UTXO to be spent in small, focused transactions. Prevents inclusion in large batch operations that could obscure the spend among hundreds of outputs.
Fee Predictability
By capping transaction weight, the maximum fee for spending this UTXO becomes bounded. Combined with RELATIVE_VALUE, this creates tight fee guarantees.