[Blocked] Add multi-relay verification for kind 5 delete propagation #4

New Issue

2026-04-14T14:36:51Z

priyanshu_bharti commented

2026-04-14 14:36:51 +00:00

Summary

We need end-to-end verification that kind 5 deletions are propagated correctly across relays and visible to observers.

Status

Blocked

Blocked by

Scope

Define reproducible test flow across at least 2 relays
Verify successful deletion propagation
Verify failed deletions do not propagate

Acceptance Criteria

Publish then delete flow confirms observer receives kind 5 deletion signal.
Negative cases (not-author, invalid tag, nothing-to-delete) show no propagation.
Test steps are documented clearly for maintainers and reviewers.

### Summary We need end-to-end verification that kind 5 deletions are propagated correctly across relays and visible to observers. ### Status Blocked ### Blocked by - https://gitea.coracle.social/coracle/nostrlib/issues/2 - https://gitea.coracle.social/coracle/nostrlib/issues/3 - https://gitea.coracle.social/coracle/zooid/issues/3 ### Related - coracle/zooid#1 (Deletes don't get broadcasted) ### Scope - Define reproducible test flow across at least 2 relays - Verify successful deletion propagation - Verify failed deletions do not propagate ### Acceptance Criteria 1. Publish then delete flow confirms observer receives kind 5 deletion signal. 2. Negative cases (not-author, invalid tag, nothing-to-delete) show no propagation. 3. Test steps are documented clearly for maintainers and reviewers.

hodlbod closed this issue

2026-04-17 18:52:24 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: coracle/zooid#4