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

safe-vanity-blockie

v1.0.0

Published

Brute-force a Safe saltNonce so the Safe address renders a two-color face as a blo identicon

Readme

safe-vanity-blockie

Brute-force a Safe deployment config (saltNonce) so the resulting Safe address renders a chosen two-color face when drawn by blo, the identicon library used by the Safe UI.

The address is counterfactual: mining only finds a config. The address exists deterministically whether or not the Safe is deployed, and on non-zkSync chains it is identical on every chain that has the canonical Safe contracts.

[!CAUTION] A matching identicon is cosmetic and must never be trusted as proof of an address. Blockie look-alikes are a known phishing vector: an attacker can mine a different address whose identicon looks the same to a human. Always verify the full address, never the picture.

[!NOTE] This is a personal side project, not an official Safe product. It is not built, reviewed, or supported by Safe, and it carries no bug bounty.

Install

Requires Node.js >= 22.

npx safe-vanity-blockie --help

Or install it:

npm install -g safe-vanity-blockie

Mine

safe-vanity-blockie --owners 0xAbC...,0xDeF... --rpc https://ethereum-rpc.publicnode.com

It scans saltNonce values across a pool of worker threads and keeps a leaderboard of the best matches. Run it until you like a result, then stop with Ctrl+C — the printed nextStart lets you resume where you left off.

| Option | Default | Meaning | | --- | --- | --- | | --owners <0x..,0x..> | required | comma-separated Safe owners | | --threshold <n> | 1 | signatures required | | --safe-version <v> | 1.5.0 | Safe contract version: 1.5.0, 1.4.1 or 1.3.0 | | --rpc <url> | required | used once, for chainId and canonical contract addresses | | --target <name\|file> | faces | builtin template (faces, or one expression), a comma-separated list of expressions (smile,open), or a FaceSpec JSON file | | --two-color / --no-two-color | on | only report blockies using exactly two colours | | --min-contrast <n> | 0 | drop results whose two colours are closer than this (0–442) | | --min-match <n> | 0 | drop results matching the face less closely than this (0–100%) | | --workers <n> | cores − 1 | worker threads | | --max-iterations <n> | unbounded | total nonces to scan | | --start <n> | 0 | first saltNonce; use the printed nextStart to resume | | --keep <n> | 20 | leaderboard size | | --out <file.json> | safe-vanity-blockie-<UTC>.json | machine-readable results; written even when the run is stopped with Ctrl+C | | --no-out | | do not write the results file | | --gallery <file.html> | | self-contained HTML gallery of real blo SVGs | | --l1-singleton | | force the L1 Safe singleton on an L2 chain |

Deploy

safe-vanity-blockie deploy --salt <n> --owners 0xAbC... --safe-version <v> --rpc <url>

Pass the same --safe-version the run was mined with: it is part of the address, and leaving it out deploys the default version's Safe, which is a different address. The deploy command a mining run prints always names it.

[!IMPORTANT] deploy needs a private key. Prefer the SAFE_VANITY_DEPLOYER_KEY environment variable over --pk: a key passed as a flag lands in your shell history and in the process list on a shared machine. The key signs the deployment transaction and is never written to disk or sent anywhere but the RPC endpoint you chose.

The command re-derives the address from your config and asks you to type yes before broadcasting. Pass --yes to skip that (always skipped when stdin is not a TTY).

Browser alternative

There is also a web app that mines in Web Workers and deploys with an injected wallet — no private key involved. See the project README.

Links

MIT