Skip to content

Update Operation Proofs to use CapabilityInvocation proofs #40

@aljones15

Description

@aljones15
  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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions