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

init

Browse Source
This commit is contained in:
steal
2026-07-24 23:32:53 -04:00
commit 968749c10d
24 changed files with 435 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
user-guide/will.md Executable file
View File

@@ -0,0 +1,54 @@
# The WILL tab
The **WILL** tab shows your inheritance transactions and their progress on each will-executor.
![WILL tab](../img/fig_p11_0.png)
## Columns
| Column | Meaning |
|---|---|
| Locktime | The date of the inheritance |
| Txid | Identifier of the Bitcoin transaction |
| Will-Executor | Address of the will-executor |
| Status | Progress of the transaction (see below) |
## Commands
1. **Prepare** — prepares the inheritance and puts it on the list.
2. **Sign** — signs your legacy transaction with your private key (wallet password or hardware key).
3. **Broadcast** — sends the inheritance transaction to the online will-executor servers in your [service list](../will-executor/service-list.md).
4. **Display** — opens the *Will-Details* window with all available data: locktime, creation time, transaction fee (miners), status, heirs, will-executor address, and the will-executor's base fee.
!!! note "Automatic execution on close"
When you close Electrum, the plugin automatically runs **Prepare → Sign → Broadcast** for any step not yet completed, to ensure the inheritance is correctly executed.
## Checking storage on servers
Transactions pushed to will-executor servers are stored there, but are **not publicly accessible** (for privacy). You can verify at any time that your transaction is properly stored: right-click the inheritance transaction in the WILL tab and select **Check**. If it is online on the server, its status becomes `Checked`.
## Transaction statuses
Transactions in the WILL tab are color-coded by status:
| # | Status | Meaning | Color | HEX |
|---|---|---|---|---|
| 1 | New | New inheritance TX | White (transparent) | `#FFFFFF` |
| 2 | Signed | TX signed in the wallet | Azure | `#2BC8ED` |
| 3 | Pushed | TX sent to will-executor | Azure-green | `#73F3C8` |
| 4 | Checked | TX actually present on the will-executor | Bright green | `#8AFA6C` |
| 5 | Confirmed | TX confirmed on the blockchain | Gray | `#BFBFBF` |
| 6 | Pending | TX awaiting confirmation on the blockchain | Yellow | `#FFCE30` |
| 7 | Failed | Communication failure with the will-executor | Red | `#E83845` |
| 8 | Invalidated | A UTXO input is no longer available | Orange | `#F87838` |
| 9 | Replaced | A backdated-locktime transaction spends the same input | Violet | `#FF97E9` |
## Behavior when the wallet balance or UTXOs change
If the balance or UTXO set of your BAL-managed wallet changes (you receive or spend funds), the inheritance must be updated. **BAL checks this automatically when Electrum closes** and updates the inheritance if needed.
This means you can use an inheritance-ready wallet for everyday Bitcoin transactions (ideally signing with a hardware key), knowing the entire wallet content will go to your heirs.
!!! warning "Read-only wallets and shared seeds"
- If you receive funds on this wallet via a **read-only copy** on another device (Zpub/Xpub), those funds are **not** added to the inheritance until you open the wallet in Electrum with BAL, so the plugin can update the UTXOs and re-send the will to the executors.
- If you use the **same seed on multiple devices** (strongly discouraged), spending even one satoshi elsewhere **invalidates the inheritance**: the UTXO structure changes and nodes discard the inheritance transaction.