Skip to content

Appendix on Proof Sets/Chains: Clarity improvements #335

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Appendix on Proof Sets/Chains: Clarity improvements #335

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
130612b
Clarity improvements. Fix wording to add missing explanatory text. Br…
Wind4Greg Feb 18, 2025
daaf2f5
Appendix on Proof Sets/Chains: Clarity improvements -- further wordin…
Wind4Greg Feb 19, 2025
302ead6
Appendix on Proof Sets/Chains: Clarity improvements -- additional wor…
Wind4Greg Feb 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3330,9 +3330,9 @@ <h2>Understanding Proof Sets and Proof Chains</h2>
<em>secretVPE/publicVPE</em>, respectively.
</p>
<p>
When multiple signatories intend to sign an |inputDocument| and the ordering of
those signatures are not of concern and there are no dependencies amongst the
signatures then a [=proof set=] is typically a more straight forward
When multiple signatories intend to sign an |inputDocument|, the ordering of
those signatures is not of concern, and there are no dependencies amongst the
signatures, then a [=proof set=] is typically a more straightforward
construction.
</p>
<p>
Expand Down