bitcoinafterlife/bal-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Upload files to "docs/user-guide"
All checks were successful
Build and deploy docs / deploy (push) Successful in 4s
Details

Browse Source 
check-alive info correct
This commit is contained in:
bitcoinafterlife
2026-10-05 16:42:32 +00:00
parent db2b672fc9
commit 8de453c0e6
1 changed files with 37 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/user-guide/check-alive.md
View File

@@ -7,28 +7,28 @@
## What it does ## What it does
Check Alive is a **warning threshold placed before your delivery date**. While the threshold is still in the future, nothing special happens: ordinary changes just refresh the will, anticipated by one day. Once the threshold has passed, the plugin tells you that the Check Alive threshold has passed and that you have to **invalidate your old will**, so that the delivery date can be pushed out — because you are evidently still alive. Check Alive is a **date you set, always earlier than your delivery date**. While that date is still in the future, nothing special happens: ordinary changes just refresh the will, anticipated by one day. Once the date has passed, the plugin tells you that the *Check Alive threshold has passed* and that you have to **invalidate your old will**, so that a new one, with a later delivery date, can replace it — because you are evidently still alive.
The check runs when you **close** the wallet, not when you open it.
![Check Alive parameter](../img/settings-check-alive.png){ .screenshot } ![Check Alive parameter](../img/settings-check-alive.png){ .screenshot }
*The threshold can be expressed as a relative period or an absolute date.* *The Check Alive can be a date, or a distance from today.*
In the **Raw** field you can also type a distance from today: `30d` is 30 days from today, `1y` is one year from today. Only days (`d`) and years (`y`) are accepted. By default the Check Alive is set 30 days from today and the delivery date one year from today.
## Example ## Example
You set a delivery date **2 years** out, with Check Alive at **6 months**. The threshold is therefore the delivery date minus 6 months: month 18. You build your will on **1 January 2027** with the delivery date on **1 January 2029**, and set Check Alive to **1 July 2027**.
| What you do | What happens | | What you do | What happens |
|---|---| |---|---|
| You close Electrum at month 3, 9 or 15 | Nothing special — the threshold is still ahead. If something changed, the will is refreshed and anticipated by one day | | You use Electrum before 1 July 2027 | Nothing special — the Check Alive date is still ahead. If something changed, the will is refreshed and anticipated by one day |
| You close Electrum at month 19 | The threshold has passed: the plugin asks you to **invalidate your old will** and sign a new one with a later date | | The plugin checks your will after 1 July 2027 | The date has passed: the plugin asks you to **invalidate your old will** and sign a new one with a later date |
| You stop using Electrum altogether | Nothing postpones the will. On the delivery date, the Will-Executors broadcast it | | You stop using Electrum altogether | Nothing postpones the will. On the delivery date, the Will-Executors broadcast it |
If you accept the prompt when it comes, the will is pushed out and never executed. If you stop, the last date stands. If you accept the prompt when it comes, the will is pushed out and never executed. If you stop, the last date stands.
## Calendar reminders ## Calendar reminders
In advanced mode the plugin can export **`.ics` calendar reminders** spread across the Check Alive window (3 by default). The last one falls the day before the delivery date, so you are reminded before it is too late. In advanced mode the plugin can export **`.ics` calendar reminders**, spread between the Check Alive date and the delivery date: 3 by default, up to 5. The last one falls the day before the delivery date, so you are reminded before it is too late.
!!! warning "A date in the past does not switch it off" !!! warning "A date in the past does not switch it off"
In advanced mode, a Check Alive **date in the past** counts as a threshold that has already passed: the plugin asks you to invalidate your will straight away. To test the plugin with a delivery time only a few hours away, use **basic mode** instead: there Check Alive is hidden and inactive, and never forces a postponement. In advanced mode, a Check Alive **date in the past** counts as a threshold that has already passed: the plugin asks you to invalidate your will straight away. To test the plugin with a delivery time only a few hours away, use **basic mode** instead: there Check Alive is hidden and inactive, and never forces a postponement.