@frontiercompute/zap1-core

v0 - implementation in progress.

Shared helpers for ZAP1 receipt submission, payload hashing, and wallet-hash derivation without venue-specific bindings.

install

npm install @frontiercompute/zap1-core

use

import {
  createClient,
  deriveEphemeralWalletHash,
  submitTradeReceipt,
} from "@frontiercompute/zap1-core";

const client = await createClient();
const walletHash = await deriveEphemeralWalletHash({
  venue: "hyperliquid",
  symbol: "BTC",
  side: "long",
  qty: 0.001,
});

const receipt = await submitTradeReceipt(
  {
    venue: "hyperliquid",
    symbol: "BTC",
    side: "long",
    qty: 0.001,
    entry_price: 100000,
    exit_price: 100100,
    pnl_bps: 10,
    wallet_hash: walletHash,
    metadata: { agent_id: "agent_a", strategy_id: "my_strategy" },
  },
  { apiKey: process.env.ZAP1_API_KEY },
);

console.log(client, receipt.leaf_hash, receipt.verify_url);

what you get

• trial-key bootstrap when ZAP1_API_KEY is absent
• deterministic contract-hash generation for trade and x402 receipt payloads
• ephemeral wallet-hash derivation keyed to the intent payload, not a persistent account identifier
• shared primitives over @frontiercompute/zap1-attest for venue adapters

runbook

1. point ZAP1_BASE_URL at your zap1 gateway only when you are not using the default https://api.frontiercompute.cash
2. provide ZAP1_API_KEY for persistent workloads; omit it only for short-lived evaluation flows
3. derive wallet_hash per intent by default; do not reuse one customer identifier across unrelated flows
4. submit the receipt with submitTradeReceipt() or submitX402Receipt()
5. verify the returned leaf_hash at GET /verify/{leaf_hash}/check

verifier endpoint

GET https://api.frontiercompute.cash/verify/{leaf_hash}/check

spec

docs: https://api.frontiercompute.cash/docs/

openapi: https://api.frontiercompute.cash/openapi/zap1.yaml

license

MIT