new NUT is the way

03.md

@@ -76,12 +76,6 @@ If successful, `Bob` will respond with a `PostSwapResponse`
 }
 ```
 
-## Cached Responses
-
-`Bob` **MUST** cache every successful `PostSwapResponse` using `PostSwapRequest` as the key.
-Each cache entry has a TTL (Time-To-Live) of at least 1800 seconds.
-In the event of a network error, `Alice` **CAN** replay the same exact request and get the same response.
-
 [00]: 00.md
 [01]: 01.md
 [02]: 02.md

04.md

@@ -161,12 +161,6 @@ Response of `Bob`:
 
 If the invoice was not paid yet, `Bob` responds with an error. In that case, `Alice` **CAN** repeat the same request until the Lightning invoice is settled.
 
-## Cached Responses
-
-`Bob` **MUST** cache every successful `PostMintBolt11Response` using `PostMintBolt11Request` as the key.
-Each cache entry has a TTL (Time-To-Live) of at least 1800 seconds.
-In the event of a network error, `Alice` **CAN** replay the same exact request and get the same response.
-
 ## Unblinding signatures
 
 Upon receiving the `BlindSignatures` from the mint `Bob`, the wallet of `Alice` unblinds them to generate `Proofs` (using the blinding factor `r` and the mint's public key `K`, see BDHKE [NUT-00][00]). The wallet then stores these `Proofs` in its database:

05.md

@@ -157,12 +157,6 @@ Response `PostMeltQuoteBolt11Response` of `Bob`:
 }
 ```
 
-## Cached Responses
-
-`Bob` **MUST** cache every successful `PostMeltBolt11Response` using `PostMeltBolt11Request` as the key.
-Each cache entry has a TTL (Time-To-Live) of at least 1800 seconds.
-In the event of a network error, `Alice` **CAN** replay the same exact request and get the same response.
-
 ## Settings
 
 The mint's settings for this nut indicate the supported method-unit pairs for melting. They are part of the info response of the mint ([NUT-06][06]) which in this case reads