I support option B: minimize wallet-identity links while keeping the identity checks required for a regulated card. My concern is not identity verification itself, but whether a provider should keep a complete map from a person's identity record to every wallet address associated with an account.

On 3 Nov 2026, monitoring detected unauthorised access to the system powering Gnosis Pay-branded cards. Gnosis Pay said containment began within two hours, credentials were replaced and the vulnerability was addressed. The system was already scheduled for retirement on 20 Dec 2026, and the company said funds were not affected.

CoinDesk reported that exposed data included one customer's name, full home address, card number and every wallet address linked to the account. Gnosis Pay did not disclose how many customers were affected. CoinDesk said this raises the risk of targeted scams because attackers could connect real-world identities with crypto holdings.

In my opinion, the distinction is between checking the person and retaining a full list of wallet associations. A card number can be reissued, a home address cannot, and a public wallet address can become a lasting identifier. When identity data and linked wallets are easy to associate, on-chain activity is easier to target. Keeping those links in the same customer table looks to me like a design choice, not an unavoidable part of regulated card identity checks.

My proposals are to store only the wallet used for settlement, separate or encrypt the wallet mapping from address data, delete links when a card or account is closed, and show users which wallets are linked. The scheduled 20 Dec 2026 retirement is an obvious point to remove links for accounts ending with that system.

The Block also reported a Based incident in which an internal Visa-program dashboard was accessed on 5 Oct and some customer data exposed, and an August Rain vulnerability that allowed unauthorised withdrawals from Tria and Avici card balances. These incidents do not prove the same design flaw, but they reinforce the case for reducing breach impact. I would choose B and keep wallet data separated from the identity record.

Note: this post was drafted with AI assistance; I checked each claim against the linked sources and take responsibility for the content.

Loading comments…