Product · Verification
Six ways to prove a condition is met.
A milestone releases only when its condition is proven. Pick the mode that fits the deal — from a human sign-off to a signed data feed.
Dual sign-off
When: Subjective acceptance — both parties confirm the work is done.
Evidence: Two cryptographic signatures.
Time / deadline
When: A date-based release with deemed approval if no objection.
Evidence: Timestamp + deemed-approval window.
Document hash
When: Delivery proven by a document matching an agreed hash.
Evidence: Uploaded document SHA-256 = expected.
API webhook
When: An external system signals completion (shipping, CI, ERP).
Evidence: HMAC-signed inbound event + payload hash.
Oracle feed
When: A certified data feed crosses a threshold (price, index, weather).
Evidence: Signed reading vs. threshold.
Accredited verifier
When: An independent third party inspects and attests.
Evidence: Signed attestation from an accredited verifier.
The moat
The verifier network.
Accredited third parties — inspectors, auditors, arbitrators — attest conditions independently. Accreditation is gated and scoped; an unaccredited verifier cannot satisfy a VERIFIER condition.