Server Status

BAL serverchecking…
Pusherchecking…
Synced block · bitcoin
—
waiting…
Server Info
Version
Status —
Description —
Network —
Network Stats — …
Total TXs
—
Waiting
—
Sent
—
Elsewhere
—
Estimate
Protocol Value*
—
Earned*
—
In Mempool*
—
Scheduled*
—
Missed* Estimate
—
* Since the activation date of this Will-Executor. Values are estimates based on our own inheritance fee. Only Earned is income we actually collected; Missed estimates what competing executors earned (we only see our own transactions), and Protocol Value is the sum of all four.
Payment Address
Address
Min Fee —
Chain —
Wallet Balance —
Tor Access
TOR Loading…

Submit transactions privately from anywhere using this .onion address.

Submit Transaction

Paste one or more pre-signed raw Bitcoin transactions (hex-encoded). Each transaction must include an output paying at least the minimum fee to the server's address. The server will broadcast it when its locktime is reached.

Network —
Only hex characters (0-9, a-f). Multiple transactions: one per line.
How it works
1. Sign Create a Bitcoin transaction with a future locktime and sign it offline using your wallet.
2. Submit Paste the hex here. Include an output paying the fee to the server's address.
3. Wait This server watches every Bitcoin block. When the locktime is reached, it broadcasts your tx automatically.

Payment Settings

Bitcoin Mainnet
It is strongly recommended to use a single fixed address for the entire lifetime of this will executor. Changing the address later may cause previously submitted transactions to pay fees to the old address, which could become unmonitored.
Minimum fee in satoshis that each transaction must pay.
This description is shown in the /<chain>/info endpoint response.
Server Branding
No
Logo
PNG, SVG, JPEG, WebP · max 200KB · 32–1024 px
Text shown next to the logo in the header (max 30 characters). Also visible publicly via /<chain>/info.

Transaction List

Transactions
Transaction states
WAITING locktime not reached yet IN MEMPOOL broadcast, not yet confirmed CONFIRMED confirmed on-chain DONE ELSEWHERE completed by another executor
Network —
Loading...

Backup & Restore

Automatic Backups

This app creates an automatic backup of the database every 7 days. If the server was offline when one was due, it is created as soon as the server is back.

Backup files are named bal-YYYYMMDD.db and stored in the configured backup directory.

Up to 12 backups are retained (one per week for 12 weeks). The oldest backup is automatically removed when a new one is created.

Backup Storage Location
Path to store automatic backups. Leave empty for default (<data-dir>/backup). To use an external drive, enter its mount path (e.g. /mnt/external/backups).
Restore from Automatic Backup

Select a saved automatic backup to merge its transactions into the current database. Only new transactions are added — existing ones are preserved. The database is not replaced.

Download Database Backup

Download the complete SQLite database including all transactions, settings, and keys.

Import Transactions from Backup

Upload a previously downloaded database to merge its transactions. Only new transactions are added — existing ones are preserved. The database is not replaced.