TYPE 0x0102 · TIMELOCK FAMILY

CSV_TIME

Relative timelock in seconds (BIP 68 time-based). Uses the type flag bit in BIP 68 sequence to specify 512-second granularity.

Timelock Invertible

Ladder Diagram

Fields

Field	Data Type	Size	Side	Description
sequence_value	NUMERIC	1-4 B	Conditions	BIP 68 sequence value with time flag (512-second units)

No witness fields required — evaluation uses the input sequence number and median-time-past from the transaction context.

Wire Format Breakdown

0x0102 0 1 NUMERIC · 3B Conditions = 4 + 5 = 9 bytes

0x0102 0 0 Witness = 4 bytes (empty block)

Total 15 bytes

Evaluation Logic

1.Read sequence_value from NUMERIC field (time-based BIP 68 encoding). Negative → ERROR

2.If SEQUENCE_LOCKTIME_DISABLE_FLAG is set → SATISFIED (disabled)

3.CheckSequence(value) — value interpreted as 512-second units. If fails → UNSATISFIED

4.Pass → SATISFIED

Return Values

Condition	Result
Missing NUMERIC field	ERROR
Negative sequence value	ERROR
SEQUENCE_LOCKTIME_DISABLE_FLAG set	SATISFIED
Sufficient time elapsed (CheckSequence passes)	SATISFIED
Insufficient time elapsed	UNSATISFIED

JSON Wire Format

Conditions (relative locktime of ~24 hours = 168 × 512s)

{
  "type": "CSV_TIME",
  "inverted": false,
  "fields": [
    { "type": "NUMERIC", "value": 4194472 }
  ]
}

The value 4194472 encodes 168 units of 512 seconds (~24 hours) with the BIP 68 time flag (bit 22) set. The UTXO cannot be spent until this duration has elapsed from its creation.

Use Cases

Time-Based Vault Delays

Vault cooling periods measured in real-world time rather than block count, providing predictable delay windows regardless of mining variance or hash rate fluctuations.

Calendar-Aware Contracts

Escrow and payment contracts where the refund path activates after a specific duration (e.g., 48 hours) rather than a block count, giving both parties a clock-based deadline.

← CSV CLTV →