rewording the paragraph

QED-it · Aug 6, 2024 · 601c6ec · 601c6ec
1 parent d94eb96
commit 601c6ec
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 7 deletions.
diff --git a/zip-0226.html b/zip-0226.html
@@ -66,13 +66,11 @@
              computation defined in ZIP 227 <a id="footnote-reference-19" class="footnote_reference" href="#zip-0227">5</a>.</p>
             <p>We include the ability to pause the ZSA functionality, via a
                 <span class="math">\(\mathsf{enableZSA}\)</span>
-             boolean flag. When this flag is set to false, it is not possible to perform transactions involving Custom Assets (the Action statement as modified for ZSAs will not be satisfied). When this flag is set to true, it will be possible to perform transactions involving Custom Assets, subject to the values of the
+             boolean flag. When this flag is set to false, the proof will fail for any non-native Asset, making it impossible to perform transactions involving Custom Assets. When this flag is set to true, the circuit will allow transactions involving Custom Assets subject to the values of the
                 <span class="math">\(\mathsf{enableSpendsOrchard}\)</span>
              and
                 <span class="math">\(\mathsf{enableOutputsOrchard}\)</span>
-             flags. That is, the types of transactions allowed for ZSAs will match those allowed for the Orchard pool in general when the
-                <span class="math">\(\mathsf{enableZSA}\)</span>
-             flag is set to true.</p>
+             flags, similar to the vanilla Orchard setting.</p>
             <p>Finally, in this ZIP we also describe the <em>burn</em> mechanism, which is a direct extension of the transfer mechanism. The burn process uses a similar mechanism to what is used in Orchard to unshield ZEC, by using the
                 <span class="math">\(\mathsf{valueBalance}\)</span>
              of the Asset in question. Burning Assets is useful for many purposes, including bridging of Wrapped Assets and removing supply of Assets.</p>

diff --git a/zip-0226.rst b/zip-0226.rst
@@ -61,9 +61,8 @@ Because in a single transaction all value commitments are balanced, there must b
 In order to ensure the security of the transfers, and as we will explain below, we are redefining input dummy notes [#protocol-orcharddummynotes]_ for Custom Assets, as we need to enforce that the :math:`\mathsf{AssetBase}` of the output note of that Split Action is the output of a valid :math:`\mathsf{ZSAValueBase}` computation defined in ZIP 227 [#zip-0227]_.
 
 We include the ability to pause the ZSA functionality, via a :math:`\mathsf{enableZSA}` boolean flag. 
-When this flag is set to false, it is not possible to perform transactions involving Custom Assets (the Action statement as modified for ZSAs will not be satisfied).
-When this flag is set to true, it will be possible to perform transactions involving Custom Assets, subject to the values of the :math:`\mathsf{enableSpendsOrchard}` and :math:`\mathsf{enableOutputsOrchard}` flags.
-That is, the types of transactions allowed for ZSAs will match those allowed for the Orchard pool in general when the :math:`\mathsf{enableZSA}` flag is set to true.
+When this flag is set to false, the proof will fail for any non-native Asset, making it  impossible to perform transactions involving Custom Assets.
+When this flag is set to true, the circuit will allow transactions involving Custom Assets subject to the values of the :math:`\mathsf{enableSpendsOrchard}` and :math:`\mathsf{enableOutputsOrchard}` flags, similar to the vanilla Orchard setting.
 
 Finally, in this ZIP we also describe the *burn* mechanism, which is a direct extension of the transfer mechanism. The burn process uses a similar mechanism to what is used in Orchard to unshield ZEC, by using the :math:`\mathsf{valueBalance}` of the Asset in question. Burning Assets is useful for many purposes, including bridging of Wrapped Assets and removing supply of Assets.