A Few Questions - How Umbrel Works

  1. Is there any way to (like Bitcoin Core) turn on/off outgoing connections (the ones that make your node visible to others to send block info out and not just receive it), or is it default and only set to “on” in order to support the decentralization of the network? I’m cool either way, just curious.

  2. Is my Umbrel a Bitcoin core node or an electrum server, or both? I’ve heard there are some privacy advantages to having an electrum server over a core node (something about indexing transactions?), and when trying to connect some certain wallets, there is electrum server info provided.

  3. Am I actually getting any say in the “consensus rules” by running a node (i.e. if there is a fork) if I’m just hodling bitcoin and not doing many transactions (other than the occasional incoming to cold storage)? I used to think that just having a node was all you needed, but recently heard that only those receiving transactions, the “economic majority,” have influence on the consensus rules. Is this correct? Does opening and closing lightning channels qualify as economic activity that increases my contribution and therefore “say” in the protocol?

1 Like

Great questions. I’d like to know as well.

By default, Umbrel is not a listening node = doesn’t allow other nodes to connect to it. It is not possible for now to turn this feature on or off.

Umbrel bundles a Bitcoin Core node, a Lightning node and an Electrum Server (electrs). An Electrum Server needs Core to work, you can see it as a more efficient way to get data from Core.

Not sure to understand what you mean by “receiving transactions”.

Lightning has nothing to do with the main chain updates (forks). It’s a second layer.

1 Like