npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@quittance/server

v0.1.3

Published

Quittance seller-side SDK: spec-compliant x402 with on-chain Exec-Pay-Deliver atomicity

Downloads

53

Readme

@quittance/server

Seller-side SDK for Quittance — spec-compliant x402 with on-chain Exec-Pay-Deliver atomicity on Kite.

Turn any HTTP service into a bonded, verifiable x402 seller in under 10 lines. The SDK handles the full protocol: 402 negotiation, escrow opening, oracle proof, quittance post, and escrow release. You write the delivery logic. That's it.

npm install @quittance/server

Quick start

import { createSellerServer } from "@quittance/server";
import { Resend } from "resend";

const resend = new Resend(process.env.RESEND_API_KEY!);

createSellerServer<{ to: string; subject?: string; body?: string }>({
  agentName: "email.kite",
  price: "1000",              // 0.001 USDC (6 decimals)
  deadlineSeconds: 300,

  async deliver({ to, subject = "Delivery", body = "" }) {
    const { data, error } = await resend.emails.send({
      from: "[email protected]",
      to, subject, html: body,
    });
    if (error) throw new Error(error.message);
    return `email:${to}:${data?.id}`;
  },
}).listen(4002, "0.0.0.0");

On every incoming request the SDK:

  1. Round 1 — returns a spec-compliant HTTP 402 with the Quittance escrow address, proof type, and deadline embedded in extra.quittance.
  2. Round 2 — verifies the X-PAYMENT header, checks the buyer's on-chain allowance, opens escrow, calls your deliver() function, has the oracle sign the result hash, posts the quittance to QuittanceRegistry, and triggers escrow auto-release — all before returning 200.

Configuration

createSellerServer({
  // Required
  agentName:    string,             // name shown in the marketplace registry
  price:        bigint | string,    // settlement-token base units (e.g. "1000" = 0.001 USDC)
  deliver:      async (payload, meta) => string,  // your service — return a result string

  // Optional
  deadlineSeconds?:      number,    // default: 300
  minBondTier?:          "bronze" | "silver" | "gold",  // default: "bronze"
  parseBody?:            (raw) => TPayload,  // shape the incoming request body

  // Settlement backend (default: "onchain")
  settlement?:           "onchain" | { type: "facilitator"; url: string },

  // Demo slash story — opens escrow then intentionally skips delivery
  cheapMode?:            boolean,
  cheapFailRate?:        number,    // 0–1, default: 0.8
  cheapDeadlineSeconds?: number,    // default: 60
})

Settlement backends

| Mode | How it works | When to use | |---|---|---| | "onchain" (default) | Seller calls openEscrow + QuittanceRegistry.post() directly. No facilitator dependency. | Now — works regardless of facilitator status. | | { type: "facilitator", url } | Routes through Pieverse /v2/verify + /v2/settle. Automatically falls back to on-chain if the facilitator returns non-200. | When Pieverse is available. |

Both paths produce identical on-chain artefacts (EscrowOpened, QuittancePosted, EscrowReleased). Switching is one config line — no buyer-side changes required.


Environment variables

| Variable | Required | Description | |---|---|---| | KITE_RPC_URL | | Kite RPC endpoint. Default: https://rpc.gokite.ai | | KITE_BUNDLER_URL | | ERC-4337 bundler. Default: Kite bundler | | USDC_ADDRESS | ✓ | Settlement token contract address | | ESCROW_ADDRESS | ✓ | Quittance Escrow contract address | | REGISTRY_ADDRESS | ✓ | QuittanceRegistry contract address | | BOND_ADDRESS | ✓ | Bond contract address | | ORACLE_PRIVATE_KEY | ✓ | Oracle EOA private key (signs delivery proofs) | | SELLER_EMAIL_PRIVATE_KEY | ✓ | Seller EOA private key (submits UserOps) | | TOKEN_DECIMALS | | Default: 6 (USDC on mainnet) |


Protocol

Quittance implements Exec-Pay-Deliver atomicity for x402:

  • Buyer funds are escrowed on-chain before delivery begins.
  • Seller delivers, then posts a cryptographic proof (oracle signature, adaptor-sig, threshold, TEE, zkTLS, or timeout).
  • QuittanceRegistry verifies the proof and releases escrow to the seller atomically.
  • If no proof is posted by deadline, anyone can call refund() — buyer gets USDC back, seller's bond is slashed.

Contracts on Kite Mainnet (chainId 2366) — see quittance.xyz for deployed addresses.


Links