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.

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.

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.

But OP would need a VPS with at least 12 GB. My Bitcoin Core chainstate is around 10.8 GB, and you also need about 300 MB of RAM for mempool and some more for the OS.

There are a few third-party services that let you do RPC calls supported by full nodes. I’ve heard of getblock.io offering that, but never actually used it, so do your own research.

Proof of Work always ends up concentrating power with those who have more resources. Even if you create some GPU and ASIC resistant algo, the hashrate still gets concentrated. Decentralization isn’t really happening.…

Seems like more of a fun project for learning than serious mining. It’s a good way to see what’s being hashed and sent to the pool. This script isn’t really optimized, right? Doesn’t seem multithreaded?

Not entirely. P2PKH has been around for a while, but the concept of addresses evolved. They’re hashed versions of public keys now. And HD wallets can generate many pairs from a master key.

Well, not exactly. Addresses are a bit abstract. Blockchain just has unspent outputs. You don’t create three entries, just one transaction showing the unspent output being spent and the new ones being created.

Was it a connection issue? I’m running nodes via Snap and it’s all good. What did the logs say?