Three weeks ago we said we’d tell each feature’s story properly on the 22nd, so that’s what the keynote is about. There are deep dive videos on every big thing coming this week too: installing it on different kinds of hardware with FailSafe, Photos and the iPhone app, and a local AI and GPUs demo.
A special thank you to everyone who ran the betas over the last three weeks and sent us feedback and bug reports. You all made this release far better than it would have been otherwise!
Also, we’re doing 10% off the Umbrel Home and Umbrel Pro (up to $200) this week to celebrate 2.0, until the 29th: https://umbrel.com
Right now I am running 1.7.4 with an external drive storing the btc blockchain. I have updated the btc and electrs docker-compose.yml files to point to the external blockchain. Everything is working great. If I upgrade to 2.0 will these custom entries be wiped? Or will the new storage manager feature see them and link the bitcoin app to the external drive? If not, what steps do I need to take to have 2.0 point to the external blockchain without any blockchain history loss? My umbrel node is running on a laptop.
Hey @croland, 2.0 lets you set up folder mounts through the app settings now, so you can point both apps at your existing blockchain without maintaining compose edits. It won’t automatically import those edits, though.
Here’s how I’d do it:
Before upgrading, save copies of both compose files and back up any wallets.
After upgrading, open Files and check that you can browse the existing blockchain folder on your external drive. Don’t format or initialize it.
Go to Settings → App settings → Bitcoin → Storage → Access to your folders → Advanced → Add custom folder.
Choose the app service matching the one you edited in compose. Select the existing folder on your external drive, and set “Path inside app service” to the same container path from your current volume entry. For example, in /external/bitcoin:/data/.bitcoin, that’s /data/.bitcoin. Leave read-only off for Bitcoin.
Add the folder and save the changes. Repeat for electrs, using its own service and container path, and preserving its existing read-only setting. Repeat for any other volume entries you customized.
This points the apps at the files already there rather than moving them, so you don’t need the “Move” app-storage option. Check that Bitcoin resumes at its previous block height and electrs catches up. If Bitcoin starts syncing from scratch, stop it and double-check the selected folder and container path before letting it continue.