PROOFLAYER
CRYPTOGRAPHIC VERIFICATION INFRASTRUCTURE

VERIFY ANYTHING.
TRUST THE PROOF.

Reusable cryptographic verification infrastructure for applications that demand verifiable results. Submit proofs, inspect verification results, and integrate proof verification into your own systems.

MODULAR VERIFICATIONDEVELOPER-FIRSTCRYPTOGRAPHICALLY VERIFIABLE
LOCAL DEMONSTRATIONNO EXTERNAL REQUESTS
PROOF INPUTmessage / witness
VERIFIERdeterministic check
RESULTverified / invalid
prooflayer://verify
01 / VERIFICATION LAB

Run the check.
See the proof.

All demonstrations execute locally in your browser. Inputs are never transmitted to a server.

01

Hash Integrity Check

Calculate a SHA-256 digest and compare it with an expected value. A matching hash confirms integrity—not the truth of an arbitrary claim.

02

Signature Verification

Verify an Ed25519 signature using a raw public key and signature encoded as base64. Private keys are never requested.

READY — awaiting input
03

Proof Interface

A reusable interface for proof systems. Only implemented mechanisms produce a verification result.

READY
02 / EXPLORER

Local verification
history.

Events generated by your local verification activity. These are not public blockchain transactions.

⌘ K
No verification events yetRun a check in the Verification Lab to populate this explorer.
03 / ARCHITECTURE

A layer for
verifiable apps.

Composable primitives for moving a proof from an application to a deterministic result.

COMPONENT / APPLICATION LAYER

Application Layer

The product or protocol that needs a claim verified.

APPLICATION PROOF VALIDATION VERIFIER RESULT
04 / DEVELOPER PORTAL

Build with
proof.

Clear contracts, honest capability boundaries, and primitives designed for integration.

GETTING STARTED

From input to result.

Run a local verification, inspect its status, and use the result in your application.

Open lab
PROPOSED API

One interface. Many verifiers.

POST /v1/verify

{
  "type": "signature",
  "proof": { ... },
  "publicInputs": { ... }
}
SECURITY MODEL

Verify, don't assume.

Verifier correctness, input validation, trust assumptions, and limitations should be explicit in every integration.

Read security model
05 / SECURITY & TRANSPARENCY

Proof is a tool.
Not a promise.

Proof verification does not automatically prove that an underlying real-world claim is true. A verifier must validate the correct proof system, public inputs, and verification parameters.

Invalid and malformed inputs must fail safely. Sensitive inputs should not be transmitted to external services without explicit consent. Local demonstrations are not substitutes for audited production infrastructure.

Actual cryptographic operations
No wallet or private key required
Honest unsupported states
06 / PROOF SYSTEM REGISTRY

Capability
registry.

Integration status reflects what is actually implemented—not what is on the roadmap.

PROOF SYSTEMPURPOSESTATUSCOMPLEXITY
Digital signaturesAuthenticate messages with a public key and signature.IMPLEMENTEDLow
Hash commitmentsCompare deterministic digests for integrity checks.IMPLEMENTEDLow
Merkle membership proofsProve inclusion in a committed data structure.PLANNEDMedium
Zero-knowledge proofsVerify statements without exposing the witness.PLANNEDHigh
On-chain verificationRead verification results from a smart contract.PLANNEDHigh