Skip to content

Releases

v0.1.12

Choose a tag to compare

@coreyphillips coreyphillips released this 27 Oct 03:11
v0.1.12
ef3573f

Adds Beignet v3 direct channel funding (bgnq) support to the native primary.

  • Compatible Bitkit, Beignet and Chicory wallets can fund a receiving phone's new channel or splice an existing channel directly from a confirmed onchain coin.
  • Includes authenticated request handling, exact transaction and fee validation, durable witness recovery, and coin reservations that survive restarts.
  • Rebuilds both AMD64 and ARM64 native daemons from the local LDK source; retains the qualified Iroh, Tor and JavaScript dependency set.

Qualification: both final images passed funded channel-open, splice, retry and restart checks, plus 12 startup/persistence checks per architecture. Beignet/native payments passed in both directions for new channels and splices. All 288 native library tests, 13 documentation tests and 266 dashboard tests passed. Testing used disposable regtest funds; physical Umbrel hardware and mainnet payments were not exercised.

Bitkit requires the matching updated local Android build and native AAR. Updating the primary alone does not update the phone. Keep the existing Umbrel wallet data when upgrading.

Both published architectures passed anonymous registry verification, and the community store pins the verified combined image digest. The native branch remains local; this release includes its exact source manifest and bundled third-party notices.

v0.1.11

Choose a tag to compare

@coreyphillips coreyphillips released this 26 Oct 19:39
v0.1.11
a6cdb24

Update the native FFOR offline-receive feature pairs to 440/441 and 442/443, matching Beignet and avoiding Eclair's on-the-fly funding assignments. Both AMD64 and ARM64 images contain rebuilt native daemons from the verified 0.1.10 source snapshot plus this protocol fix.

Upgrade the primary and compatible phone client together before using offline receive. Peers advertising only the former 560-563 bits intentionally no longer negotiate FFOR. Ordinary channels, wire-message encodings and stored wallet custody data remain unchanged. This native implementation does not implement or advertise the separate async receive service at 444/445.

Validation includes 266 dashboard tests, 14 native FFOR regression tests, and real encrypted Lightning handshakes against both release architectures. Disposable 0.1.10 wallets were upgraded in place: identities survived, new feature advertisements appeared, regtest addresses and unpaid invoices worked, and disabling offline settlement removed its advertisements. Tests used isolated, unfunded regtest wallets. Physical Umbrel hardware and funded offline payments were not exercised in this release.

Iroh, Tor and locked JavaScript dependencies retain the qualified 0.1.10 runtime. The attached source manifest and qualification records identify the exact source snapshot and binaries. The native source branch remains unpublished.

For manual installation, download the archive matching your hardware and verify it using SHA256SUMS. The community app on main pins the verified published 0.1.11 image. PR #8 records the source update and verification.

v0.1.10

Choose a tag to compare

@coreyphillips coreyphillips released this 26 Oct 17:08
a741647

Fix incoming primary payments that exceed a compatible private channel's original capacity. This release rebuilds the native daemon with the splice-compatible payment limit and retains the automatic balance updates from 0.1.9.

The Logs page now reads native wallet logs as well as process diagnostics, with Refresh, Copy logs and Download logs controls. Exports use bounded snapshots and redact sensitive values.

Testing

  • 266 manager tests and 24 Linux log tests passed.
  • 49 desktop/mobile browser checks passed.
  • Both AMD64 and ARM64 images passed startup, authentication, wallet restart, container restart and automatic receive checks.
  • A Beignet sender paid 50,000 regtest sats through the final ARM64 primary image to Bitkit's native client engine. The same channel grew from 40,000 to 110,000 sats and credited 49,850 sats after the 150 sat receive fee. This test did not exercise Android UI or physical Umbrel hardware.

Upgrade notes

Bitkit Primary Regtest version 197 already has the matching client changes. Existing channels keep their saved payment limit after an engine upgrade. Use a fresh test channel, or complete a controlled normal close and reopen with the updated primary and compatible client. Preserve wallet data.

The native LDK source branch remains local and unpublished. The attached source manifest and qualification record identify the exact source snapshot and binary hashes used in these images.

Download the archive matching your hardware: AMD64 for Intel/AMD, ARM64 for ARM. Verify it with SHA256SUMS before loading. The accompanying PR #7 contains the community app update and remains open for review. The normal Umbrel update becomes available after that PR is merged.

v0.1.9

Choose a tag to compare

@coreyphillips coreyphillips released this 26 Oct 16:53
v0.1.9
d3fcf50
  • Keep balances and payment activity updating while a receive QR is open, and refresh when returning to the dashboard.
  • Watch recent receive addresses through the wallet's configured Electrum or Esplora backend and request native synchronization when activity changes. Watches resume after restart. Bitcoin Core retains its native automatic synchronization.
  • Show live wallet balances beside the receive QR without replacing the address or invoice. Slow activity requests no longer hold up a ready balance, and temporary failures retain the last good value with a delay notice.
  • Protect receive requests from stale wallet or session responses, and preserve wallet isolation through stop, restart and deletion.

Monitoring covers the last 16 SegWit receive addresses generated by the dashboard. Native background synchronization remains active for other addresses and interrupted connections. The native wallet remains the source of balances and spendability.

Linux AMD64 and ARM64 release assets contain Docker archives and SHA256SUMS. Existing Tor, local TCP and Iroh connection selection and wallet deletion remain available.

v0.1.8

Choose a tag to compare

@coreyphillips coreyphillips released this 26 Oct 16:00
v0.1.8
fb985a7
  • Add Delete wallet in wallet Settings with exact-name confirmation and a full-backup option. Stop the wallet before deleting it.
  • Remove only the selected wallet and its local data, keeping other wallets and dashboard sign-in intact.
  • Keep interrupted deletions marked Deletion pending, with startup disabled and an explicit Finish deleting wallet action.

Deletion permanently removes the selected wallet’s local identity, channel state and connection identities. It does not send funds or close channels. Save a current full backup first if you need to retain the data; a recovery phrase alone cannot restore Lightning channels.

Linux AMD64 and ARM64 release assets contain the qualified Docker archives and SHA256SUMS. Automatic Tor, local TCP and Iroh connection selection from 0.1.7 remain available.

v0.1.7

Choose a tag to compare

@coreyphillips coreyphillips released this 26 Oct 15:35
v0.1.7
1a7792e
  • Add Enable Tor connections in wallet settings. The app now creates and retains a private v3 onion address automatically.
  • Choose Tor in Pair Chicory > Connection method to scan or copy its address while Iroh and local TCP remain enabled.
  • Show Tor startup progress and failures without disturbing the selected QR code. Preserve onion identity and Tor guard state through restart and full encrypted backup.

To enable it on an existing wallet, stop the wallet, open Settings > Edit configuration, enable Tor, save and start the wallet. Tor can take a few minutes to become reachable. This provides incoming Tor connections; outgoing Lightning and chain-backend connections retain their existing routing.

Linux AMD64 and ARM64 images include the bundled Tor service. The release assets contain the qualified Docker archives and SHA256SUMS.

v0.1.6

Choose a tag to compare

@coreyphillips coreyphillips released this 26 Oct 14:50
v0.1.6
a2341eb

Choose how each client connects to your node in Pair Chicory > Connection method:

  • View and scan separate QR codes for Iroh, Local network (TCP), and Tor when available.
  • Pair one client over Tor while Iroh remains enabled for other clients.
  • Keep the selected connection through dashboard refreshes, with matching Copy values and QR retry support.

Tor requires an existing v3 onion service mapped to the wallet's native Lightning port.

This release also includes the Electrum improvements since the last public release, v0.1.4: connections through the Umbrel device's own local hostname and support for host:port:t and host:port:s shorthand. Existing wallet identities and settings are preserved.

AMD64 and ARM64 image archives and SHA256 checksums are attached. Reload the dashboard tab after updating the app.

0.1.4: Recovery phrases and encrypted backups

Choose a tag to compare

@coreyphillips coreyphillips released this 26 Oct 02:56
v0.1.4
3f0b628
  • New wallets now have a 24-word recovery phrase. Open Settings > Recovery & backup to reveal and copy it. The phrase hides when the dialog closes, the tab is hidden, or one minute passes.
  • Back up all wallets downloads an encrypted full snapshot, including keys and current Lightning channel state. Wallets stay stopped after the download so you can save the backup safely before restarting them.
  • Existing wallets retain their binary seeds and node identities. They have no original mnemonic and use full backups instead.
  • Includes an offline restore tool that authenticates the archive before restoring private files to a new directory.

Both AMD64 and ARM64 are supported and tested with native wallet backup and restore. The native Lightning and Iroh binaries are unchanged. Reload the dashboard after updating.

A phrase alone does not restore Lightning channels. Keep the latest full backup and its password private, and never run an original wallet and restored copy simultaneously. See the backup and restore guide.

0.1.3: Stable Chicory pairing page

Pre-release

Choose a tag to compare

@coreyphillips coreyphillips released this 25 Oct 21:40
b3effb3

Fixes Pair Chicory jumping to the top every few seconds during live refresh.

  • Keeps the displayed pairing details and QR code mounted during background polling, preserving scroll position, Copy button focus and selected connection text.
  • Continues checking live connection details and updates the QR when its connection URI changes.
  • Discards delayed responses after navigation, logout or a wallet switch, and prevents a prior wallet's refresh from appearing in the newly selected wallet.
  • Includes all 0.1.2 Electrum fixes, including the plaintext Umbrel Fulcrum preset at tcp://10.21.21.200:50002, connection diagnostics and saved trailing-slash normalization.

Update LDK Node through your Umbrel community app store, then reload the dashboard tab. Keep the existing app data and wallets.

The scroll regression was reproduced on desktop and mobile Chrome layouts. The fix is checked with automatic polling, changing connection details, wallet lifecycle changes and delayed responses. Both AMD64 and ARM64 images serve the exact reviewed frontend and retain the previously qualified native daemon, Iroh components and Electrum backend. No funds were sent or existing wallets modified during testing.

0.1.2: Electrum setup and Fulcrum compatibility

Choose a tag to compare

@coreyphillips coreyphillips released this 25 Oct 21:30
290ba76

Fixes Electrum setup and connection errors using the same local server presets as Beignet Umbrel.

  • Umbrel Fulcrum uses tcp://10.21.21.200:50002 with SSL disabled. Umbrel Electrs uses tcp://10.21.21.10:50001.
  • Adds a Test connection action that verifies the Bitcoin network and explains DNS, TCP, TLS and wrong-network failures.
  • Normalizes trailing slashes in saved Electrum URLs before native startup. Existing wallet identity and channel storage are retained.
  • Replaces the invalid guessed Electrs default with explicit presets and optional Umbrel backend environment settings. Existing custom endpoints stay selected.

To repair an existing wallet, update the app, open that wallet's Settings, choose Edit configuration, select the installed Electrum server, test the connection and save. Start the same wallet. For Fulcrum on the same Umbrel, choose Umbrel Fulcrum. No wallet recreation or app uninstall is needed.

Verified on Linux AMD64 and ARM64: 32 manager tests, 13 browser checks, 14 container and Iroh lifecycle checks per architecture, 12 upgrade and preset checks per architecture, and 6 checks per architecture against an actual plaintext Mainnet Fulcrum server with empty disposable wallets. Native daemon and Iroh binaries are unchanged from the qualified 0.1.1 release. No funds were sent. Physical Umbrel installation remains untested.

The release archives and SHA256SUMS support local loading. The community app uses public architecture-specific container images selected through a pinned combined index.