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

Aggiunto zoom immagini (click to enlarge) con mkdocs-glightbox

Browse Source
This commit is contained in:
bitcoinafterlife
2026-07-26 14:04:59 +02:00
parent 254045dc16
commit 2ab16d910e
10 changed files with 307 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
docs/getting-started/installation.md
View File

@@ -23,12 +23,35 @@ Get the latest release from the [plugin releases page](https://bitcoin-after.lif
![Electrum Tools menu with Plugins](../img/install-electrum-plugins-menu.png){ .screenshot }
*Electrum → Tools → Plugins.*
BAL is an **external plugin**, so it is added from a `.zip` file:
1. Open Electrum and go to **Tools → Plugins**.
2. Choose **install from file** and select the BAL zip.
2. **Internal plugins** are listed in the dialog — you toggle their checkbox to enable or disable them.
3. **External plugins** such as BAL are imported from `.zip` files with the **Add** button in the plugins dialog.
4. Some plugins (hardware wallets) are enabled automatically when you create or restore a hardware wallet.
![Install from file dialog](../img/install-from-file.png){ .screenshot }
*Selecting the plugin archive.*
### First-time setup: the plugin authorization password
The first time you load **any** external plugin, Electrum asks you to set a **plugin
authorization password**. Two things to know about it:
- It is **independent of your wallet password**, and it can be reset if you forget it.
- Setting it requires **administrator (root) permissions**, because Electrum writes a
password-derived public key into the system. On later startups that key lets Electrum
verify the plugin's authenticity without asking you for the password again.
!!! info "Why administrator permissions are needed"
This is an Electrum security measure, not something specific to BAL. The elevated
permissions are what stop **malware from silently installing or modifying plugins**,
or from tampering with the stored key. External plugins can only be enabled by
someone who can enter that password — so a piece of malware running as your normal
user cannot enable one behind your back.
Full details: [plugins.electrum.org](https://plugins.electrum.org/)
## 3. Enable and restart
Tick **Bitcoin After Life** in the plugin list, then restart Electrum.
@@ -51,3 +74,9 @@ Step-by-step installation notes for specific platforms are kept in their own rep
- [Windows installation](https://bitcoin-after.life/gitea/bitcoinafterlife/bal_plugin_windows_installation)
- [Linux installation](https://bitcoin-after.life/gitea/bitcoinafterlife/bal_plugin_linux_installation)
## More on Electrum plugins
For how Electrum's plugin system works in general — internal vs external plugins, the
authorization password, and the plugin directory — see the official reference:
[plugins.electrum.org](https://plugins.electrum.org/)

214
docs/img/architecture.svg Normal file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 59 KiB

4
docs/index.md
View File

@@ -1,6 +1,6 @@
<div class="bal-hero">
<img class="logo-light" src="assets/logo-mark-black.svg" alt="Bitcoin After Life">
<img class="logo-dark" src="assets/logo-mark-white.svg" alt="Bitcoin After Life">
<img class="logo-light no-lightbox" src="assets/logo-mark-black.svg" alt="Bitcoin After Life">
<img class="logo-dark no-lightbox" src="assets/logo-mark-white.svg" alt="Bitcoin After Life">
<span class="name">Bitcoin After Life</span>
<span class="tagline">BAL Protocol — decentralized Bitcoin inheritance</span>
</div>

5
docs/protocol/how-it-works.md
View File

@@ -2,6 +2,11 @@
A summary of the mechanism, for readers who want to understand what happens underneath the interface.
## Architecture at a glance
![BAL architecture: plugin, Will-Executor, Bitcoin Core](../img/architecture.svg){ .diagram }
*How a will travels from the Electrum plugin to the Bitcoin network. Click to enlarge.*
## The building block: absolute time-locks
Bitcoin lets a transaction declare an **absolute `nLockTime`**: a point in time before which the transaction is not valid. Nodes reject such a transaction from the mempool until that moment arrives — this is a consensus rule, not a policy choice.

21
docs/stylesheets/extra.css
View File

@@ -226,3 +226,24 @@ p > img.screenshot + em {
.bal-hero .logo-dark { display: none; }
[data-md-color-scheme="slate"] .bal-hero .logo-light { display: none; }
[data-md-color-scheme="slate"] .bal-hero .logo-dark { display: inline; }
/* -------- Diagrams -------------------------------------------------------- */
/* Wide technical diagrams: full content width, light frame, no drop shadow
(they already have their own internal panels). */
img.diagram {
display: block;
width: 100%;
height: auto;
border: 1px solid var(--md-default-fg-color--lightest);
border-radius: 8px;
background: var(--bal-panel);
padding: 4px;
}
[data-md-color-scheme="slate"] img.diagram { background: #f6f8fa; }
img.diagram + em {
display: block;
margin-top: .4rem;
font-size: .72rem;
font-style: normal;
color: var(--md-default-fg-color--light);
}

8
docs/will-executors/running-a-server.md
View File

@@ -20,6 +20,14 @@ This page covers setting up your own Will-Executor node. If you are wondering *w
Two things to keep in mind: for a user's redundancy, a consortium still counts as **one** Will-Executor; and the internal split is an agreement outside the protocol, which BAL neither arbitrates nor guarantees.
See the [architecture diagram](../protocol/how-it-works.md#architecture-at-a-glance) for how
`bal-server` and `bal-pusher` fit into the full flow from plugin to Bitcoin node.
## Architecture at a glance
![BAL architecture: plugin, Will-Executor, Bitcoin Core](../img/architecture.svg){ .diagram }
*How a will travels from the Electrum plugin to the Bitcoin network. Click to enlarge.*
## The two components
| Component | Role |

4
docs/will-executors/what-they-are.md
View File

@@ -11,6 +11,10 @@ A Will-Executor is a server with one narrow job: **it stores pre-signed inherita
What it *does* require is longevity: being still there, still working, years from now.
!!! info "See the whole flow"
The [architecture diagram](../protocol/how-it-works.md#architecture-at-a-glance) shows how a
will travels from the Electrum plugin, through a Will-Executor, to the Bitcoin network.
## Why competition makes it work
When you create your will, the plugin generates **a separate transaction for every Will-Executor you selected**. Each of those transactions carries an extra output paying that specific server its fee.