Imagine a payment messaging solution so elegant and secure it needs no database—where the payment is mathematically bound to the ISO Message, making them inseparable.

Payment Rail + Message Rail + Hook Enforcement
One Signature. 3-5s Finality.

Passwords (70s-80s) Antivirus (90s-00s) E2EE (00s-20s) Zero Persistent Knowledge ZPK™ (2026 →)

ZPK is an open protocol SDK for payment privacy. The engine remains ours.

Demo video coming soon

Four steps. No persistent data.

Your app calls the AIFS API. The engine handles the rest. The ShatterEngine never leaves the server.

01
Shatter

Your payload is dispersed into 1,024 entropic particles. The sender's wallet address is the XOR identity salt -- no separate key management required.

02
Anchor

A 24-character DNA cryptographic witness is generated from the particle set. This is the only artifact that travels on-ledger.

03
Settle

The anchor is submitted to Xahau with an XAH payment. The ZPK-Enforcer Hook validates the anchor format and enforces single-use replay protection.

04
Reassemble

The authorized party presents their wallet address and DNA anchor. The engine verifies identity and returns the original payload. No one else can.

Three API calls.

Shatter a payload, get a DNA anchor, submit it to Xahau with the ZPK-Enforcer Hook installed on your receiving address. That is the full integration.

Full SDK reference →
// 1. Shatter your payload const { dna } = await fetch('https://api.aifs.dev/v1/liquify', { method: 'POST', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ originAddress: senderWallet, receiverAddress: recipientWallet, metadata: payload }) }).then(r => r.json()); // 2. Submit to Xahau with DNA anchor const tx = { TransactionType: 'Payment', Destination: 'rHs7o2n6r6YaRkzhg7zZFa1VWwiEx84hKr', HookParameters: [{ HookParameter: { HookParameterName: '444E41', HookParameterValue: Buffer.from(dna).toString('hex').toUpperCase() } }] }; // 3. Reassemble (receiver side) const { payload } = await fetch('https://api.aifs.dev/v1/materialize', { method: 'POST', body: JSON.stringify({ dna, walletAddress: recipientWallet }) }).then(r => r.json());

The engine is the moat.

Your integration uses the open API. The ShatterEngine that produces the DNA anchor never leaves the AIFS server.

Privacy by design

No encryption keys to manage. No persistent identity linkage. The sender's wallet address is the cryptographic salt -- identity is bound to the math, not stored anywhere.

Onchain enforcement

The ZPK-Enforcer Hook on Xahau validates every anchor format and enforces single-use replay protection at the ledger layer. Fabricated anchors are rejected before settlement.

ISO 20022 native

ZPK was designed around ISO 20022 financial messaging. Shatter a pacs.008 credit transfer, settle on Xahau, and deliver a formatted message receipt -- all in a single flow.

Engine agnostic

The ZPK protocol defines the interface, not the implementation. Any platform -- TipBots, payment apps, compliance tools -- can integrate via the API without touching the engine.

Replay protection

Every DNA anchor is single-use. The Hook writes the anchor to Xahau state on first settlement and rejects any duplicate submission. No double-settlement is possible.

Patent pending

ZPK Protocol is covered by pending US patent applications. The DNA anchor, engine signature, and Hook enforcement mechanism are protected IP of AIFS Protocol Inc.

Install the Hook on your receiving address.

The ZPK-Enforcer Hook is live on Xahau Mainnet. Install it from the public hook hash on any Xahau address using the Hooks Builder. Once installed, that address only accepts payments carrying a valid ZPK DNA anchor.

Hook integration guide →
Hook hash (Xahau Mainnet)
9D35CFCE2ACF4C59E15063AD09119AC4269EA1E11766F6A412D2B1443BDBBF6A
Gateway address: rHs7o2n6r6YaRkzhg7zZFa1VWwiEx84hKr
SetHook tx: 39249C41

Start building with ZPK.

Open API. Open spec. Proprietary engine.

SDK reference Protocol spec