From 888ba213743c300199e2b395362944f5f7676501 Mon Sep 17 00:00:00 2001 From: Ivan FB Date: Thu, 30 Apr 2026 13:58:33 +0200 Subject: [PATCH] Revert "MessageSentEvent is the one that confirms a msg was rx by a store node" This reverts commit 01cf30d5e8f39e52a464df563ece8296433b5202. --- standards/application/reliable-channel-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standards/application/reliable-channel-api.md b/standards/application/reliable-channel-api.md index b430e13..3a487c9 100644 --- a/standards/application/reliable-channel-api.md +++ b/standards/application/reliable-channel-api.md @@ -106,7 +106,7 @@ See [SEGMENTATION](./segmentation.md). - Each new segment to be sent, requires the following data: - `MessageId`: a 40-character random hex string (e.g. `a23f89b4df7e1ba5a709352da3a247a4fd609f4c`), generated by the Reliable Channel API. - `ChannelId`: the `channelId` passed to `createReliableChannel`. - - Retrieval hint: the transport `MessageHash` of previous segments, exposed by the underlying [MESSAGING-API](/standards/application/messaging-api.md) upon ``MessageSentEvent` reception. + - Retrieval hint: the transport `MessageHash` of previous segments, exposed by the underlying [MESSAGING-API](/standards/application/messaging-api.md) upon ``MessageSendPropagatedEvent` reception. The hint provider registered during [Node initialization](#node-initialization) performs this `MessageId → MessageHash` lookup. In turn, that mapping MUST be persisted by SDS using the `persistence` backend configured in `SdsConfig`. - Each sent segment is registered in an outgoing buffer.