2 Matching Annotations
  1. May 2024
    1. An escrow cache of unverified out-of-order event provides an opportunity for malicious at-tackers to send forged event that may fill up the cache as a type of denial of service attack. Forthis reason escrow caches are typically FIFO (first-in-first-out) where older events are flushed tomake room for newer events.

      This may misfire, when there's a ton of valid events to sync, whose amount is greater than the cache limit.

      May happen when adding a new witness, requiring to sync the entire history. (do we need to provide it the entire history though? only the last not-yet-verified events are of interest for the controller to be signed by the witness)

    2. Event escrow isan optional implementation specific configurable capability of controllers and witnesses imple-mentations