From 32ed0173022dc81fc751883dfa1865c5334067d6 Mon Sep 17 00:00:00 2001
From: Greg Bernstein <gregb@grotto-networking.com>
Date: Tue, 4 Jun 2024 15:55:36 -0700
Subject: [PATCH] JCS Context Injection: update proofConfig to be  clone of
 options as done in all other specs and don't set individual fields.

Co-authored-by: Dave Longley <dlongley@digitalbazaar.com>
---
 index.html | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/index.html b/index.html
index 42462e3..73cdeee 100644
--- a/index.html
+++ b/index.html
@@ -1082,14 +1082,6 @@ <h4>Proof Configuration (eddsa-jcs-2022)</h4>
 Let <var>proofConfig</var> be a clone of the <var>options</var> object.
             </li>
             <li>
-Set <var>proofConfig</var>.<var>type</var> to
-<var>options</var>.<var>type</var>.
-            </li>
-            <li>
-If <var>options</var>.<var>cryptosuite</var> is set, set
-<var>proofConfig</var>.<var>cryptosuite</var> to its value.
-            </li>
-            <li>
 If <var>options</var>.<var>type</var> is not set to `DataIntegrityProof` and
 <var>proofConfig</var>.<var>cryptosuite</var> is not set to `eddsa-jcs-2022`, an
 `INVALID_PROOF_CONFIGURATION` error MUST be raised.