System Architecture

ZK ONE architecture combines decentralized identity, verifiable computation, and modular permissioning. Below a concise but technical architecture overview.

High-Level Architecture

flowchart TB
    A[Next.js Frontend<br/>Shadcn UI] --> B[Client Crypto Layer<br/>WASM ZK Engine]
    B --> C[Lisk L2 Smart Contracts]
    C --> D[Identity Registry]
    C --> E[Verification Contract]
    C --> F[Access Controller]
    C --> G[Event Logs / Indexer]
    G --> H[Third-Party Verifiers]

Architectural Layers

Frontend Layer (Next.js + Shadcn)

Responsible for:

• ZK proof generation (WASM)

• local hashing

• session-less client operations

• declarative access UI

Client Crypto Layer

• zkSNARK prover (Groth16 / Plonk)

• poseidon hashing for circuits

• AES-256-GCM for local encryption

• canonical document normalization

Smart Contract Layer (Lisk L2)

Contracts:

• IdentityContract – stores identity hashes + verification flags

• VerificationContract – validates zk-proofs

• AccessController – bitmask + revocation + expiry logic

4. Off-Chain Indexing

Used for:

• activity logs

• attestation tracking

• third-party verifier dashboards

State Architecture

classDiagram
    class IdentityContract {
      +mapping(address => IdentityRecord) identities
      +createIdentity()
      +verifyIdentity()
    }

    class AccessController {
      +mapping(address => Permission) perms
      +grant()
      +revoke()
      +checkAccess()
    }

    class VerificationContract {
      +verifyProof(proof, pubSignals)
    }

    IdentityContract --> AccessController
    VerificationContract --> IdentityContract

Data Processing Pipeline

sequenceDiagram
    participant U as User
    participant FE as Frontend
    participant CP as Crypto Layer
    participant SC as Smart Contracts
    participant V as Verifier

    U->>FE: Upload Document
    FE->>CP: Normalize + Hash
    CP->>CP: Generate zk-Proof
    CP->>SC: Submit (hash + proof)
    SC->>SC: Validate Proof
    SC->>V: Emit Verification Event

Access Control Architecture

flowchart LR
    A[User/Third Party] --> B[AccessController Contract]
    B --> C{Permissions Mask OK?}
    C -- no --> D[DENY]
    C -- yes --> E{Revocation/Expiry?}
    E -- expired --> D
    E -- valid --> F[ALLOW]

Security Architecture (Condensed)

flowchart TB
    A[Client Security<br/>Hashing / ZK / AES] --> B[Smart Contract Security<br/>Immutability + ZK Validation]
    B --> C[Permission Security<br/>Bitmask + Revocation]
    C --> D[Network Security<br/>Wallet / RPC]
    D --> E[Data Privacy<br/>No raw data on-chain]