28 lines
1.7 KiB
Markdown
Executable File
28 lines
1.7 KiB
Markdown
Executable File
# Security & Privacy
|
|
|
|
## UTXO consolidation caution
|
|
|
|
When you send the **entire contents** of a wallet, you risk losing the privacy of your UTXOs.
|
|
|
|
A good rule of thumb: execute the inheritance leaving a small remainder to another wallet, especially when there is only one heir. For example: 99.7% to the heir and 0.3% to a random Bitcoin address (e.g., taken randomly from a block explorer). This makes the transaction harder to interpret.
|
|
|
|
## Same seed on multiple devices
|
|
|
|
Using the same seed on multiple devices is **strongly discouraged**. If you spend even a single satoshi from another device, you change the wallet's UTXO structure and **invalidate the inheritance transaction** — nodes will discard it.
|
|
|
|
## Read-only (watch-only) wallets
|
|
|
|
If you monitor the wallet via Zpub/Xpub on other devices, funds received there are **not** automatically added to the inheritance. Open the wallet in Electrum with BAL so the plugin can update the UTXOs and re-send the will to the executors.
|
|
|
|
## Wallet file vs. seed
|
|
|
|
The BAL inheritance data lives in the **Electrum wallet file**, not in the seed. Keep backups of the wallet file (`File → Save backup`) and do not lose the wallet password: restoring from seed recovers the funds but **loses the inheritance configuration**.
|
|
|
|
## Will-executor privacy
|
|
|
|
Inheritance transactions stored on will-executor servers are not publicly accessible. Only your plugin can check their presence (right-click → **Check** in the WILL tab).
|
|
|
|
## Backup transaction discretion
|
|
|
|
If you deliver an offline [backup transaction](user-guide/backup-transaction.md) directly to an heir, the heir learns the date and amount of the inheritance — consider whether that is prudent, or use a notary/trusted person instead.
|