Skip to content
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.

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

Update Operation Proofs to use CapabilityInvocation proofs #40

Open
aljones15 opened this issue Sep 14, 2021 · 0 comments
Open

Update Operation Proofs to use CapabilityInvocation proofs #40

aljones15 opened this issue Sep 14, 2021 · 0 comments

Comments

@aljones15
Copy link
Contributor

aljones15 commented Sep 14, 2021

  1. All proofs (expect merge events) should have a purpose of CapabilityInvocation
  2. There should be two proofs for each ledger write or update
  3. The first proof should have capabilityAction: write and a invocationTarget set to the ledger itself with a postfix
    • <ledgerId>/config for LedgerConfiguration events and
    • <ledgerId>/records for writing new records to the ledger
  4. The second proof should also have capabilityAction: write and an invocationTarget set to the record.id
  5. Most if not all existing record writes in the test project should conform to the 2 CapabilityInvocation proofs
  6. All of the LedgerConfiguration writes will need to be changed from AssertionPurpose to CapabilityInvocation
@aljones15 aljones15 changed the title Add zcap context to WebLedgerConfiguration Update Operation Proofs to use CapabilityInvocation proofs Sep 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant