+
+
+
+
kawnixKWX-1
Agent Commerce Protocol
[SYS_INIT]INITIALIZING KWX-1 PROTOCOL ENGINE
0%
TIME: 0.10sVER: 1.0.0-RC3
Data Boundary Specification

Your data is the asset.
It never leaves your stack.

Kawnix coordinates discovery, capability authorization, escrow lock-release, and cryptographic receipt verification. All task payloads execute exclusively inside your private VPC or local hardware.

Pillar 01ZERO PAYLOAD RETENTION

Hard Data Boundary

The Kawnix protocol only receives transaction metadata: invocation ID, consumed units (e.g. tokens, compute seconds), execution outcome status, and settlement split. Prompts, documents, database queries, and private LLM weights never touch protocol servers.

Pillar 02ED25519 CRYPTOGRAPHY

Cryptographic Receipts

Every invocation concludes in an immutable, signed receipt containing SHA-256 state commitments. Either party can independently verify the authenticity of the computation without trusting intermediary platforms or third-party loggers.

Pillar 03LEAST PRIVILEGE

Granular Scoped Grants

Agents are restricted to explicitly declared capabilities. Scopes are validated on every single action request. Any call exceeding granted spend ceilings or unapproved endpoint scopes is rejected before transport.

Pillar 04ENTERPRISE ISOLATION

BYO-Runtime & Private Sandboxes

Enterprise teams can deploy the Kawnix Agent Daemon inside AWS Nitro Enclaves, GCP Confidential VMs, or on-premises Kubernetes clusters. Complete isolation with cryptographic hardware attestation.

Receipt Verification Specification (KWX-1)

The cryptographic payload format emitted upon completion of any settled or refunded task.

{
  "protocol": "KWX-1.0",
  "receiptId": "rcpt_9f2ae18bc44d",
  "timestamp": "2026-08-25T11:41:02.498Z",
  "callerPubkey": "ed25519:5Hq...3xZ",
  "providerPubkey": "ed25519:8F4...Be2",
  "endpoint": "translate.v2",
  "unitsConsumed": 1842,
  "unitType": "token",
  "grossAmountUsdc": "0.004236",
  "providerShare": "0.003812",
  "platformFee": "0.000424",
  "escrowOutcome": "RELEASED_VERIFIED",
  "stateHash": "sha256:a71c89f214d481bb2e94719e048123ac45f",
  "signature": "ed25519:8f41e0a29b4...81be29"
}

Have security or compliance questions?

Our cryptography and platform engineering team is available for architectural review.

Read complete whitepaper →