Skip to content

Commit a879627

Browse files
committed
Explain unintentional initiation of rrecovery-plan.
1 parent 5538fb4 commit a879627

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

bip-timelock-recovery-storage-format.mediawiki

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,9 +65,17 @@ pre-signed transactions:
6565

6666
A ''Timelock-Recovery plan'' consists of two transactions:
6767

68-
* ''Alert Transaction'': A mostly-consolidation transaction that keeps most funds in the original wallet, except for a fee and a small fixed amount that goes to ''anchor-addresses'' - addresses which can be used to accelerate the ''Alert Transaction'' via CPFP. The majority of funds should remain on the original wallet, in a new previously-unused address which we call the ''alert-address''. We use the term ''Alert Transaction'' because it should alert the user that the recovery-plan has been triggered, giving them a limited time to prevent the majority of the funds from moving to the secondary wallets.
68+
* ''Alert Transaction'': A mostly-consolidation transaction that keeps most funds in the original wallet, except for a fee and a small fixed amount that goes to ''anchor-addresses'' - addresses which can be used to accelerate the ''Alert Transaction'' via CPFP. The majority of funds should remain on the original wallet, in a new previously-unused address which we call the ''alert-address''. We use the term ''Alert Transaction'' because monitoring the blockchain and looking for it should alert the user that the recovery-plan has been initiated (intentionally, unintentionally or maliciously).
6969
* ''Recovery Transaction'': The transaction that moves the funds from the alert-address UTXO from the ''Alert Transaction'' to one or more addresses of secondary wallets (each may receive a different amount). This transaction should have a special <code>nSequence</code> relative-locktime according to the size of cancellation-period requested by the user, following the rules of [[bip-0068.mediawiki|BIP-68]].
7070
71+
With a reliable tool to monitor the blockchain and look for the ''Alert Transaction''
72+
and/or ''Alert Address'', the user can safely save online backups of the recovery-plan's
73+
JSON file.
74+
If the presigned transactions have leaked and the ''Alert Transaction'' has been broadcast
75+
unintentionally, the user has the cancellation-period (which is expected to be at least a
76+
few days) to stop the majority of funds from moving, by sending them to a new address, thus
77+
invalidating the ''Recovery Transaction''.
78+
7179
It is important that the ''Alert Transaction'' will be non-malleable (e.g. by using
7280
[[bip-0140.mediawiki|BIP-140]]).
7381
If a malleable ''Alert Transaction'' is used, a malicious miner could replace the

0 commit comments

Comments
 (0)