cobra51

You actually have some incoming traffic. Your node wouldn’t work without a little bit. You’re a Full Node since you validate all transactions and blocks. Usually, Full Nodes are the opposite of SPV nodes.

It’s all about asymmetric cryptography, like RSA or ECDSA. You sign with your private key and anyone can verify it with your public key. In Bitcoin, signatures are needed for transactions. Addresses like P2PKH and…

You are a Full Node as long as you're validating consensus rules, regardless of incoming connections. The only difference is whether peers can connect to you, but it doesn’t change your node’s role.

Nah, you're good. People can connect through port 8333, but Bitcoin Core is designed to only listen on that port. It doesn’t share sensitive data with anyone, so you shouldn't worry about it. The data shared is just…

Nope, you're definitely a node. Nodes connect to others and let others connect to them. If you haven't forwarded port 8333, then Bitcoin Core can’t allow incoming connections, but you can still connect out to others.…

If you turn off wallet features, it might work. I had Core running on a 1GB RAM VPS once. It was super optimized but struggled with IDB. The command line worked fine, no crashes, but you had to manage resources…

For sure it's doable. But running a Raspberry Pi as a main server? Not ideal. It's pretty underpowered and honestly not that much cheaper than better options. No vulnerabilities, just a smaller computer. If you're going…

The memory pool holds unconfirmed transactions your node sees that haven't been included in a block yet. So, the number represents how many transactions are in that pool, and memory usage shows how much memory is used…

As long as you're running Bitcoin Core, you're a node, even if it's not fully synced. You can safely turn off your computer after shutting it down properly. When you start it again, it’ll sync to the latest block. But…

That could be a better way to gauge things. But it really depends on how quickly the mempool fills up, right after a block can look very different than even 10 mins later. Core's estimates are pretty forgiving for…

It really depends on your connections and how open your peers' mempool policies are. Some platforms like Johoe and Mempool.space are super well-connected.

Are you fully synced? That warning usually pops up if the client doesn’t have enough transactions in the mempool to estimate fees accurately. It might also mean some transactions haven’t been confirmed yet.

Actually, total rewards for a block, including fees, is around 3.192BTC, which is roughly 211,972 bucks at the moment. Current block reward alone is 3.125BTC.

Probably just one. This dude was mining with 500GH for weeks, then upped it to 3TH. Seems sketchy for more than that.

I built a node following some tutorials on here. Raspbian Lite had temps around 65-67°C while syncing. Now I use Start9, and it’s faster and easier to customize.

I had mine with 4GB RAM, and yeah, it got hot. It took weeks for sync too.

What were you running on yours? How much RAM did it have?

I agree, Raspberry Pi might struggle with data analysis.

RAM failures can mess up your whole setup. Luckily, once installed properly, it doesn’t fail often. Each time Bitcoin Core verifies a block, it’s reading/writing to chainstate a lot, so low RAM could slow things down.

Storage is cheaper than RAM, and if your chainstate is in RAM, any RAM corruption could cause serious issues, leading to needing another reindex. It’s likely Bitcoin Core still reserves some disk space for chainstate.