User Story 2026_074
As a Participant, I want the CASE_MANAGER to check each ledger entry's hash before it sends the entry, and to send no later entry of that send after an entry that fails, so that a damaged entry in its store never reaches my copy of the case
Notes
The check is the same one a receiver makes, and it applies to fan-out, replay and backfill alike. Sending the entries after a damaged one would only give receivers a chain with a gap they cannot fill, so the send stops there. Each entry held back is logged at ERROR, because it means the CASE_MANAGER's own store is damaged.
Metadata
- Speaker: Participant
- Roles: all
- Related issues: #4487 (source Concern: the user-story set is stale), #2599 (source Idea: distributed case consistency and replication)
- Drafted for: #4516 (split of the catch-all story 2022_045)
- Added: 2026-11-04