Quickstart

This sends USDC through the protected-transfer contract with the poisoning firewall running by default. If the recipient looks like a poisoning lookalike or has baited you with a zero-value transfer, the send is refused before any funds move.

A config encodes your integrator behaviour (recall window, claim mode, optional fee). It is content-addressed, so calling it on every boot is free.

import { defineConfig, registerConfig } from '@ctrl-arcz/sdk';

const { configId } = await registerConfig(clients, defineConfig({ recallWindow: 3600 }));

Create a claim secret

The recipient will claim with a short code; the salt is the entropy that keeps the 6-digit code safe from brute force.

import { generateClaimCode } from '@ctrl-arcz/sdk';

const secret = generateClaimCode(); // { code, salt, claimHash }

Send, protected

sendProtected runs the firewall itself and throws RiskBlockedError on a block before it submits. No funds move on a block.

import { approveUsdc, sendProtected, parseUsdc } from '@ctrl-arcz/sdk';

const amount = parseUsdc('5'); // 5 USDC, 6 decimals
await approveUsdc(clients, amount);

const { transferId, txHash } = await sendProtected(clients, {
  configId,
  to: recipient,
  amount,
  claimHash: secret.claimHash,
});

Deliver the code to the recipient through your normal channel with them. The protection is that a wrong or poisoned recipient cannot claim without it, and you can cancel to reclaim.

Recipient claims

import { claim } from '@ctrl-arcz/sdk';

await claim(recipientClients, transferId, secret.code, secret.salt);

What just happened

Layer 1 — firewall

sendProtected scanned the recipient and would have refused a lookalike or bait address. See the firewall guide.

Layer 2 — escrow

Funds were held by the contract, claimable only with the code, refundable to you. See protected transfer.

Payer privacy

To also hide your wallet from the recipient, use Private Pay.

Installation Private Pay

Get started

Integrate the SDK

Concepts

Reference

What just happened

Layer 1 — firewall

Layer 2 — escrow

Payer privacy

​What just happened

Layer 1 — firewall

Layer 2 — escrow

Payer privacy

What just happened