Skip to main content
  1. A Member queues a transaction via web or SDK Transactions can be initiated through the web dashboard or programmatically via the API & SDK. If the transaction does not match any policies, the Member will be unable to queue the transaction.
  2. Required approvals are collected If the transaction is governed by a policy that requires manual approval by a Member or Group, those approvals must be provided.
    • Web workflow: Members approve in the web application, then sign the transaction on their mobile wallet. The mobile wallet independently runs the policy engine to verify the transaction before allowing the signature.
    • SDK workflow: Members approve programmatically via the SDK. The SDK independently runs the policy engine to verify the transaction before approval.
  3. The transaction is executed via web or SDK Once all approvals are collected, the transaction initiator or any reviewer can execute the transaction via the web application or SDK. The off-chain Guardian Service independently runs the policy engine to verify the transaction. If valid, it submits the transaction to the on-chain Smart Contracts, which also run the policy engine on-chain before executing.