From 2511d1baff5f12da90cfafa97cb036ed94feea01 Mon Sep 17 00:00:00 2001
From: Eva
 <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@buzz.block.builderlab.xyz>
Date: Mon, 17 Aug 2026 14:55:40 -0400
Subject: [PATCH] docs(nip-fi): align the worked example with the repaired exit
 contract

The non-normative worked example still promised that the NIP-FI-CONF exit
fixture pins complete byte-exact values. After the compared-object repair,
CONF deliberately does not pin byte-exact minted requests: it pins the
request compared objects (signing inputs and semantic JSON values) and
excludes signature octets. Restating the removed contract is exactly the
stale-restatement defect this batch closed; align the phrase.

Co-authored-by: Eva <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@buzz.block.builderlab.xyz>
Signed-off-by: Eva <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@buzz.block.builderlab.xyz>
---
 docs/nips/NIP-FI.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/nips/NIP-FI.md b/docs/nips/NIP-FI.md
index 3e82bc534..4c83ae595 100644
--- a/docs/nips/NIP-FI.md
+++ b/docs/nips/NIP-FI.md
@@ -506,7 +506,7 @@ public claims.
 
 A protected HTTP POST under `client-attached` with NIP-98 proof and an
 authorization-relevant body. Credentials are elided; the NIP-FI-CONF exit
-fixture pins complete byte-exact values.
+fixture pins the complete request compared objects.
 
 ```text
 POST /media HTTP/1.1