30 lines
1.6 KiB
Markdown
Executable File
30 lines
1.6 KiB
Markdown
Executable File
# Backup transaction
|
|
|
|
Accessible from `Tools → Plugins` (BAL parameters).
|
|
|
|
**Backup Transaction** (default: *Disabled*) lets you keep the inheritance transaction (locktime TX) even **without** relying on the automation of the will-executor online servers.
|
|
|
|
|
|
|
|
When enabled, you get an **offline backup of the signed legacy transaction** — useful in the (highly unrealistic) event that all will-executor servers are destroyed.
|
|
|
|
The backup can be saved locally, on a USB stick, or wherever you prefer — and delivered through a notary, trusted persons, or even directly to the heir. In the latter case, note that the heir will learn they are receiving an inheritance on a specific date and of a specific amount, which could be imprudent.
|
|
|
|
Once delivered to the heir, the backup transaction can be sent to the nodes via Electrum (on a date later than the delivery time) to receive the funds.
|
|
|
|
## Risks of relying only on the backup
|
|
|
|
1. The transaction is **invalidated** if you accidentally spend even one satoshi from the wallets whose UTXOs were pre-signed in the legacy transaction.
|
|
2. Delivering the signed transaction reveals the inheritance and its value to the heir.
|
|
3. Every step must be handled by hand, with risk of errors.
|
|
|
|
## Saving the backup
|
|
|
|
With Backup Transactions enabled, the transaction appears in the **WILL** tab with status `NONE` in the Will-Executor column.
|
|
|
|
|
|
|
|
Right-click it, select **Details**, and save the transaction to your preferred medium (USB drive, cloud, NAS, etc.).
|
|
|
|
|