Proverthat ingests data passed to the
Workstepand outputs a zero-knowledge proof that can be used to verify synchronization of data amongst
Workflow. They provide context for the data required to instantiate, populate and execute a zero-knowledge
Proveras it relates to a corresponding business process.
proofcan be used as input for a subsequent
Workstepto ensure that a
Workflowcannot be completed if all participants are not in sync. As additional worksteps are completed and a
Workflowis completed, the
proofderived from the exit-workstep provides verifiable proof of synchronization amongst all participants.
Proveris a zero knowledge circuit that generates a method by which one party (the prover) can prove to another party (the verifier) that a given statement is true while the prover avoids conveying any additional information apart from the fact that the statement is indeed true. To learn more about provers, see Provide Privacy.
WorkflowInstanceand all subsequent
Workstepincluded in a
Workflow. Once executed as a
WorkstepInstance, it outputs a recursive
proofencompassing all previous
proofresulting from the execution exit-workstep must always be published to a
WorkstepInstanceis a run-time execution of a deployed
WorkstepInstanceexecutions included in a
WorkflowInstanceare spawned when the conditions specified in the prime-workstep are met. A
WorkstepInstanceshares the same schema as a
Workstepand is distinguishable by the presence of a value in the
Organizationacting as a
Organizationscoped JWT is available for use
Organizationis a participant in a
Workflowhas been created
Workstepobjects in the authorized scope
Workstepis calculated by the service, as determined by the order of creation.