From ea6b5c5fb9bc3ab0f6183c84ab81c54b9b57e7ab Mon Sep 17 00:00:00 2001
From: nicholaspai <9457025+nicholaspai@users.noreply.github.com>
Date: Fri, 20 Dec 2024 09:47:37 -0500
Subject: [PATCH] Update ERC-7683: Add clause about not knowing
 minOutput.recipient at order creation time

Merged by EIP-Bot.
---
 ERCS/erc-7683.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/ERCS/erc-7683.md b/ERCS/erc-7683.md
index 222c87d9f5..83bb4778d2 100644
--- a/ERCS/erc-7683.md
+++ b/ERCS/erc-7683.md
@@ -108,7 +108,8 @@ struct ResolvedCrossChainOrder {
 	Output[] maxSpent;
 	/// @dev The minimum outputs that must be given to the filler as part of order settlement. Similar to maxSpent, it's possible
 	///      that special order types may not be able to guarantee the exact amount at open time, so this should be considered
-	///      a floor on filler receipts.
+	///      a floor on filler receipts. Setting the `recipient` of an `Output` to address(0) indicates that the filler is not
+        ///      known when creating this order.
 	Output[] minReceived;
 	/// @dev Each instruction in this array is parameterizes a single leg of the fill. This provides the filler with the information
 	///      necessary to perform the fill on the destination(s).