Should proving ownership require revealing the whole wallet history?

Consider a tokenized device warranty. The service desk needs to know that I currently control the valid warranty token—not which collectibles I own, who transferred it to me, or every address I have ever used. Yet the conventional ERC-721 model exposes transfer events and public ownership lookups, making provenance transparent and potentially linking activity over time.

That transparency can help detect duplicate claims, investigate fraud, and establish a useful chain of custody. But it also leaks metadata that can support behavioral profiling, and ownership records on a public ledger are not meaningfully withdrawable later. Selective-disclosure credentials or a zero-knowledge proof could answer “does this person currently control a valid token?” without exposing unrelated history, though the issuer, wallet, and verifier would all need compatible support—and even disclosed identifiers can remain correlatable.

Should privacy-preserving ownership proofs be a wallet default, or would the added verification complexity make real-world adoption worse?

The default should probably be “prove the minimum,” but I would not call the proof private by itself. Public inputs, calldata, emitted events, metadata, RPC logs, and front-end analytics can recreate the link. The threat model has to cover the whole verification path, not just the cryptography.

The provenance argument is stronger than the usual ownership rhetoric. A transfer history can help establish continuity and investigate conflicting claims. But it does not establish that the token legally conveys warranty rights; that connection still depends on the issuer and the governing terms.

As a product choice, I would make privacy the normal path and offer an audit view when the user explicitly authorizes it. Most people do not want to learn proof systems just to get a repair. The verifier should receive a yes/no result, not a blockchain archaeology assignment.

I would separate current control from identity. A zero-knowledge proof that a valid token is controlled is useful; a proof that quietly binds the presenter to a reusable wallet identifier may just move the surveillance point. Recovery and revocation also need answers before this is a default.

Enterprise buyers will ask who can validate the proof five years from now, what happens when the issuer rotates keys, and how support staff troubleshoot a failed presentation. Transparent records are crude, but operationally legible. Privacy wins only if the lifecycle is boring.

There is also a social norm problem: once a rich ownership history is easy to request, people will request it. A selective proof makes restraint part of the interface instead of relying on every verifier to behave well.

If the user sees “verify ownership” and gets a twelve-step cryptography ceremony, they will use a screenshot instead. Hide the machinery, keep the claim narrow, and preserve an auditable route for disputes. Otherwise this is privacy theater with better terminology.