MiniBolt v2.2

What's new

• Added a new Frigate bonus guide, original author @j4b4t0.
• To improve privacy, sovereignty, and censorship resistance, the guide is now accessible via an onion address: miniboltgbsvmnrowjvjmslh2imy47bsmms4azn73fvtcudbjr32ghqd.onion to access via Tor.

What's changed

• Nostr relay in Rust bonus guide actions:
  • Renamed the user, systemd service, and PostgreSQL database from generic Nostr Relay naming to Nostr RS Relay-specific software naming to support future relay software guides.
  • Fixed broken links and applied various documentation improvements.
• Deleted the Ordisrespector bonus guide and added it as a Bitcoin client: Bitcoin Core extra section, named Ordisrespector Patch filter.
• Bitcoin client: Bitcoin Core actions:
  • Added a new method to install Option 2: Compiling from source code, and changed the old one to Option 1: Using precompiled binaries.
  • Relocated the Ordisrespector old bonus guide extra sections to the Bitcoin client: Bitcoin Core extra sections, in concrete: Reject other possible data included in transactions.
  • The Upgrade section has been updated to include the two new installation methods added.
• Bitcoin Knots bonus guide actions:
  • Added new Bitcoin Knots compatible Extra sections from Bitcoin client: Bitcoin Core guide
• Updated guides terminology from "Bitcoin Core" to "Bitcoin client" where appropriate, reflecting support for both Bitcoin Core and Bitcoin Knots.
• Public Pool bonus guide actions:
  • Reworked the steps and content to improve alignment and optimization with the project architecture.
  • Exposed the HTTP port 4200 to enable access via Tor onion hidden service.
• Relocated the "Add an external fee estimator to the LND" extra section where appropriate, from Bitcoin client: Bitcoin Core to Lightning client: LND guide.
• Added Bitcoin Knots as a supported Bitcoin client option in service requirements. [Bitcoin client: Bitcoin Core or Bitcoin Knots]
• Updated Lightning Client: LND to the latest v0.21.0, which includes a database migration of the payment store from the KV format to native SQL. Only applies if you use PostgreSQL as the database backend. Here are some logs for reference for the migration process:

[...]
[INF] PYDB: Starting payment migration from KV to SQL...
[INF] PYDB: Found ~217 index entries to migrate (includes duplicates)
[INF] PYDB: ========================================
[INF] PYDB:    Payment Migration Summary
[INF] PYDB: ========================================
[INF] PYDB: Total Payments:        217
[INF] PYDB:   Successful:       159
[INF] PYDB:   Failed:           58
[INF] PYDB:   In-Flight:        0
[INF] PYDB:   Initiated:        0
[INF] PYDB:
[INF] PYDB: Total HTLC Attempts:   165
[INF] PYDB:   Settled:          165
[INF] PYDB:   Failed:           0
[INF] PYDB:   In-Flight:        0
[INF] PYDB:
[INF] PYDB: Total Route Hops:      472
[INF] PYDB:
[INF] PYDB: Migration Duration:    2.024768309s
[INF] PYDB: ========================================
[...]

• The software version of some services was updated; no changes were made to the functional configuration.

Additional notes

• To stay up to date with the latest changes and releases, make sure GitHub release notifications are enabled for this repository by following the instructions below: