Implement Sync Prototype

[jcarraror]

• Motivation: As it stands, OrbiterSDK lacks a synchronization mechanism. This means that if a node bootstraps while the blockchain has already advanced, it cannot catch up with the rest of the network, since the code for downloading blocks and syncing to the highest height has not been implemented. Currently, the AIO script that creates all nodes starts the network at the same height for every node, eliminating the need for synchronization.

• Objectives: Implement a basic sync functionality to enable recently joined nodes to catch up with the network.

• Success Criteria: Successfully synchronize a node after the network has already bootstrapped, based on the highest height of connected nodes.

• Dependencies: No external dependencies are required for this milestone.

• Risks and Mitigations: To ensure secure synchronization, it is necessary to request blockchain information from multiple nodes and compare the data to avoid downloading from a malicious actor. Moreover, the network employs the rdPoS mechanism, which guarantees that each block can only be created by a single validator. This means that if a node accidentally downloads a block from a malicious source, it can switch to another node upon recognizing the block's invalidity, and continue syncing with the best/closest node.

• Resource Allocation: This feature will impact the Syncer and P2P classes and may also affect the State class. Adequate resources should be allocated to ensure smooth implementation and integration with the existing system.