You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an element of the rule is has no value, then the restriction does not apply. For example, if Destination Whitelist is empty, then the Coldcard will not consider the destination address when considering the rule.
If no rules are defined, then no PSBT will be signed. This can be useful for text message signing applications. On the other hand, an empty rule, allows any transaction to be signed, so be careful!
This reads to me as - if no rules are defined (empty parameter) then no PSBT will be signed, ie... all submitted PSBT's will be denied.
Maybe you should remove the
If no rules are defined, then no PSBT will be signed.
If empty==undefined, you should pick one word and use it throughout documentation.
My assessment of this section is : if all rules are empty then any PSBT submitted will be signed.
Please clarify so I can explain properly in Guide.
The text was updated successfully, but these errors were encountered:
On Wed, Feb 3, 2021 at 3:45 PM, Peter ***@***.***> wrote:
empty != undefined.
- no rules => no PSBT signing
- one empty rule => everything signed (no restrictions)
- more empty rules => same as a single empty rule.
—
You are receiving this because you authored the thread.
Reply to this email directly, [view it on GitHub](#8 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ANCACZABHGBIHUWQHM6TIPDS5GYXDANCNFSM4XA7F6AA).
This reads to me as - if no rules are defined (empty parameter) then no PSBT will be signed, ie... all submitted PSBT's will be denied.
Maybe you should remove the
If empty==undefined, you should pick one word and use it throughout documentation.
My assessment of this section is : if all rules are empty then any PSBT submitted will be signed.
Please clarify so I can explain properly in Guide.
The text was updated successfully, but these errors were encountered: