Use cases

Any payload. Any wallet. Two functions. Here is what developers are building with ZPK.

Medical records

Doctor shatters a lab result. Only the patient's wallet can materialize it. Nothing readable on any server.

Legal contracts

Lawyer shatters a draft. Only the named counterparty can read it. Proof of delivery is the DNA anchor onchain.

Payroll

HR shatters salary data. Each employee's wallet sees only their own number. No shared database of compensation.

ISO 20022 payments

Payment message shattered before transmission. Receiver materializes. SWIFT-grade privacy on any rail.

M&A due diligence

Shatter the data room. Receiver wallet is the acquiring party only. Expires the moment the deal closes.

NFT metadata

Shatter the token URI so only the proven owner can read the actual asset. No public metadata exposure.

Permanent file storage

Shatter any file before it touches Arweave. 200-year storage. Zero liability. Only your wallet retrieves it.

AI session context

Shatter conversation state between sessions. No persistent memory on any server. Compliance by architecture.

Whistleblower submissions

Shatter the document. DNA anchor is the receipt. No server ever holds the readable content.

Try it now

Live demo running against the real ZPK API. No account. No setup.

Step 1 - Type anything

DNA anchor

Step 2 - Your DNA anchor (onchain proof)

Waiting for shatter...

Reassembled

Step 3 - Original payload (unscrambled locally, never on server)

Waiting for materialize...

The code that just ran

// One script tag. Two functions.
<script src="https://zpkpay.com/zpk.js"></script>

const dna = await zpk.shatter(payload, walletAddress);
const original = await zpk.materialize(dna, walletAddress);
                