From df266f9f319b24b3dfbaba5c3391d50f1f6df51f Mon Sep 17 00:00:00 2001 From: lollerfirst Date: Sat, 26 Oct 2024 20:03:08 +0200 Subject: [PATCH] ecash loss, not data loss --- XX.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/XX.md b/XX.md index 2292ef0..b0278b7 100644 --- a/XX.md +++ b/XX.md @@ -5,7 +5,7 @@ NUT-XX: Cached Responses --- -To mitigate the risk of potential ecash loss due to network errors during critical operations such as minting, swapping, and melting, we introduce a caching mechanism for successful responses. This mechanism uses the `POST` request path and the serialized body contents to derive a key and then cache the responses using that key. If an identical request is received, the system will provide the cached response, minimizing the risk of data loss in the event of network disruptions. +To mitigate the risk of potential ecash loss due to network errors during critical operations such as minting, swapping, and melting, we introduce a caching mechanism for successful responses. This mechanism uses the `POST` request path and the serialized body contents to derive a key and then cache the responses using that key. If an identical request is received, the system will provide the cached response, minimizing the risk of ecash loss in the event of network disruptions. ## Requests & Responses