Skip to main content
Warp Verify
Warp Verify is in beta. Attestations are recorded on testnets, and interfaces may change before general availability.
Warp Verify issues attestations: signed, on-chain-recorded statements that a claim about an asset is true, backed by a zero-knowledge proof. A verifier can confirm the claim without seeing the private data behind it.

Attestation types

Attestations can describe real-world assets such as real estate, invoices and receivables, equity, commodities, carbon credits and intellectual property.

Lifecycle

1

Create

In the Warp Platform, open your project’s Warp Verify section, choose a type and describe the asset and policy.
2

Prove and attest

Warp compiles the circuit, generates the proof and records the attestation in an on-chain registry. The attestation becomes active.
3

Share and check

Share the attestation ID or its public check page (https://platform.usewarp.net/verify/check/<id>). Anyone can check it with the API below.
4

Renew or revoke

Attestations can expire. Renew them before they lapse, or revoke them if the claim no longer holds.

Check an attestation

Check an attestation is public: it needs no API key and is rate limited per IP.
valid is true only when the attestation is active, not expired or revoked, and its proof was verified and registered on-chain in the Warp attestation registry. Treat valid: false, or a status such as revoked or expired, as a failed check.

Next steps

ZK Proofs

Build and verify your own circuits.

Check an attestation (API)

Response reference.