You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2020. It is now read-only.
We shouldn't expose the network layer directly, but add an abstraction in-between.
Avoid duplicates in the queue.
This will affect how nodes sync: e.g.,: nodes in chain A -> B - > C, if the syncing process starts top to bottom (If B hears a transaction), B will wait until it is solid and C will not start syncing until B is solid.
Description
We only want to pass solid transactions to other nodes.
Motivation
Non solid transactions can't affect the ledger state. They might be plane spam.
No need to gossip them.
Requirements
TransactionValidator
solidifier, add it to the broadcast queue.MilestoneSolidifier
add it to the broadcast queueTipsSolidifier
(off by default) add it to the broadcast queue.The text was updated successfully, but these errors were encountered: