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

@tonresistor/zkresistor-sdk

v1.0.2

Published

TypeScript SDK for ZKResistor, a trustless ZK privacy pool on TON. Builds messages, generates proofs, reads pool state.

Readme

@tonresistor/zkresistor-sdk

TypeScript SDK for ZKResistor, a trustless ZK privacy pool on TON. It builds the protocol messages, reads pool state, generates Merkle witnesses, and drives the deposit and withdraw flows. It is RPC-agnostic (you supply a small Client adapter) and prover-agnostic (snarkjs by default).

The SDK never signs or broadcasts. Every builder returns an { address, value, payload } triple for your own wallet integration.

  • Contracts: https://github.com/TONresistor/zk-resistor-contracts
  • App: https://zk.resistance.dog
  • License: MIT

Install

npm install @tonresistor/zkresistor-sdk @ton/core

@ton/core is a peer dependency.

Deposit

import {
  prepareDeposit,
  finalizeDeposit,
  createPoseidon2,
  createSnarkjsProver,
} from "@tonresistor/zkresistor-sdk";

const poseidon2 = createPoseidon2(hasherWasmBytes);
const insertProver = createSnarkjsProver({
  wasm: "/circuits/insert.wasm",
  zkey: "/circuits/insert_final.zkey",
});

// Phase 1 is instant and local. Show the note to the user before signing.
const prep = await prepareDeposit(client, {
  kind: "jetton",
  poolAddress,
  asset: "KITO",
  denomination: 1_000_000_000_000n,
  userAddress,
  userJettonWallet,
});
console.log("Save this note:", prep.noteString);

// Phase 2 generates the proof and builds the transaction.
const plan = await finalizeDeposit(client, { prep, poseidon2, insertProver });
await wallet.send(plan.message);

Withdraw

import {
  buildWithdraw,
  parseNote,
  createPoseidon2,
  createSnarkjsProver,
} from "@tonresistor/zkresistor-sdk";

const note = parseNote(savedNoteString);
if (!note) throw new Error("Invalid note");

const withdrawProver = createSnarkjsProver({
  wasm: "/circuits/withdraw.wasm",
  zkey: "/circuits/withdraw_final.zkey",
});

const plan = await buildWithdraw(client, {
  kind: note.asset === "TON" ? "ton" : "jetton",
  note,
  poolAddress,
  recipientAddress,
  poseidon2: createPoseidon2(hasherWasmBytes),
  withdrawProver,
});

await wallet.send(plan.message);

The recipient is bound to the proof by construction, so anyone can broadcast the resulting message. The transaction sender receives the fixed relayer reimbursement.

The Client interface

The SDK reads the chain through a small interface you implement once for your stack (tonutils-bridge, tonapi.io, ton-access, or a raw liteclient):

interface Client {
  getAccountState(address: string): Promise<AccountState>;
  runMethod(address: string, method: string, params: readonly RunMethodArg[]): Promise<RunMethodResult>;
  getTransactions(address: string, limit: number): Promise<GetTransactionsResult>;
}

The factory address is never hardcoded. Pass it explicitly to Factory.listPools and the other factory readers. The current deployment address is in the contracts repository.

Circuit artifacts

The SDK does not bundle the ZK artifacts. Three files are needed at runtime, hosted wherever you choose:

  • hasher.wasm, the Poseidon BLS12-381 witness calculator.
  • insert.wasm and insert_final.zkey, the Merkle insertion circuit.
  • withdraw.wasm and withdraw_final.zkey, the withdraw membership circuit.

Sources and build scripts are in the contracts repository under circuits/. In a browser, run the prover in a Web Worker so proof generation does not block the main thread.

The current trusted setup is a solo Powers-of-Tau. A multi-party ceremony is planned.

License

MIT, see LICENSE.