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
As a Block Node
I want the verification handler to be another consumer from the unverified, unparsed ring buffer
so it consumes the blockstream at the same time as other subscribers that also need an unverified stream.
Notes:
Verification Handler needs to communicate with the BlockStatusManager the state of the Block.
Verifier Handler most consume all of the pending items on the RingBuffer and keep it's own ordered queue for asynchronous processing.
Calculate Hash using BlockHashingService Interface
Compare BlockHash received vs calculated
Verify Signature of BlockHash (Verify BlockProof)
Set a Verified Status using the BlockStatusManager
And should re-propagate the verified possibly also parsed block on the verified ringBuffer
*Verified RingBuffer, Pipeline and BlockStatusManager might be worked on a separate Epic. Block Pipelining Epic, for the intents of this Ticket, those interfaces will have a NOOP implementation that all it does is register metrics (maybe) and set logs (definitively)
The text was updated successfully, but these errors were encountered:
As a Block Node
I want the verification handler to be another consumer from the unverified, unparsed ring buffer
so it consumes the blockstream at the same time as other subscribers that also need an unverified stream.
Notes:
BlockHashingService
InterfaceBlockProof
)BlockStatusManager
ringBuffer
*Verified RingBuffer, Pipeline and BlockStatusManager might be worked on a separate Epic.
Block Pipelining Epic
, for the intents of this Ticket, those interfaces will have a NOOP implementation that all it does is register metrics (maybe) and set logs (definitively)The text was updated successfully, but these errors were encountered: