Whether another's node syncinfo shows that another node is ahead or behind ours
Whether another's node syncinfo shows that another node is ahead or behind ours
other's node sync info
Equal if nodes have the same history, Younger if another node is behind, Older if a new node is ahead
Is there's no history, even genesis block
Whether a modifier could be applied to the history
Whether a modifier could be applied to the history
- modifier to apply
Whether the history contains a modifier with the given id
Whether the history contains a modifier with the given id
- modifier's id
Whether the history contains the given modifier
Whether the history contains the given modifier
- modifier
History of a blockchain system is some blocktree in fact (like this: http://image.slidesharecdn.com/sfbitcoindev-chepurnoy-2015-150322043044-conversion-gate01/95/proofofstake-its-improvements-san-francisco-bitcoin-devs-hackathon-12-638.jpg), where longest chain is being considered as canonical one, containing right kind of history.
In cryptocurrencies of today blocktree view is usually implicit, means code supports only linear history, but other options are possible.
To say "longest chain" is the canonical one is simplification, usually some kind of "cumulative difficulty" function has been used instead, even in PoW systems.