Add note about replaceable event re-computation and re-publishing

lawalletio · Feb 21, 2024 · 58bce92 · 58bce92
1 parent 6f650ba
commit 58bce92
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/pages/wallet-provider/nostr.mdx b/pages/wallet-provider/nostr.mdx
@@ -80,6 +80,11 @@ A NOSTR event is expected to define three related entities:
 
 In what follows we'll simply refer to an event's `AUTHOR`, `SIGNER`, and `TARGET`s as defined above, and refrain from referring to specific event fields or tag values or indices.
 
+## Replaceable Event Treatment
+
+Since NOSTR replaceable events may "collide" if both of them happen to happen on the exact same second, internal modules are prepared to **re-compute and re-publish** replaceable events with a one-second delay.
+This ensures that replaceable events are eventually consistent with the platform's internal state.
+
 ## Multi-NIP-04
 
 We extend the [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md) specification so as to be able to have multi-recipients.

diff --git a/pages/wallet-provider/nostr/card-config-change-ack.mdx b/pages/wallet-provider/nostr/card-config-change-ack.mdx
@@ -3,6 +3,8 @@
 This event is used to signal the successful change of an NFC card's configuration for a given client.
 It serves as the configuration repository for the client in question, by realizing this via a replaceable event tagged with the client's pubkey.
 
+This event being replaceable, [replaceable event treatment considerations](../nostr#replaceable-event-treatment) apply.
+
 ## Event Signature
 
 A _Card Config Change Acknowledgement_ event has the following form: