Axiom ZK workflow introduction

The TLDR on how Axiom works at a high level

You will perform three tasks when creating any Axiom zk-workflow

  1. Design and deploy the workflow via Provide Shuttle. The magic of the Provide platform is in templating your integration scenario to be represented by zero knowledge proofs.

  2. Invite participants and distribute credentials. Distributing cryptographic credentials has long been a difficult chore for IT teams - especially when private keys are involved. Shuttle makes this as simple as a slack or email invite without compromising any security of the underlying private keys.

  3. Generate, propagate, and verify proofs. This the part where you and your business partner's applications interact asynchronously to each other. In the places where your data would previously fall into a 'black box' against eachother - you and your business partner can determine you have synchronicity of your data sets without exposing your systems to one another.

Interested to see it action? Check out this example for a basic introduction applying zk proofs to a banking master data example

If you were able to connect Shuttle directly to your SAP system - you can check out a more advanced use case involving EDI iDoics and zero knowledge proofs up next

Last updated