Skip to main content
£0.00 0

Basket

No products in the basket.

ASIC mining knowledge centre

BIP 128 Timelock-Recovery Storage: Backup and Monitoring Guide

BIP 128 guide to Draft timelock-recovery plan storage, presigned transaction pairs, relative delay, checksums, monitoring, cancellation and reorg safety.

BIP 128 Timelock-Recovery Storage Format guide cover

This guide explains BIP 128 Timelock-Recovery Storage Format in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.

TL;DR

  • What it is: BIP 128 is a Draft application-layer specification for exporting timelock-recovery plans between wallets and monitoring or execution services. The plan uses presigned transactions, including a relative-delay stage, so recovery can move towards secondary wallets while leaving a cancellation period.
  • Why it matters: A timelock-recovery file is a living operational plan, not passive backup paperwork. Its value depends on authenticated storage, continuous chain monitoring, viable fee strategy and repeated proof that cancellation works within the intended delay.
  • Current position: BIP 128 is a Draft application-layer specification for exporting timelock-recovery plans between wallets and monitoring or execution services.

BIP 128 Timelock-Recovery Storage Format in simple English

A BIP is a document that proposes or explains a Bitcoin idea, standard or rule. A BIP number does not mean the idea is active. Some BIPs are widely used, while others are drafts or historical proposals.

You do not need to read code to understand the main point. Start with the status, the problem being addressed and the practical effect on ordinary users, wallets, miners or node operators.

Simple example

Think of a mempool as one node’s waiting room for valid transactions that have not yet entered a block. Different nodes can have different waiting rooms, and the contents can change from one second to the next.

Key terms in plain English

BIP:
Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
Node:
A computer running Bitcoin software that checks data and communicates with other peers.

Recovery model

A plan contains presigned transaction stages that eventually direct funds to secondary wallets. A relative nSequence delay in the second stage creates time for the owner to detect and cancel an unintended trigger.

Why two stages

Unlike a single future-nLockTime transaction, the staged construction avoids requiring the owner to refresh solely before a fixed date, while preserving a response window after activation.

Export purpose

The format lets one wallet generate a plan and another application monitor or execute it. Interoperability does not transfer responsibility for custody, availability, fee funding or chain interpretation.

BIP 128 Timelock-Recovery Storage Format technical diagram
Export purpose: the fields, validation boundary and operational evidence that implementations need to agree.

Fee acceleration

The first transaction may need fee acceleration without moving most funds to recovery. Services must model CPFP or other supported mechanisms, dust, package policy and changing relay conditions.

Monitoring and reorgs

Track the trigger transaction, confirmation state, relative timelock and successor transaction across replacements and reorganisations. Persist checkpoints and make actions idempotent.

Storage controls

Treat the JSON and transaction material as sensitive: encrypt at rest and in transit, authenticate origin, validate the specified checksum, maintain offline copies and inventory every service that can access it.

Recovery rehearsal

Test parsing, checksum failure, unavailable inputs, fee spikes, delayed monitoring, replacement, shallow and deep reorgs, cancellation during the response window and restoration from an independent backup. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.

Frequently asked questions

What is BIP 128 Timelock-Recovery Storage?

BIP 128 is a Draft application-layer specification for exporting timelock-recovery plans between wallets and monitoring or execution services. The plan uses presigned transactions, including a relative-delay stage, so recovery can move towards secondary wallets while leaving a cancellation period.

Is BIP 128 Timelock-Recovery Storage active or supported today?

BIP 128 is a Draft application-layer specification for exporting timelock-recovery plans between wallets and monitoring or execution services.

Why does BIP 128 Timelock-Recovery Storage matter?

A timelock-recovery file is a living operational plan, not passive backup paperwork. Its value depends on authenticated storage, continuous chain monitoring, viable fee strategy and repeated proof that cancellation works within the intended delay.

Do beginners need to use the technical details?

No. Most readers only need to understand the idea and its current status. Developers and node operators can use the primary sources when they need the exact technical rules.

Conclusion

A timelock-recovery file is a living operational plan, not passive backup paperwork. Its value depends on authenticated storage, continuous chain monitoring, viable fee strategy and repeated proof that cancellation works within the intended delay.

Primary sources

Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.

On this page

Search More Guides

Continue Reading

Explore more practical guidance on ASIC hardware, profitability, setup, hosting and maintenance.

Need Advice for Your Mining Setup?

Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.
Contact our team
Browse ASIC miners