Bitcoin

Security – Header-first synchronization and malicious peers

Since header-first synchronization specifies that the entire header chain is downloaded from a single peer, how does the downloading node know that it will not be presented with a header chain outside of the manufactured consensus? Do you cross-reference to other peers? What is the exact mechanism used here?

Related Articles

Back to top button