Update Coldcard listing: domain rebrand, product version not reflected, and listing predates Mk5 release

[devdavidejesus]

Summary

The current _wallets/coldcard.md entry has not been substantively updated since 2021-03-17 (last commit by @doc-hex: "Coldcard now has deterministic build, as of v4.0.0"). Several factual changes have occurred since then that are not reflected in the listing.

Key observations:

• The website link points to coldcardwallet.com, which now redirects to coldcard.com (HTTP 301).
• The companion listing _wallets/coldcardq.md already uses the current coldcard.com URL, creating internal inconsistency between the two Coldcard entries.
• The vendor's current active product line (per the official site's hero banner and store) consists of COLDCARD Mk5 and COLDCARD Q. Mk4 remains supported by firmware but is no longer sold as a new device; it is referenced on the official site primarily in migration guides ("How to Clone/Migrate from Mk4 to COLDCARD Q").
• The _wallets/coldcard.md listing uses the family name "Coldcard" without a hardware version. While the convention across _wallets/ is mixed, several hardware wallets are listed with their specific version (e.g. "Trezor One", "Trezor Model T", "Ledger Nano S", "BitBox02", "Coldcard Q", "Cypherock X1", and the recently added "OneKey Classic 1S" from April 2026). The "Coldcard" listing predates the Mk5 release and does not currently distinguish which product version it represents.
• The description in _translations/en.yml references "a dedicated security chip" (singular). The Mk5 product documentation describes a dual secure element architecture (Microchip ATECC608 and Maxim DS28C36B).

This Issue is opened to bring visibility to these factual updates so they can be addressed collaboratively.

Evidence

All evidence below is verifiable via public sources:

#	Finding	Source
1	coldcardwallet.com returns HTTP 301 → https://coldcard.com/	Direct HTTP request (curl -sI)
2	Current canonical domain coldcard.com returns HTTP 200; site title: "COLDCARD - Most Trusted Bitcoin Signing Device"	https://coldcard.com/
3	_wallets/coldcardq.md already uses https://coldcard.com/	https://github.com/bitcoin-dot-org/Bitcoin.org/blob/master/_wallets/coldcardq.md
4	Vendor's homepage hero image: "COLDCARD Q and COLDCARD Mk5 side by side"; primary store buttons: "Shop Q" and "Shop Mk5"	https://coldcard.com/
5	Official site explicitly references support scope: "Only for Mk5, Mk4 and Q (not Mk3 or earlier)"	https://coldcard.com/
6	Mk4 product URLs on store.coinkite.com return HTTP 405 (no longer sold as new); Mk5 and Coldcard Q remain available	Direct HTTP requests
7	Vendor documentation explicitly describes dual secure element architecture: "two secure element chips from different manufacturers (Microchip ATECC608 and Maxim DS28C36B)"	https://coldcard.com/
8	_wallets/coldcard.md last substantive commit: 2021-03-17 (predates Mk5 release)	https://api.github.com/repos/bitcoin-dot-org/bitcoin.org/commits?path=_wallets/coldcard.md
9	Recent listing pattern: "OneKey Classic 1S" added on 2026-04-07 with version-specific naming	https://api.github.com/repos/bitcoin-dot-org/bitcoin.org/commits?path=_wallets/onekeyclassic1s.md
10	Firmware repository Coldcard/firmware actively maintained (last push 2026-04-25), with @doc-hex as primary committer	https://api.github.com/repos/Coldcard/firmware

Current listing discrepancy

Aspect	Listed in _wallets/coldcard.md	Current state
Website URL (link)	https://coldcardwallet.com/	Redirects (HTTP 301) to https://coldcard.com/
Source repository (source)	https://github.com/Coldcard/firmware	Already current ✓
Product name (title)	"Coldcard" (no version)	Vendor's active product line: Mk5 and Q (separately listed); Mk4 supported but no longer sold
Description (en.yml)	"a dedicated security chip" (singular)	Mk5 documentation specifies dual secure elements (ATECC608 + DS28C36B)
Last substantive update	2021-03-17	~5 years; predates Mk5 product release

Possible path forward

1. Coordinated vendor update. The Coinkite team can propose the update directly, ensuring that the listing accurately reflects the product’s current positioning and their preferences.

Notes

• Opening this issue as part of the broader wallet section audit tracked in Wallet section audit: discontinued wallets, outdated descriptions, and missing Lightning wallets (April 2026) #4662.
• Not opening a PR yet; the right path forward seems better decided collaboratively given the multiple aspects involved.
• This Issue documents factual observations only. Any decisions about whether to update the listing, and how, belong to the bitcoin.org maintainers in coordination with the Coinkite team.

cc @crwatkins @doc-hex

[devdavidejesus]

Thank you, @siim-m !

Your PR #4709 addresses the update. I appreciate your help in keeping the wallet entries accurate. I will proceed with closing this issue.