Event & Proof Logging

Event & Proof Logging defines how ZKFund records what happened without recording what was done.

Instead of treating logs as a history of actions, ZKFund treats logs as cryptographic evidence of correctness.

This distinction is fundamental to preserving long-term privacy.

Why Traditional Event Logs Fail

Standard on-chain event logs are designed for transparency:

Even when values are masked, patterns accumulate over time.

For private funds, this turns logs into:

ZKFund deliberately rejects this model.

Proof-First Logging

ZKFund replaces traditional events with proof receipts.

A proof receipt is a minimal on-chain record that proves:

It does not describe the action itself.

Think of it as a cryptographic “pass/fail” record, not an activity log.

What Is Logged

Each proof receipt may include:

This is the minimum required to:

Nothing more is recorded.

What Is Never Logged

Proof logging explicitly avoids recording:

There is no transaction graph to analyze.

Verifiability Without Visibility

Anyone can:

No one can:

The system remains publicly verifiable but operationally opaque.

Log Isolation & Non-Correlation

Each proof receipt is:

Even repeated actions produce receipts that cannot be meaningfully correlated.

Support for Audit & Compliance

For audit purposes:

Logs do not need to be expanded to support audits.

Why Proof Logging Is Safer Than Redaction

Redacting logs still leaks structure. Proof logging never creates structure to redact.

There is no data accumulation risk. There is no future de-anonymization threat.

Last updated 2 months ago