zkReveal builds on-chain receipt and settlement infrastructure for digital sellers.

The current focus is Reveal Receipt Mode — a minimal USDC-based primitive for seller-issued checkout flows, payment links, agents, and private digital commerce.

A buyer pays, settlement happens immediately, and an on-chain receipt is created.

That receipt becomes the source of truth for seller systems, agents, dashboards, apps, and indexers.

Receipt Mode is a payment and receipt layer — not a marketplace or escrow protocol.

zkReveal provides infrastructure for:

• seller-issued payment links
• crypto checkout for digital products
• on-chain proof-of-payment receipts
• agentic and Telegram-native commerce flows
• private access and credential sales
• gated content and memberships
• composable settlement primitives for apps and marketplaces

The v1 flow is intentionally simple:

seller creates listing
→ seller/backend generates purchase reference
→ buyer pays in USDC
→ contract records receipt
→ seller system fulfills off-chain

We are currently building Reveal Receipt Mode as the first production primitive.

The current stack focuses on:

• Solidity + Foundry smart contracts
• Arbitrum-based deployment
• USDC settlement
• seller-owned listings
• seller-scoped purchase references
• EIP-712 signed quotes for dynamic checkout
• event-driven, indexer-friendly design
• lightweight seller flows through agents, dashboards, payment links, and Telegram interfaces

This is the first layer — not the final system.

For real-world checkout flows, Receipt Mode supports EIP-712 signed quotes.

Signed quotes bind:

• buyer
• seller
• listing
• amount
• purchase reference
• metadata hash
• settlement token
• expiry
• chain and contract

This enables:

• private payment links
• agent-assisted and Telegram-native checkout
• dynamic pricing
• integrator fees
• seller-controlled checkout logic

Reveal Receipt Mode records payment, settlement, and receipt creation on-chain.

Fulfillment happens off-chain through seller systems, agents, dashboards, APIs, or applications.

This keeps the v1 primitive simple, composable, and honest about its trust boundaries.

zkReveal does not try to force every part of digital commerce on-chain. Instead, it provides a reliable receipt layer that other systems can build on.

zkReveal is built around a few principles:

• minimal — focused primitives, not bloated systems
• composable — usable inside apps, agents, APIs, and marketplaces
• honest — clear trust boundaries instead of fake decentralization
• seller-first — built for real sellers and real checkout flows
• event-driven — easy to integrate through indexers and listeners
• extensible — new primitives over complex upgrades

• contracts — Solidity + Foundry implementation of Reveal Receipt Mode

Additional repositories for SDKs, agents, apps, and tooling may follow.

zkReveal is in an early-stage, infrastructure-first phase.

Current capabilities include:

• immediate USDC settlement
• seller-owned listings
• seller-scoped purchase references
• EIP-712 signed receipt quotes
• on-chain receipt records
• off-chain fulfillment

zkReveal is not currently a marketplace, escrow protocol, or dispute system.

The current version of zkReveal does not use zero-knowledge proofs yet.

The name comes from the long-term direction of the project: building privacy-aware commerce infrastructure where payments, receipts, access rights, delivery claims, and agent workflows can become more selective, private, and programmable.

The current MVP focuses on the foundation first:

• USDC settlement
• seller-issued checkout flows
• EIP-712 signed receipt quotes
• on-chain payment receipts
• off-chain metadata commitments
• event-driven indexing

This gives zkReveal a practical base before adding heavier cryptographic features.

The "zk" in zkReveal represents the future direction: selective disclosure, private verification, and privacy-preserving commerce flows — not a claim that the current MVP already uses ZK proofs.

zkReveal starts with a simple primitive:

payment → settlement → on-chain receipt

From there, the protocol may expand into a broader programmable commerce layer.

Future directions include:

• selective disclosure receipts — prove specific payment, access, or fulfillment facts without exposing all underlying metadata
• privacy-preserving checkout — reduce unnecessary exposure of buyer, seller, product, or purchase context
• encrypted delivery flows — support private delivery and reveal mechanisms for digital goods, credentials, files, gated content, and memberships
• buyer-verifiable reveal mechanisms — let buyers verify that a purchase is linked to a valid off-chain reveal or access process
• escrow-based settlement modes — add optional settlement flows where immediate payment is not enough
• agentic and Telegram-native commerce systems — allow bots and agents to create, request, verify, and act on payment receipts
• SDKs for apps and marketplaces — make receipt creation and verification easy to embed into other products
• cross-chain payment entry — allow buyers to pay from different chains or assets while sellers receive settlement in a preferred token
• stronger fulfillment guarantees — gradually move from simple proof-of-payment toward stronger delivery and access assurances

The current MVP intentionally avoids trying to solve every part of digital commerce at once.

Its goal is to create a reliable receipt and settlement foundation that future privacy, automation, delivery, and verification layers can build on.

zkReveal is designed for:

• creators selling private content
• sellers delivering credentials and access
• apps monetizing gated resources
• communities selling memberships
• marketplaces embedding crypto-native checkout
• agents purchasing digital resources

The first step is simple:

reliable on-chain receipts for digital payments.

Open an issue in the relevant repository or reach out through project channels as they become available.

Each repository contains its own license.