IRI gossip currently using a single packet. With https://github.com/iotaledger/iri/issues/1794 iri will support split up gossip. We should change our pipeline to make use of this feature.
Motivation
More specific requesting results in less network usage and faster syncing time
Requirements
Change the pipeline to use TX_REQUEST and TX_BROADCAST instead of TRANSACTION_GOSSIP
Change transactionRequester to use correct protocol method
Open Questions (optional)
How are we handling TipsRequester? (probably remove it)
Description
IRI gossip currently using a single packet. With https://github.com/iotaledger/iri/issues/1794 iri will support split up gossip. We should change our pipeline to make use of this feature.
Motivation
More specific requesting results in less network usage and faster syncing time
Requirements
Open Questions (optional)
How are we handling TipsRequester? (probably remove it)