diff --git a/neode-ui/src/views/settings/AccountInfoSection.vue b/neode-ui/src/views/settings/AccountInfoSection.vue index 848f8a31..2d365d42 100644 --- a/neode-ui/src/views/settings/AccountInfoSection.vue +++ b/neode-ui/src/views/settings/AccountInfoSection.vue @@ -188,6 +188,26 @@ init()
+ +
+
+ v1.7.97-alpha + June 16, 2026 +
+
+

The Bitcoin sync status on the home screen no longer disappears for a moment when it refreshes. If the node was briefly busy, the panel used to vanish and pop back; it now stays put and simply shows "Updating…" until the next reading arrives, while a genuinely stopped node still correctly shows as not running.

+

Bitcoin sync progress on the home screen now updates more promptly, so the percentage and block height keep pace with the node instead of lagging behind.

+

The Lightning wallet "connect your wallet" screen loads its details and QR code again across all nodes, instead of failing to fetch them.

+

Your list of trusted nodes is now clean: the same node no longer appears several times under different names, and removed nodes stay removed. In chat, a node that previously showed up as two separate contacts now appears just once.

+

Browsing another node's cloud is smoother: music and video files from a peer now preview and play properly (including seeking partway through), and the connection now shows a small badge telling you whether it's using the fast encrypted mesh or the slower Tor network.

+

Opening "My Folders" in the cloud now shows a clear, friendly message when the file app isn't running, instead of a confusing error.

+

The Electrum server app opens on its own once it's ready, instead of sometimes leaving a loading spinner stuck on top of the screen.

+

The Fedimint app now displays with its proper styling and icons, instead of appearing unstyled with a missing image.

+

The Mempool app now connects to your Bitcoin node whether the node is Bitcoin Core or Bitcoin Knots, instead of only working with one of them.

+

Nodes start up cleanly after a reboot. On some boots the node's main service was trying to start before its data drive had finished mounting, so it failed and retried about twenty times over roughly five minutes — showing a wall of "Failed to start" messages — before finally coming up. It now waits for the data drive to be ready first, so it starts on the first try.

+

The background images throughout the interface now load faster — they've been made significantly smaller with no loss of quality.

+
+