Besu behaviour when Orion not available to process a private transaction

Description

Currently:
If a receiving Orion is available when the private transaction is distributed but is unavailable
when the privacy marker transaction is processed, the private transaction is not executed by
the receiving Besu node. The private states in the Besu nodes are then inconsistent.

Options:
1. Retain current behaviour and clearly doc requirement and strategies to ensure HA
2. Stop Besu when private tx unable to processed due to Orion being down. When Orion is back up, resync chain from point it stopped at
3. Log a message and provide a way to resync over skipped private transactions from the point they stopped being processed

Status

Assignee

Unassigned

Reporter

Madeline Murray

Labels

None

Refinement State

Not Started

Scrum Team

Revenant

Sprint

Fix versions

Priority

P3
Configure