{% extends "base.html" %} {% from "macros.jinja" import window_vars with context %} {% block scripts %} {{ window_vars(user) }} {% endblock %} {% block page %}
Manage your bitSpire fleet, liquidity providers, and commission distribution.
Each ATM is paired with one dedicated wallet. Inbound payments to that wallet trigger automatic distribution.
LPs receive proportional DCA distributions from your machines. Balances reflect deposits less the sats they've been paid.
Record fiat handed in by LPs. Confirmed deposits increase the LP's balance and feed proportional DCA distribution.
After the LNbits platform fee is taken, the remainder is distributed across the wallets you configure here. Per-machine overrides take precedence over your default rules.
Settlements that didn't process cleanly. Errored ones need retry; stuck ones may need force-reset (processor crashed mid-flight).
Client-side CSV exports of the data currently loaded in the dashboard. For larger date ranges or server-side filters, use the LNbits API directly.
Register an ATM by its Nostr public key. Choose the LNbits wallet that will receive cash-out payments from this machine — settlements there trigger the automatic distribution chain.
Mints a dedicated signing key for inside the operator bunker and issues a one-shot seed URL. The spire's key never touches its disk; its cash-outs route to this machine's wallet. Re-pairing issues a fresh seed.
provision-atm. Shown once — copy it now.
Every bitSpire transaction lands here. Click a row's menu for retry / partial-dispense / notes.
The machine owns these counts — it holds the notes. You record what you did to a bay and it keeps the running total. Bay count and denomination set are hardware-determined (re-provision via atm-tui to change the bays themselves).
"Pending" means sent but not yet echoed back by the machine. Every publish carries the recent window, so a pending operation keeps being re-offered until it lands — there is nothing to retry by hand.
Notes are append-only and timestamped. Use for reconciliation context, off-LN refund records, dispute narrative, etc.
Charged on every transaction's principal across the LNbits instance. Independent per direction. Each direction's total (super + operator) is capped at 15%. Operators see these as a read-only banner. Wallet ID is where the collected fee lands; typically a wallet you (the super) own.
) — not
operator-editable. See aiolabs/satmachineadmin#26.
The deposit will be marked rejected and won't count toward the LP's balance. Optional reason for the audit trail.
Enrol an LP at one of your machines. Wallet, DCA mode, and autoforward are configured by the LP themselves via the satmachineclient extension — you can't set them here. Deposits are refused until the LP has registered.