FAQ
What is ZKFund, in one sentence?
ZKFund is a protocol for running funds and treasuries on-chain where governance, execution, and settlement are enforceable and verifiable, but never publicly observable.
Is ZKFund a privacy mixer?
No.
ZKFund is not designed to obscure random transactions or provide anonymity as a standalone service. It is a governance and fund execution protocol where privacy is a structural requirement, not a user feature.
If everything is private, how can ZKFund be trusted?
ZKFund replaces transparency with cryptographic verifiability.
Anyone can verify that:
governance rules were followed
approvals met required thresholds
execution respected constraints
settlement was valid
What is hidden is who acted and what exactly moved—not whether the system behaved correctly.
Who controls the funds?
No single person or wallet controls the funds.
Control is distributed and enforced by:
ZK DAO governance
role-based permissions
ZK multisig execution
rule-bound settlement
Even fund creators cannot act unilaterally.
Can fund managers steal or drain funds?
No.
Fund managers:
cannot bypass governance
cannot exceed execution constraints
cannot move assets without approval proofs
Any unauthorized attempt simply fails at the protocol level.
How are LPs protected?
LPs are protected by:
anonymous onboarding
private share representation
governance-gated withdrawals
stealth settlement
LP identities, balances, and participation history are never public.
Can ZKFund be audited?
Yes, but not through data disclosure.
Audits are performed via:
proof receipts
verification of governance and execution rules
selective disclosure approved by governance
Auditors verify correctness, not transaction history.
Does ZKFund support compliance?
Yes.
ZKFund supports proof-based compliance, including:
proof of fund legitimacy
proof of rule adherence
selective disclosure for regulators
Compliance does not require exposing LP identities or treasury balances.
What happens if an execution fails?
If execution or settlement fails:
no assets move
no partial state is exposed
a failure proof is logged
Governance can then decide on corrective action.
Is ZKFund chain-specific?
No.
ZKFund is designed to be chain-agnostic and can operate across multiple blockchains without breaking its privacy model.
Each chain verifies only what it needs to.
Can ZKFund interact with external protocols?
Yes.
ZKFund can execute across:
DEXs
bridges
liquidity venues
external infrastructure
All interactions are mediated through ZK Pool to preserve privacy.
What information is public?
Publicly verifiable information includes:
protocol rules
proposal lifecycle states
proof validity
execution success or failure
No financial or identity data is public.
What information is never public?
ZKFund never exposes:
treasury addresses
balances or asset composition
LP identities
execution routes or timing
internal approvals
These are protected by design.
Is ZKFund censorship-resistant?
ZKFund minimizes censorship risk by:
removing reliance on public addresses
distributing authority
enforcing execution via proofs
However, it does not attempt to bypass base-layer chain rules.
Who is ZKFund for?
ZKFund is designed for:
institutional funds
OTC desks
DAO treasuries
private syndicates
serious on-chain capital
It is not designed for casual or fully permissionless usage.
What problem does ZKFund solve that existing DAOs don’t?
Existing DAOs assume transparency is safe.
ZKFund assumes transparency is an attack surface.
It allows organizations to operate on-chain without turning their behavior into public intelligence.
What is the core idea behind ZKFund?
That on public blockchains:
verifiability matters more than visibility
ZKFund is built entirely around that principle.
Last updated