Hot answers tagged

4

Your points 1 & 2 are both correct. The good news is the only time those old blocks get requested is by new nodes that are still bootstrapping and downloading the blockchain for the first time. As long as those old blocks are available and accessible somewhere, those new nodes will sync up just fine. Another fact about pruned nodes is they are required ...


2

The IP-addesses of Bitcoin nodes are not a secret. See addr Nodes don't explicitly tell other nodes their Bitcoin addresses. Since nodes pass on details of other nodes transactions, working out which nodes originated a transaction isn't straightforward. Since the set of Bitcoin nodes is constantly changing, and nodes go offline temporarily (or permanently), ...


2

Miners offer up blocks to the network hoping that their offerings will be accepted. Other nodes may accept or reject such blocks. A node that accepts a block adds that block to their copy of the blockchain. Nodes that don't accept a particular block don't add it to their copy of the blockchain and don't pass on that block to anyone else. Any miner that is ...


2

If the nodes are running different versions then communication cannot continue. That is incorrect. If two nodes interact which have different versions, they just communicate using the lower of the two versions.


1

There is no way for a block explorer to know which addresses belong to the same wallets, in fact no block explorer shows the balance of wallets but only by addresses. The only way to know which addresses are from the same wallet is having generated that wallet or having it's seed. Wallets are a client structure that collects all the addresses for which you ...


Only top voted, non community-wiki answers of a minimum length are eligible