How do I verify an approval happened?
To verify an approval happened, check the proof of approval: a signed proof artifact that binds the approver’s authorized identity, the approved action (as a hash), and an anchored timestamp. Verification confirms an authorized party approved the specific action at the stated time — mathematically, without trusting the approval system.
Explanation
Approvals gate money, access, and risk, which makes them frequent targets of disputes and manipulation. An approval recorded only in a workflow system can be back-dated, misattributed, or edited, and confirming it requires trusting that system.
A proof of approval removes that dependency. Because the artifact is signed by the approver’s authority and commits to the action and time, anyone can verify the approval independently and detect any tampering or misattribution.
How to do it
- 1Bind the approval to the approver’s authorized identity and role.
- 2Commit to the approved action with a hash so the details stay private.
- 3Anchor and sign a timestamp to prevent back-dating.
- 4Emit the proof of approval artifact at the moment of sign-off.
- 5Verify by checking the signature, the issuer’s authority, and the timestamp.
Examples
High-value payment
A treasury controller approves a wire above threshold; the proof confirms the authorized controller signed off before funds moved.
Privileged access grant
A manager approves admin access. The proof evidences authorized approval, supporting least-privilege controls.
Related concepts
Related comparisons
Next steps
See how this works end-to-end in the live demo, or read the cornerstone guide.