getumbrel/umbrel-bitcoin

The official Bitcoin Node app for Umbrel, powered by Bitcoin Core.

umbrel-bitcoin's Issues

`mempoolfullrbf=1` should be set in `bitcoin.conf` by default

Over 90% of hashpower is mining full-RBF now because it's common for full-RBF replacements to pay quite high fees. Some of the reasons why users run nodes include self-soverign fee estimation and block explorers: both those use-cases are improved by accepting and relaying common fee-paying transactions that miners do in fact mine, as you have a better understanding of what fees are being paid, and of course, block explorers running on Umbrel devices can show those transactions. Notably, both https://mempool.space and https://blockstream.info switched to running full-RBF quite some time ago to be able to display those transactions.

Users of course can continue to turn it off if desired. But on balance I believe the default should be on for typical Umbrel use-cases.

Bitcoin Core doesn't seem to be interested in changing the defaults, nor do Bitcoin Core members seem to be interested in explaining why. They already made two releases recently without changing the default, even though a supermajority of hash power have adopted full-RBF. But that shouldn't stop us from doing the right thing for Umbrel users.

Please integrate Prometheus exporters

You might find useful to add to the compose image the following:

https://github.com/jvstein/bitcoin-prometheus-exporter

That way we can monitor how bitcoind is doing.

Thanks.

Expose maxuploadtarget via settings

For users in low to moderate bandwidth settings, it is important to be able to modify how much data is uploaded by the node. The default setting is to upload as hard as it can.

Currently the only approach for reconfiguring this behaviour is to ssh onto the host and edit bitcoin.conf directly.

When Umbrel receives an update, this setting is overridden and the process has to be repeated.

It may be ideal to expose this setting via the Umbrel settings page and persist it across updates.

Add `deprecatedrpc=create_bdb` to `bitcoin.conf`

BerkeleyDB (BDB) wallet creation was deprecated in Bitcoin Core v26.0. This leads to issues for JoinMarket and thus also Jam. The problem should be fixed once JoinMarket supports Bitcoin Core descriptor wallets.

For the time being, the fix for affected users is to add deprecatedrpc=create_bdb to bitcoin.conf file.

Can this be added to Umbrel in order for users not getting annoyed by sudden malfunction after updating to Core v26?
What is the proper procedure here?

Thank you for any feedback on this 🙏

Pruned version

This issue was discussed before in here but ended up not being implemented for the sake of other apps' health.

Making another version of this umbrel-bitcoin might be a wiser solution. Electrs (and other apps that depend on a non-pruned node) can then depend on the non-pruned version and apps that support pruned nodes (like lnd, cln, etc...) can depend on either versions.

Having a node, besides being beneficial for the usage of some apps, is essential for one's sovereignty on the blockchain. And pruning would allow more people to run nodes.

UI feature to enable mempoolfullrbf=1

Hi, there doesn't seem to be a way to easily update the Bitcoin Core config file on Umbrel, so it would be nice if there was an advanced settings where Umbrel users have the ability to set their node mempool policy with this new flag coming in Bitcoin Core 0.24. Thanks

Feature to modify mempool memory size

Hi there, it would be nice if there was an advanced feature in the Bitcoin Core node UI to modify the amount of memory dedicated to the mempool. Ideally it could be set to 0mb up to 1000mb (suggest keeping the current default at 300mb)

Connecting Ledger Live

Hi, I’m trying to connect ledger live to umbrel and running into issues. I’m suspecting it could because of tor but not sure. I reached out to ledger to see if they could support native tor and they have forwarded this over to their dev team to see if they could get this working with umbrel. But I’m not sure if umbrel would also need to provide support for ledger? If so, could this be possible? I’d like to use my own node when using ledger and don’t want to move all my funds to a new wallet because of the lack of support.

If support could be added, that would be fantastic.

thanks so much.

Expose console in Bitcoin Core Node UI

Hi there, it would be nice if I could use a console in the Bitcoin Core Node app to run a limited set of console commands (I realize there is no wallet). Thanks!

Synchronized Percent Displays Incorrect Value

I'm setting up a new BitCoin node on Umbrel for the first time. I was watching it sync, and noticed the math seemed to be a bit off.

Here's an example from my Node:

Note that 71,993 / 790,002 should equal 0.091130149. Moving that to a percentage should make it 9.1130149%. It's about 1/10th the way complete.

I initially suspected that maybe the code was doing 71,993 / 790,002 and then rounding, but that would result in 0.09% displayed, not 0.01%. This appears to not be the case. Either way, the math appears to be incorrect, unless my assumption of what it's counting is incorrect.

Strategy on Bitcoin consensus forks

With the current discussion about deploying Taproot, I am interested how Umbrel will handle policy for consensus. I believe your users are already significant part of the network and might have different preferences. Will you include Taproot? Will it be LOT=true or LOT=false, or maybe possibility to choose between them?
Thanks for you work guys!

[Shower Thought] If NETWORK=regtest a cronjob should generate blocks

1 block per minute seems reasonable, since an empty block (most will be empty) is a couple hundred bytes anyways.
The address to generate to should be an on-chain LND address so you can use those mined coins in LND.
Also, to start off with, it should just generate like 1000 blocks to the LND address to start off with.

Maybe even add a UI button for regtest only that says (generate block) and will generate a block on demand.