Skip to content
Menu

keyrx

Dev Tools

Is this your project? Claim and verify →

The keyRX CLI: Solana vanity address grinder. One seed, unlimited addresses, keys for every wallet. Offline. Open. Verified.

What HEY knows

Building
Last shipped 42 days agoActive: 0 meaningful events in 30 days; latest ship 42 days ago. Evidence Source

Build Momentum 20How it is measured

Latest ship
Code changes, week of 2026-09-14 – 2026-09-20 · 10 commits · · Code activity

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

Latest change
Derived13 days ago: 2 meaningful ships this month, 10 the month before. Evidence

HEY’s own reading

What this change is
What it names
HEY’s own reading names no capability.
Stage
HEY’s own reading of the record, not something the project shipped.
Reported by
HEY’s reading of the record. HEY’s own reading of the record: nothing to corroborate.
Release and deployment
Not a release or a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it 2026-10-13; HEY first knew on 2026-10-13.
Not known
  • No source HEY holds names what this change does.

Evidence: signal record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts keyrx on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me keyrx’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Published packages (not enough yet), Official docs (no source), API description (no source). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 7 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule's longer window: 4 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-14, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 10 commitskeyrx 0.4.25Code changes, week of 2026-09-07 – 2026-09-13 · at least 7 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source2 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · 10 commitskeyrx 0.4.25Code changes, week of 2026-09-07 – 2026-09-13 · at least 7 commits+3 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-09-14 – 2026-09-20 · 10 commits

Code activitySource linked

What changed, in the repository’s own words:

1 active day in keyrx/keyrx.

This week HEY looked inside 1 of 10 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:3ee2505a… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗ (opens in a new tab)

Shared change · Release

keyrx shipped keyrx 0.4.25.

Builder status: Active.

Dated 2026-09-14 by the sourceSource: GitHub

View evidence ↗Evidence receipt

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 2 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about keyrx — as of 26 Oct

Is keyrx still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 42 days ago. Evidence
What did keyrx ship last?
FactCode changes, week of 2026-09-14 – 2026-09-20 · 10 commits — Code activity, 42 days ago. Evidence
What does HEY not know about keyrx?
Unknown3 gaps: Published packages (not enough yet), Official docs (no source), API description (no source). Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. 3 releases in keyrx/keyrx on 14 Sep

    GitHub release

    Show all 3 releases

    1. keyrx 0.4.25

      GitHub releaseSource verified

      Make an official Linux/WSL prebuilt keyrx --update stop after the authenticated latest-release check when already current. It leaves the executable and shell profile untouched, and refreshes the start screen from the running binary. A newer release still takes the verified… Show all

      Make an official Linux/WSL prebuilt keyrx --update stop after the authenticated latest-release check when already current. It leaves the executable and shell profile untouched, and refreshes the start screen from the running binary. A newer release still takes the verified install path; rerunning the public one-line installer remains an explicit full repair/reinstall.

      View evidence: keyrx 0.4.25 (opens in a new tab)

    2. keyrx 0.4.24

      GitHub releaseSource verified

      Put both Linux/WSL prebuilt and locked Rust source install choices directly in the homepage DOWNLOAD panel, with a guided WSL setup pointer. Keep the Mac source path explicit and document Apple's Command Line Tools when its compiler or linker is missing. · Gate future release… Show all
      • Put both Linux/WSL prebuilt and locked Rust source install choices directly in the homepage DOWNLOAD panel, with a guided WSL setup pointer. Keep the Mac source path explicit and document Apple's Command Line Tools when its compiler or linker is missing.
      • Gate future release publication on hosted Apple silicon and Intel macOS source-install checks; no macOS binary is claimed or shipped.
      • On macOS, relaunch a held source-installed executable through a duplicated descriptor that survives exec, and keep the invalid-UTF-8 filename test honest on filesystems that refuse such a name before…
      View evidence: keyrx 0.4.24 (opens in a new tab)

    3. keyrx 0.4.23

      GitHub releaseSource verified

      The protected 0.4.22 tag stopped in read-only CI before publication. Make the installer's GitHub CLI test fixture hermetic on runners that have a real gh; 0.4.23 is the first release carrying the changes below. · Make the verified Linux/WSL one-command installer set up future… Show all
      • The protected 0.4.22 tag stopped in read-only CI before publication. Make the installer's GitHub CLI test fixture hermetic on runners that have a real gh; 0.4.23 is the first release carrying the changes below.
      • Make the verified Linux/WSL one-command installer set up future Bash shells as well as the current terminal, preserving system commands even when an earlier profile line replaced PATH. Refuse unsafe profile and install directories before download, and never execute a preexisting binary merely to read its version. Leave wallet records and unrelated tools untouched.
      • Let an…
      View evidence: keyrx 0.4.23 (opens in a new tab)

  2. Code changes, week of 2026-09-07 – 2026-09-13 · at least 7 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    12 active days in keyrx/keyrx.

    How HEY read this week

    This week HEY looked inside 1 of 7 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 7 commits (opens in a new tab)

  3. 2 releases in keyrx/keyrx on 13 Sep

    GitHub release

    Show all 2 releases

    1. keyrx 0.4.21

      GitHub releaseSource verified

      Keep the one-command Linux/WSL installer working when an older GitHub CLI is installed but lacks gh attestation verify. Treat that command as unavailable, name the checksum-only path explicitly, and still refuse when KEYRX_REQUIRE_ATTESTATION=1. A supported command that fails… Show all
      • Keep the one-command Linux/WSL installer working when an older GitHub CLI is installed but lacks gh attestation verify. Treat that command as unavailable, name the checksum-only path explicitly, and still refuse when KEYRX_REQUIRE_ATTESTATION=1. A supported command that fails verification remains a refusal; no CLI binary behavior changes.
      • Make keyrx.tech's Install panel show the one Linux/WSL command by default. Keep the archive and macOS source instructions behind install manual, and replace the oversized mobile release URL with a copyable install control.
      View evidence: keyrx 0.4.21 (opens in a new tab)

    2. keyrx 0.4.20

      GitHub releaseSource verified

      Add one real Linux x86-64 and WSL install command at The bounded installer refuses unsupported systems, downloads the exact versioned archive and checksum, verifies SHA-256 before extraction, verifies signed GitHub provenance when gh is present, installs only in the user's… Show all
      • Add one real Linux x86-64 and WSL install command at https://keyrx.tech/install.sh. The bounded installer refuses unsupported systems, downloads the exact versioned archive and checksum, verifies SHA-256 before extraction, verifies signed GitHub provenance when gh is present, installs only in the user's absolute Cargo bin root, checks the installed version, and runs keyrx verify.
      • Publish the installer as its own checksummed and signed-provenance release subject, then require keyrx.tech to serve those exact bytes at /install.sh. Keep the complete inspection-first manual path and…
      View evidence: keyrx 0.4.20 (opens in a new tab)

  4. keyrx 0.4.18

    GitHub releaseSource verified

    Add an attested, checksummed x86_64-unknown-linux-musl release archive so Linux and Windows WSL users can download and verify keyRX without first compiling its Rust dependency tree. Keep native Windows unsupported until its owner-only file guarantees exist, and keep macOS on the… Show all
    • Add an attested, checksummed x86_64-unknown-linux-musl release archive so Linux and Windows WSL users can download and verify keyRX without first compiling its Rust dependency tree. Keep native Windows unsupported until its owner-only file guarantees exist, and keep macOS on the source-build path until signed and notarized native archives can be tested honestly.
    • Make first-run guidance lead with the prebuilt archive and give source builders one complete official-rustup, Rust 1.85+, Cargo PATH, and cargo install --locked path. The official prebuilt now points --update users back…
    View evidence: keyrx 0.4.18 (opens in a new tab)

  5. keyrx 0.4.17

    GitHub releaseSource verified

    After a successful default grind, print the exact copy-ready keyrx show command for every Markdown record just written. The command carries the full managed path, realized address casing, duplicate .02 / .03 suffixes, and the EVM directory without revealing seeds or private… Show all

    After a successful default grind, print the exact copy-ready keyrx show command for every Markdown record just written. The command carries the full managed path, realized address casing, duplicate .02 / .03 suffixes, and the EVM directory without revealing seeds or private keys. A successful explicit --out FILE grind keeps its established completion-line form; any grind that later fails persistence or custody now withholds every completion command.

    View evidence: keyrx 0.4.17 (opens in a new tab)

  6. keyrx 0.4.16

    GitHub releaseSource verified

    Save every default grind hit as its own mode-0600 Markdown recovery record. Uppercase field headings put each address, path, seed, and key on the following line; Solana records include the base58 and JSON forms, while EVM records carry only the 0x private key. · Name each record… Show all
    • Save every default grind hit as its own mode-0600 Markdown recovery record. Uppercase field headings put each address, path, seed, and key on the following line; Solana records include the base58 and JSON forms, while EVM records carry only the 0x private key.
    • Name each record after both the requested pattern and the exact casing that actually matched: --ends-with coined --ignore-case can produce coined.ic.coiNED.md. A repeated exact result is created without overwrite as .02.md, .03.md, and so on. Prefix and combined-edge searches preserve their realized address text the same…
    View evidence: keyrx 0.4.16 (opens in a new tab)

  7. 3 releases in keyrx/keyrx on 2 Sep

    GitHub release

    Show all 3 releases

    1. keyrx 0.4.15

      GitHub releaseSource verified

      Make an interrupted automatic release resume through the normal tag-only workflow. Inert drafts are found across every authenticated release page, and discovery, upload, publication and final verification remain bound to one numeric GitHub Release identity. · Pin every Cargo… Show all
      • Make an interrupted automatic release resume through the normal tag-only workflow. Inert drafts are found across every authenticated release page, and discovery, upload, publication and final verification remain bound to one numeric GitHub Release identity.
      • Pin every Cargo publish and yank operation to crates.io, then retire one normal predecessor plus one interrupted predecessor only after the new crate and immutable release are independently revalidated.
      • Add behavior-driven controls for pagination, duplicate draft producers, empty-draft races, upload-response identity and digest…
      View evidence: keyrx 0.4.15 (opens in a new tab)

    2. keyrx 0.4.14

      GitHub releaseSource verified

      Restore the normal one-tag release path: a protected version tag, short-lived crates.io OIDC credential, and one sequential run now publish the crate and immutable GitHub Release without a repository-administration token, temporary branch admission, or manual recovery dispatch.… Show all
      • Restore the normal one-tag release path: a protected version tag, short-lived crates.io OIDC credential, and one sequential run now publish the crate and immutable GitHub Release without a repository-administration token, temporary branch admission, or manual recovery dispatch.
      • Restore keyrx.sol beside the authoritative Solana address on keyrx.tech, in both desktop and mobile layouts.
      • Make the concurrent benchmark custody test prove the refusal path from its output and diagnostic instead of depending on wall-clock timing.
      View evidence: keyrx 0.4.14 (opens in a new tab)

    3. keyrx 0.4.13

      GitHub releaseSource verified

      Match output and grind coordination are fail-closed: private files are opened without following links, must be caller-owned and single-link, concurrent grinds cannot share a target, exact match counts are reserved before a record is written, bounded files cannot grow beyond the… Show all
      • Match output and grind coordination are fail-closed: private files are opened without following links, must be caller-owned and single-link, concurrent grinds cannot share a target, exact match counts are reserved before a record is written, bounded files cannot grow beyond the read limit, and invalid zero-work requests are refused.
      • Secret-bearing values have shorter lifetimes and are zeroized more consistently. verify now returns a failing process status when either chain's self-test fails. Existing EVM records refuse scalar zero before address derivation.
      • Benchmark caches are bound…
      View evidence: keyrx 0.4.13 (opens in a new tab)

  8. 4 releases in keyrx/keyrx on 22 Aug

    GitHub release

    Show all 4 releases

    1. keyrx 0.4.11

      GitHub releaseSource verified

      keyrx --help introduces itself as the keyRX CLI too (its summary line was the one place that still said only what it does, not which product it is). Completes 0.4.10. No behaviour change.

      View evidence: keyrx 0.4.11 (opens in a new tab)

    2. keyrx 0.4.10

      GitHub releaseSource verified

      The product names itself keyRX CLI wherever it introduces itself: the page title and cards of keyrx.tech, the README, and the crate description (the start screen already read keyRX | CLI). Two products share the keyRX name now, and this is the one with no token; saying CLI every… Show all

      The product names itself keyRX CLI wherever it introduces itself: the page title and cards of keyrx.tech, the README, and the crate description (the start screen already read keyRX | CLI). Two products share the keyRX name now, and this is the one with no token; saying CLI every time keeps that sentence true without a footnote. No behaviour change.

      View evidence: keyrx 0.4.10 (opens in a new tab)

    3. keyrx 0.4.9

      GitHub releaseSource verified

      The donate panel names the Solana wallet as keyrx.sol only. 0.4.8 printed keyrx.sol · keyrx.sns and called them two spellings of one domain; .sns is not a spelling of anything, so it is gone from the CLI and the site. The addresses are unchanged.

      View evidence: keyrx 0.4.9 (opens in a new tab)

    4. keyrx 0.4.8

      GitHub releaseSource verified

      The donate panel names the wallets as well as printing them: keyrx.sol · keyrx.sns (one on-chain domain, two spellings) under the Solana address, keyrx.eth · keyrx.base.eth · keyrx.hoodfi.eth under the EVM address (ENS, Basename, Robinhood Chain), each resolving to the address… Show all

      The donate panel names the wallets as well as printing them: keyrx.sol · keyrx.sns (one on-chain domain, two spellings) under the Solana address, keyrx.eth · keyrx.base.eth · keyrx.hoodfi.eth under the EVM address (ENS, Basename, Robinhood Chain), each resolving to the address shown; the address stays the thing to read. The site says the same. The two addresses are now the wallets those names resolve to: Solana 2pSgpgA6TqdynuAdVpFEZbyVRrKi5oTyvxGL9gjKEYRX, EVM 0x036C…0000; the previous Gi2z…KEYRX and 0x34F0…00000 are retired, so a name and the address…

      View evidence: keyrx 0.4.8 (opens in a new tab)
Earlier ships (8)

  1. 3 releases in keyrx/keyrx on 21 Aug

    GitHub release

    Show all 3 releases

    1. keyrx 0.4.7

      GitHub releaseSource verified

      Every GitHub Release now carries the .crate packaged from the tag, its Sigstore provenance bundle (keyrx- .crate.sigstore.json; check with gh attestation verify keyrx- .crate --owner keyrx) and the CycloneDX SBOM. Robinhood Chain is named among the EVM chains on the start… Show all

      Every GitHub Release now carries the .crate packaged from the tag, its Sigstore provenance bundle (keyrx- .crate.sigstore.json; check with gh attestation verify keyrx- .crate --owner keyrx) and the CycloneDX SBOM. Robinhood Chain is named among the EVM chains on the start screen, in --help, the README and the site (the same address works there; keyrx networks has its values). No change to grinding, matching or files.

      View evidence: keyrx 0.4.7 (opens in a new tab)

    2. keyrx 0.4.6

      GitHub releaseSource verified

      keyrx networks: the first framed row read "network nameRobinhood Chain" · a key one character wider than the key column ran into its value. The key is name; the bare line below the frame still says "network name". Nothing else changes. Show all
      • keyrx networks: the first framed row read "network nameRobinhood Chain"
      • a key one character wider than the key column ran into its value. The key is name; the bare line below the frame still says "network name". Nothing else changes.
      View evidence: keyrx 0.4.6 (opens in a new tab)

    3. keyrx 0.4.5

      GitHub releaseSource verified

      keyrx networks: the add-a-network steps for MetaMask and Rabby, and the five values a wallet's form asks for, for EVM chains it does not list by default · framed for reading, then each value bare on its own line for pasting (the rule the keys follow). First entry: Robinhood… Show all
      • keyrx networks: the add-a-network steps for MetaMask and Rabby, and the five values a wallet's form asks for, for EVM chains it does not list by default
      • framed for reading, then each value bare on its own line for pasting (the rule the keys follow). First entry: Robinhood Chain (Ethereum L2, mainnet), RPC https://rpc.mainnet.chain.robinhood.com, chain ID 4663, ETH, Blockscout explorer; the chain id was checked against that RPC on 2026-08-21, and a test pins the table. The EVM panel, COMMANDS and A TYPICAL SESSION point at it; the site's EVM section carries the same block with…
      View evidence: keyrx 0.4.5 (opens in a new tab)

  2. 5 releases in keyrx/keyrx on 20 Aug

    GitHub release

    Show all 5 releases

    1. keyrx 0.4.4

      GitHub releaseSource verified

      Import steps said plainly, on both chains: a fresh Phantom or MetaMask insists on a seed phrase first and only then offers a private-key import, so every place that says "import the key" now says "a wallet must exist first (any seed; it never sees this key), then the key import… Show all

      Import steps said plainly, on both chains: a fresh Phantom or MetaMask insists on a seed phrase first and only then offers a private-key import, so every place that says "import the key" now says "a wallet must exist first (any seed; it never sees this key), then the key import ADDS an account"; and the seed route says "import THIS seed as the wallet, then 'add account' N times: account N+1 is the one". MATCH panel, import hints, the EVM panel, THE 128, RECIPES, README and the site's WALLETS and EVM sections. No functional change.

      View evidence: keyrx 0.4.4 (opens in a new tab)

    2. keyrx 0.4.3

      GitHub releaseSource verified

      A TYPICAL SESSION: every row is one line again. The --checksum example was the one command too long for the column and wrapped into a two-line row among one-line rows; it is gone from this panel (RECIPES carries the full --checksum command, and the EVM panel explains the flag).… Show all

      A TYPICAL SESSION: every row is one line again. The --checksum example was the one command too long for the column and wrapped into a two-line row among one-line rows; it is gone from this panel (RECIPES carries the full --checksum command, and the EVM panel explains the flag). No functional change.

      View evidence: keyrx 0.4.3 (opens in a new tab)

    3. keyrx 0.4.2

      GitHub releaseSource verified

      DONATE shows the EVM address: 0x34F0…0000, one address for every EVM chain, ground with --chain evm (a five-zero suffix, EIP-55 case as printed). The same string is in the site's DONATE panel with click-to-copy. Nothing else changes.

      View evidence: keyrx 0.4.2 (opens in a new tab)

    4. keyrx 0.4.1

      GitHub releaseSource verified

      The full EVM pass on the start screen: COMMANDS names both chains and the per-chain bench; THE 128 says what a branch costs on secp256k1 and why --indices buys less there; WHAT A MATCH WRITES carries the EVM four-line block as rows; RECIPES gains EVM (key import) and EVM EIP-55… Show all

      The full EVM pass on the start screen: COMMANDS names both chains and the per-chain bench; THE 128 says what a branch costs on secp256k1 and why --indices buys less there; WHAT A MATCH WRITES carries the EVM four-line block as rows; RECIPES gains EVM (key import) and EVM EIP-55 (--checksum); A TYPICAL SESSION gains bench --chain evm and show evm/dead --keys; verify and show help texts name both chains; estimate --chain evm without a bench says what its model is anchored to. DONATE gains an EVM address slot, empty until the ground wallet is set and shown only then; the ask…

      View evidence: keyrx 0.4.1 (opens in a new tab)

    5. keyrx 0.4.0

      GitHub releaseSource verified

      --chain evm: Ethereum and every EVM chain (Base, Arbitrum, Optimism, Polygon, BNB, Avalanche C-Chain: one key, all of them). The same idea as the Solana path, on secp256k1: one mnemonic pays PBKDF2 once, then the BIP44 tree m/44'/60'/0'/0/N is walked at one HMAC-SHA512 plus one… Show all

      --chain evm: Ethereum and every EVM chain (Base, Arbitrum, Optimism, Polygon, BNB, Avalanche C-Chain: one key, all of them). The same idea as the Solana path, on secp256k1: one mnemonic pays PBKDF2 once, then the BIP44 tree m/44'/60'/0'/0/N is walked at one HMAC-SHA512 plus one scalar multiplication per candidate; the address is the last twenty bytes of keccak-256 over the public key, written in EIP-55 case. estimate, grind and bench take --chain evm; bench --chain evm measures its own rate and estimate reads it (a separate file, bench-evm.txt, because the two loops…

      View evidence: keyrx 0.4.0 (opens in a new tab)

What changed

39 changes on HEY’s record for keyrx: 35 releases · 2 build pace changes · 2 weeks of code pushed.

All 39 changes for keyrx →

The full change record holds 1 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 20h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 42d ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 22h ago.

Code and packages

  • Repository detailsMeasuredRead 6d ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources