Author

Topic: How would a node detect a reorganization/orphan of the blockchain? (Read 671 times)

sr. member
Activity: 287
Merit: 250
A full node should be able to see every blockchain, sans the possibility of some MITM attacks.

What if the node is more like a 9/10ths node?

If you don't download the full copy of the blockchain you're not considered a full node. In that case(you download just the block headers) you're susceptible to sybil attack by some entities controlling more than 50% of the hashpower feeding you the wrong chain.
Is there any way to defend against a sybil attack if I don't download every transaction, I do have some transactions, but not all of them?

How does a full node defend against an attacker with >50% of the hashpower?
hero member
Activity: 784
Merit: 1000
A full node should be able to see every blockchain, sans the possibility of some MITM attacks.

What if the node is more like a 9/10ths node?

If you don't download the full copy of the blockchain you're not considered a full node. In that case(you download just the block headers) you're susceptible to sybil attack by some entities controlling more than 50% of the hashpower feeding you the wrong chain.
sr. member
Activity: 287
Merit: 250
A full node should be able to see every blockchain, sans the possibility of some MITM attacks.

What if the node is more like a 9/10ths node?
hero member
Activity: 784
Merit: 1000
A full node should be able to see every blockchain, sans the possibility of some MITM attacks.
sr. member
Activity: 287
Merit: 250
Such as it was downloading the wrong chain, and suddenly the chain ends?

Like if 2-3 blocks back was suddenly marked as orphaned, how would the qt client understand this had happened?
Jump to: