ZK-AI™
Protocol and organization identifier for ZK-AI proof infrastructure, specifications, and public program materials.
Legal notice
Legal and Trademarks
Public notice for claimed marks, open ZK-SNAP interop, and protocol governance boundaries on zk-ai.org. This summary is not legal advice, is not an investment, and is not a token sale.
Trademarks
Claimed Marks and License Position
ZK-AI™, ZKAI™, ZK-AI 3DVC™, 3DVC™, and ZK-AI VTL™ are trademarks of ZK-AI. All rights reserved.
This notice summarizes repository policy and protocol framing. It does not grant operator certification, trademark license, or commercial rights by browsing or using reference tools.
This site and repository do not grant any license to use the marks above. Internal use by authorized operators or partners may be permitted only under written agreement. External use — marketing, product interfaces, packaging, distribution, or app-store listings — requires explicit approval from the mark owner.
Marks identify ZK-AI protocol programs and display systems. In human-facing materials they modify a generic noun (for example, ZK-AI™ receipts), not verbs or standalone product names. Marks must not be inserted into protocol identifiers: JSON keys, schemas, URIs, receipt preimages, and cryptographic material remain unmarked.
ZKAI™
Compact trust-state prefix used with ZK-AI VTL™ (for example ZKAI™·S4). Identifies rendered Sigil outcomes, not a separate protocol layer.
ZK-AI 3DVC™
Three-Dimensional Verification certification program mark. Denotes independent assessment against Validity, Transparency, Finality, and the Context gate — not self-declaration.
3DVC™
Short form of the ZK-AI 3DVC™ program mark. Display is governed by the 3DVC Mark Program Policy and License Agreement.
ZK-AI VTL™
Visual Trust Language — the deterministic Sigil display system for verifier outcomes S0 through S6. Adjacent to, and separate from, the 3DVC™ program mark.
3DVC™ program mark
Display Rules for the Certification Mark
Commercial and operational use of 3DVC™ is governed by the 3DVC Mark Program Policy and 3DVC Mark License Agreement. Technical eligibility is defined in the ZK-AI 3DVC Mark & Triangulated Security Specification.
Verifier-gated display
The 3DVC™ mark MUST NOT be shown unless the verifier returns status = 3DVC_OK per the ZK-AI 3DVC Mark & Triangulated Security Specification. It is a program mark, not a decorative status.
Adjacent to the Sigil
3DVC™ MUST render adjacent to the ZK-AI VTL™ Sigil and MUST NOT appear inside the Sigil glyph. Sigils remain computable by any conforming verifier; 3DVC™ requires program qualification.
Recorded artifacts only
3DVC™ MUST NOT be displayed for artifacts that are valid offline but lack the recognition, transparency, and finality evidence the program requires. Offline-valid receipts may show Sigils without the program mark.
Open specification
ZK-SNAP — Protocol Identifier, Not a Proprietary Mark
The receipt kernel, schemas, goldens, and public interchange format — the open interoperability surface, not a proprietary trademark.
ZK-SNAP names the receipt kernel, schemas, goldens, and public interchange format intended for open publication and interoperable implementation. It is reserved for the open interoperability path and is not listed as a proprietary trademark in public materials. Baseline conformance is exercised through shared goldens and the open TCK; 3DVC™ certification and ZK-AI VTL™ display marks remain governed program layers above receipt interop.
Normative receipt bytes
Published specification, JSON schemas, and shared goldens define the ZK-SNAP receipt object independent of any single operator implementation.
Open TCK baseline
The open TCK baseline suite exercises implementations against shared artifacts. Conformance at this layer does not require entry into the 3DVC™ operator program.
Independent mint and verify
Any party may mint and verify ZK-SNAP receipts against the published kernel. Sigils render through ZK-AI VTL™; 3DVC™ remains a separate certification mark for qualified operators.
Governed witness layers
ZK-AI Chain recognition, Evidence Graph discovery, and program marks are governed protocol layers on top of open receipt validity — not substitutes for it.
Protocol governance
Authority, Roles, and Release Boundaries
ZK-AI separates receipt proof (ZK-SNAP), ledger witness (ZK-AI Chain), discovery (Evidence Graph), and program marks (Sigils, 3DVC™). Root governance authorizes protocol meta-rules through visible chain events. It does not sign individual ZK-SNAP receipts or bless specific proofs.
Validators witness ordering. Operators emit receipts near execution and submit batches. Verifiers check cryptography with or without chain recognition. Proof generation does not confer consensus authority over ledger rules.
Role separation
Governance sets ledger rules. Validators witness ordering. Operators emit receipts and submit batches. Verifiers check cryptography.
Visible changes
Rule changes are meant to be chain-visible — not edited through opaque dashboards.
Proof ≠ authority
Generating receipts or proving demand does not grant control over chain rules.
Visible rule changes
Governance decisions become chain-visible events and are mirrored publicly. The ledger rules are not edited through opaque dashboards.
Proof ≠ consensus weight
Generating receipts and proving demand does not grant authority over chain rules. Validators sign ordering; verifiers check cryptography.
Open kernel, governed witness
ZK-SNAP interop is the open floor. Public recognition on ZK-AI Chain and program marks are governed layers above it.
Built for the long run
Protocol economics are usage-metered with a supply floor and recycle path — designed so metering and settlement can keep operating as demand scales, not as a one-time launch event.
Release stage
Pre-Testnet Assurances
The network is pre-testnet. Controlled private testnet will exercise anchor and metering mechanics under protocol rules; public mainnet settlement follows operator, validator, economics, and hardening gates — not a fixed public calendar. See Network — Governance.
Use of zk-ai.org, Proof Lab, or support contributions does not grant governance rights, validator priority, tokens, operator status, or 3DVC™ certification. Contact for protocol, operator, or research correspondence.
Disclaimers
Limitations of Public Materials
The following boundaries apply to visitors, implementers, and contributors. They do not modify normative protocol specifications in the repository.
No legal or investment advice
Materials on zk-ai.org are protocol documentation and reference tooling. They are not legal, tax, or investment advice. Use of this site is not an investment and does not purchase governance, validator, or commercial rights.
No token or securities offer
Public copy is not a token sale, securities offering, or grant of revenue participation. Network economics and settlement assurances remain staged until published release gates complete.
No default IP license
Unless otherwise stated, specifications and documentation in the ZK-AI repository are proprietary. No trademark, copyright, operator, or certification license is granted by browsing, cloning, or running reference tools.
Reference tooling scope
Proof Lab demonstrates local ZK-SNAP verification with a dedicated demo signing key. It does not certify an operator, award 3DVC™, or imply DoT-5 chain recognition without the full recognition path.
ZK-AI publishes specifications and reference implementations subject to change-controlled revision. Nothing on this page creates a client relationship, investment solicitation, or trademark license. Correspondence via the contact form.
Support contributions fund public protocol work; they do not purchase tokens, governance weight, validator priority, revenue share, or commercial licenses. See Contact.
Protocol vocabulary
Canonical Glossary
Public definitions for ZK-AI, ZK-SNAP, dePoD, DoT, Sigils, and related protocol terms. When a definition says “not X”, that exclusion is normative in the specs.
Open the full glossary index (13 terms, each with its own reference page).