-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
- All proofs (expect merge events) should have a purpose of
CapabilityInvocation
- There should be two proofs for each ledger write or update
- The first proof should have
capabilityAction: write
and ainvocationTarget
set to the ledger itself with a postfix<ledgerId>/config
for LedgerConfiguration events and<ledgerId>/records
for writing new records to the ledger
- The second proof should also have
capabilityAction: write
and aninvocationTarget
set to the record.id - Most if not all existing record writes in the test project should conform to the 2 CapabilityInvocation proofs
- All of the LedgerConfiguration writes will need to be changed from
AssertionPurpose
toCapabilityInvocation
Metadata
Metadata
Assignees
Labels
No labels