A workstep is a prototype of one stepwise state transition contained in a
Proverthat ingests data passed to the
Workstepand outputs a zero-knowledge proof that can be used to verify synchronization of data amongst
Worksteps are useful for defining the real-world activities or operations to be used as synchronization check-points in a
Workflow. They provide context for the data required to instantiate, populate and execute a zero-knowledge
Proveras it relates to a corresponding business process.
Workstep configuration modal
When used in series, a verified claim from a previously derived
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.
The Workstep Creation form
- 1.Enter a workstep name and optionally provide a description.
- 2.Select the
General Consistencycircuit from the dropdown menu.
- 3.If a workstep should require finality (post the resulting proof to a configured network), click the
Requires Finalitycheckbox. Note: The final workstep in a workflow must require finality.
- 4.Search for and select the domain model you created previously in the
Select Domain Modelinput field.
- 5.If you have added additional participants to a workgroup, you can define the participants allowed to execute this workstep in the Participants dropdown. If no participants are specified, all participants in the workgroup will be able to execute this workstep.
Repeat this process until you have created a workflow that captures the business process you intend to synchronize.
The final workstep in a workflow must reach finality.