pull down to refresh
43 sats \ 3 replies \ @Scoresby 4 Dec \ parent \ on: Why Should I Have a Bitcoin Core Full Node If I'm Not a Miner? bitcoin_beginners
Not relevant to my answer.
Yes. When you only turn your node on for broadcast/receive, your list of peers goes stale. Sometimes you have to resort to hard coded list of peers to get connected again. This is a trust issue. Maybe you trust the hard coded list, but it's a clear benefit to not need such a thing. When your node is mostly on, you develop a more organic set of peers. Much harder to attack.
Yes. Serving blocks is only a little of it, relaying unconfirmed transactions is important for the reasons I listed above. I believe your node still relays unconfirmed txs even if port 8333 is closed (please let me know if I'm wrong).
Same as above.
Just for few of your onchain txs is not relevant to have a full blown core node 24/7.
If you transact only onchain you can easily just start that core app every day, few minutes and let it sync. Then close it down. Nothing burger. It's all fine.
KEEPING A CORE NODE 24/7 OPEN IT DOESN'T MEAN YOU HELP THE NETWORK. You help only yourself.
Even if you use another client connected to that core node, like Sparrow, you need it only TO SERVE THE LATEST BLOCKS and sync your wallet. That's all.
On contrary, if you do not know how to secure well your network and keep a core 24/7 you are mostly receive more attacks than usual and will slow down your whole network, FOR NOTHING.
reply
reply
It helps only yourself.
If you are a miner or big LN routing node is totally another story. But for a regular meaningless user, it doesn't matter.
reply