OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Wallets

Keycard CLI

Keycard CLI is an open-source Go command-line tool and shell for managing Status Keycards, programmable NFC/USB hardware wallets for Ethereum and other cryptographic operations. It provides commands for card lifecycle, pairing, key management, signing, credentials, data, metadata and applets.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Keycard CLI — OpenViST project profile in Wallets.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use Keycard CLI when a Status Keycard task belongs in a terminal workflow, such as checking card state, managing keys or invoking supported signing operations. Confirm the card’s applet version and reader setup before choosing a pairing or authentication path.

Who it is for

  • Developers incorporating Status Keycard operations into terminal workflows or scripts.
  • Hardware-wallet users who need command-line access to card information, initialization, keys or signing.

Documented uses

  • Inspect card information such as applet version, initialization status and public key.
  • Initialize a card and manage its authentication secrets.
  • Pair with eligible Secure Channel V1 cards or use the V2 certificate-based authentication path.
  • Generate keys or BIP39 mnemonics, and manage card credentials and data.
  • Install or manage card applets and use supported signing commands.
Before you choose

Requirements & limits

  • Requires a USB smart-card reader; the README says contact readers are more reliable than NFC readers.
  • Linux use requires installing and running the PC/SC daemon.
  • Pairing is needed only for applet versions earlier than 4.0 using Secure Channel V1; V2 uses certificate-based authentication.
  • The README warns that credentials passed as command-line arguments may appear in shell history and process listings, and recommends environment variables.
  • The delete command removes all applets and keys; factory-reset erases all card data.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install the CLI from a release binary

Prepare the Keycard CLI executable from a published prebuilt binary.

Before you start

  • A prebuilt binary for your platform from the project’s releases page.

Steps

  1. Download the prebuilt binary for your platform from the releases page.

  2. Rename the downloaded file to keycard, removing the platform-specific suffix.

Expected outcome

The downloaded executable is named `keycard`.

Guide limitations

  • This describes installation only; it does not verify that the CLI can communicate with a card.
  • Card use requires a USB smart-card reader; contact readers are described as more reliable than NFC readers.
  • On Linux, install and run the PC/SC daemon.
Documentation 1 ↗
Source-based practical guide

Build the CLI from source

Build the Keycard CLI and display its help output.

Before you start

  • The project repository and the tools required by its Makefile.

Steps

  1. Run the command below.

    Documented command
    make build

  2. Run ./build/bin/keycard --help.

Expected outcome

The build command produces the CLI at the documented path, and the second command requests its help output.

Guide limitations

  • These instructions do not cover card setup or executing a card operation.
  • Card communication requires a USB smart-card reader; on Linux, the PC/SC daemon must be installed and running.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
7 October 2026
Original website title
keycard-tech/keycard-cli · Official homepage title · retained in its source language
How we review sourcesSuggest a correction