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

zcash-faucet

v1.2.1

Published

Zcash testnet coins (TAZ) from your terminal: npx zcash-faucet <address>

Readme

Zcash testnet coins (TAZ), straight to your terminal.

npm node deps network uptime license

npx zcash-faucet utest1your_testnet_address...

One command, no account. Your machine mines a short proof-of-work, and TAZ arrives at your unified, Sapling or transparent testnet address.


✨ What it looks like

  ✔ Proof-of-work done (3,912 hashes in 13.8s, no account needed)

  ⓩ  0.1 TAZ on its way to utest17rnhex9h…2dd5rk

  txid      ab12cd34…
  explorer  https://testnet.zcashexplorer.app/transactions/ab12cd34…

  Arrives after ~1 block (75s). Done testing? Give it back: npx zcash-faucet --donate

🚀 Usage

npx zcash-faucet <testnet-address>    # request TAZ (mines ~10-60s, no account)
npx zcash-faucet <address> --github   # skip mining: sign in with GitHub instead
npx zcash-faucet --status             # health, balance, drip size, recent drips
npx zcash-faucet --donate             # where to send leftover TAZ

| Option | What it does | | --- | --- | | --github | Sign in with GitHub instead of mining. No permissions requested; the login is revoked right after the check | | --faucet <url> | Use another zcash-faucet server, such as your local regtest one (or set ZCASH_FAUCET_URL) | | NO_COLOR=1 | Turn off colors |

Accepted addresses: utest1… (unified), ztestsapling1… (Sapling), tm… (transparent), textest1… (TEX). Mainnet addresses are rejected before anything is sent.

Needs Node 24.7+ for proof-of-work (it uses Node's built-in Argon2id). On older Node, --github and --status still work.

🛡 Why this faucet stays up

Most Zcash faucets died from bots draining them. This one is built so that doesn't happen:

| Problem | What zcash-faucet does | | --- | --- | | Bots drain the wallet | Argon2id proof-of-work, no account needed. It's memory-hard (19 MiB per hash), so GPUs and bot farms gain little over a laptop. Each proof is signed for one address, pays once, and gets harder when claims spike. One claim per address every 24h. | | Identity shouldn't be required | No login by default. --github is an optional fast lane: no scopes, token revoked right after the check. | | Per-IP limits block whole classrooms | No IP limits. 40 students on one campus Wi-Fi can all claim. | | Big payouts empty it fast | Modest drips (0.1 TAZ) and a global daily cap. | | Nobody notices when it breaks | Public status page plus a GitHub Actions monitor every 5 minutes that opens an issue on outage or low balance. | | It runs dry | npx zcash-faucet --donate prints the address to send leftovers back to. |

🧠 How it works

  npx zcash-faucet utest1…
          │
          │ 1. mine an Argon2id proof for a signed, single-use challenge
          ▼
  ┌──────────────────────┐   POST /api/claim     ┌───────────────────────────┐
  │  CLI (this package)  │ ────────────────────▶ │  faucet server (Node)     │
  │  zero dependencies   │ ◀── txid ──────────── │  • verifies the proof     │
  └──────────────────────┘                       │  • cooldown + daily cap   │
                                                 │  • one send at a time     │
                                                 └────────────┬──────────────┘
                                                              │ zcash-devtool wallet send
                                                              ▼
                                                 ┌───────────────────────────┐
                                                 │ lightwalletd              │
                                                 │ (testnet.zec.rocks)       │──▶ Zcash testnet
                                                 └───────────────────────────┘

The server wraps zcash-devtool, the Zcash team's developer wallet, which talks to a public lightwalletd. No full node to sync or babysit. The server is one file using only the Node standard library.

📊 Status & donations

  • Live status page: https://zcash-faucet.vercel.app (or npx zcash-faucet --status)
  • JSON for your own dashboards: GET /api/status
  • Done testing? Send leftover TAZ back: npx zcash-faucet --donate

👛 Don't have a testnet address yet?

  • zcash-devtool: wallet init … -n test, then wallet list-addresses (see its walkthrough)
  • zingo-cli: start it with --chain testnet, then run addresses
  • Zallet / zcashd on testnet: z_getnewaccount → z_getaddressforaccount

🧪 Local regtest

Don't want to depend on anyone's faucet, including this one? Run the same server against your own regtest network with AUTH=none. See deploy/regtest.md.

🏗 Run your own faucet

# on any Linux box with Docker and a public IP
git clone https://github.com/anukulpandey/zcash-faucet && cd zcash-faucet/deploy
DOMAIN=$(curl -s ifconfig.me).sslip.io docker compose up -d
docker compose logs faucet   # prints the faucet address: fund it with TAZ

On Google Cloud's free tier, one command creates the VM, static IP and firewall: PROJECT=<id> sh deploy/gcp.sh

  1. Optional --github fast lane: create a GitHub OAuth App (Settings → Developer settings → OAuth Apps), tick "Enable Device Flow", and set GITHUB_CLIENT_ID + GITHUB_CLIENT_SECRET.
  2. Caddy gets a TLS certificate automatically. sslip.io gives you a free hostname for your IP.
  3. Back up the seed: docker compose exec faucet zcash-devtool wallet -w /data/wallet display-mnemonic --enable -i /data/identity.txt

| Env var | Default | Meaning | | --- | --- | --- | | POW_DIFFICULTY | 12 | Base proof-of-work bits (~4k Argon2id hashes); +1 per doubling past 10 claims/hour | | POW_SECRET | random | Signs challenges; set it so challenges survive a restart | | GITHUB_CLIENT_ID | (unset) | Optional: enables --github | | GITHUB_CLIENT_SECRET | (unset) | Required with the ID: lets the server verify and revoke each login token | | DRIP_ZAT | 10000000 | Payout per claim (0.1 TAZ) | | DAILY_CAP_ZAT | 500000000 | Max paid out per 24h (5 TAZ) | | COOLDOWN_HOURS | 24 | Per address (and per GitHub account with --github) | | MIN_GITHUB_AGE_DAYS | 30 | Reject newer GitHub accounts | | NETWORK / LWD_SERVER | test / zecrocks | regtest + host:port for local | | AUTH | pow | none for local regtest only |

🛠 Development

npm test                       # CLI + server end to end, with a fake wallet binary
node bin/zcash-faucet.js --help

Publishing: npm login once, then npm version patch && npm publish && git push --follow-tags.

🔒 Security & privacy

By default there is no login at all. The CLI mines an Argon2id proof-of-work; the server sees only the address you ask it to pay.

With --github (optional), the login only replaces mining. Here is exactly what happens:

  1. The CLI runs GitHub's device flow for the faucet's own OAuth app, requesting no scopes. A no-scope token can only read public profile data: no repos, no email, no private anything. GitHub shows you this on the approval screen.
  2. The CLI never reads any existing credential (not gh, git or your browser), and never writes the token to disk. It lives in memory for one request. (v1.0.0 cached it; v1.1.0+ deletes that old file on every run.)
  3. The server first asks GitHub whether the token belongs to this faucet's app and carries no scopes. Any other token is refused without being used.
  4. It reads your public user ID and account creation date (GET /user), then immediately revokes the token through GitHub's API, so it can never be reused, even by whoever runs the server.
  5. Only your numeric GitHub ID and the claim time are stored, for the 24h cooldown.

The whole flow is about 40 lines: githubLogin in the CLI and githubUser / revoke on the server, with a test in test/github-auth.test.js. You can also revoke the app any time at github.com/settings/applications. Found a problem? Please open an issue.

⚠️ Testnet only

TAZ has no monetary value. Never send it to a mainnet address, and never reuse a testnet key for real funds.

MIT © anukulpandey · built on zcash-devtool and zec.rocks