The Trade.

packages you'll see in `node_modules`

• @kashscript/trade-sdkrequired

  Hydrator, contracts, deploy ceremony, EIP-712 signal layer.

• @kashscript/tradeoptional

  High-level wrappers + Trust-Score logic (opinionated defaults).

• @kashscript/identity-coretransitive

  Signer interfaces — already pulled in by every Kash package.

• @kashscript/lexiconstransitive

  `kash.trade.*` envelope shapes for off-chain records.

peer dependencies · install in your project

• viem@^2.21.0All chain interaction (PublicClient, WalletClient, ABI encoding) is via viem.required
• zod@^3.23.8Manifest hydration validates with strict Zod schemas.required

outside npm · what else you need

• Foundry (`forge`)

  Only required if you compile contracts yourself OR run `kash trade forge-deploy` to install the suite on a new chain. Pre-built artifacts ship in the npm tarball.

  curl -L https://foundry.paradigm.xyz | bash && foundryup

• An L2 JSON-RPC endpoint

  Read + write paths both need an RPC URL. Public fallbacks ship for Base, Optimism, Arbitrum, Polygon, Ethereum mainnet/sepolia — use Alchemy/Infura/QuickNode for production.

  # pick a provider — Alchemy free tier is enough for dev

framework wiring

// app/actions/deploy-trade.ts
"use server";
import { TradeManager } from "@kashscript/trade-sdk/core";
import { createPublicClient, createWalletClient, http } from "viem";
import { privateKeyToAccount } from "viem/accounts";
import { base } from "viem/chains";

export async function deployTrade(manifest, overlay) {
  const account = privateKeyToAccount(process.env.DEPLOYER_KEY as `0x${string}`);
  const wallet  = createWalletClient({ account, chain: base, transport: http(process.env.RPC_URL!) });
  const pub     = createPublicClient({ chain: base, transport: http(process.env.RPC_URL!) });

  const manager = new TradeManager({
    publicClient:   pub,
    walletClient:   wallet,
    chainId:        base.id,
    factoryAddress: process.env.TRADE_FACTORY as `0x${string}`,
  });
  return await manager.deploy({ manifest, overlay });
}

# CLI route (recommended for ops)
kash trade forge-deploy --chain 8453 --key 0x...          # install the suite
kash trade deploy --manifest ./otdc.json --chain 8453 --factory 0x...

# Programmatic route
import { TradeManager } from "@kashscript/trade-sdk/core";
const trade = await manager.deploy({ manifest, overlay });

import { TradeForge, OTDCTrade } from "@kashscript/trade-sdk/contracts";
const factory = await viem.deployContract({ abi: TradeForge.abi, bytecode: TradeForge.bytecode, args: [owner] });
await factory.write.setImplementation([0, otdcImpl]);

troubleshooting · the support inbox

• ▸ `ArtifactsNotBuiltError: Trade-SDK contract artifacts not built` at runtime.

  You're importing from `@kashscript/trade-sdk/contracts` against a dev tarball that wasn't compiled. Run `bun run forge:build && bun run artifacts:gen` in the trade-sdk package, OR install the official published version which ships with bytecode populated.

• ▸ `Deployed address X != predicted Y — manifest tampering detected`.

  Something between hydration and on-chain submission rewrote the manifest. Most common cause: the `_onchain` overlay addresses don't match the manifest's anchors. Re-derive the overlay from the same source-of-truth as the manifest.

• ▸ `no RPC URL available for chain X`.

  The chain ID isn't in the public-fallback table. Pass `--rpc <url>` or set `KASH_RPC_URL`. For supported public fallbacks, see `packages/trade-sdk/src/cli/util/client.ts`.

• ▸ EIP-712 signal verification fails on-chain (`InvalidSigner`).

  Re-check the domain separator — the chain ID and verifying-contract address are part of the EIP-712 domain. A signature minted against a different clone (or a different chain) will never verify, by design.

• ▸ Tx reverts with `MoneyLockViolation`.

  Your transfer attempted to route more than the locked principal. The Money-Lock invariant (Phase-7-A formal verification) prohibits any path that nets withdrawal > deposit. Check your BPS recipients sum to ≤ 10_000.

• ▸ `kash trade forge-deploy` fails on Windows.

  Foundry's Windows binary is experimental. Use WSL or run the deploy from a Linux CI runner. Native Windows support is on Foundry's roadmap, not ours.