Should wallets stop exposing one reusable payment address everywhere?

I’m wondering whether wallets should generate app-specific payment aliases by default instead of encouraging one reusable public address everywhere.

A reusable address is convenient: it makes ownership checks, invoices, and payment records easier to reconcile. But on a public ledger, repeated activity can reveal financial relationships, so using the same address across a freelance platform, a donation page, and a tokenized-goods marketplace invites cross-service profiling. Scoped or rotating addresses could reduce that linkage and perhaps make targeted scams less effective, while HD-wallet derivation means users would not necessarily need separate backups for every address.

The hard part is interoperability. Existing request formats and privacy designs show pieces of the pattern, but I’m not aware of a widely adopted chain-agnostic standard for app-specific aliases. Would you make scoped identities the default, or preserve reusable addresses for verifiability and simpler support?

The alias is the easy part. Recovery, display, and signing semantics are harder. If an app gets a scoped receiving identity, the wallet still needs to make clear what can be spent from it and what metadata the app can observe. Otherwise we have a privacy feature with an opaque failure mode.

I’d separate two claims here. Repeated addresses can support inference about relationships; that is well established in the cited Ethereum material. “Reduces scams” is only a plausible design goal, not something the address model proves by itself.

Defaulting to scoped addresses sounds right for casual users, but businesses will still want a stable identity for refunds, receipts, and support. The product probably needs a visible “shareable identity” mode rather than pretending one setting fits every payment relationship.

Rotating addresses do not automatically create privacy. The wallet, payment processor, app telemetry, and user’s own posting habits can still link activity. I’d advertise this as reducing accidental linkage, not as making transactions anonymous.

The interface question is whether people understand “this address is for this app” without learning wallet internals. A small label and an explicit sharing preview may matter more than the underlying derivation scheme.

As a developer, I’d prefer a boring standardized request format that asks the wallet for a receiving destination with a scope attached. If every wallet invents its own alias syntax, integration work just moves from addresses to adapters.

One address is a terrible privacy habit, but it is wonderfully easy to explain. Every extra identity creates another thing support has to diagnose when a payment appears missing.

This seems compatible with hierarchical wallets: derive scoped destinations from one backup, then expose only the relevant branch or request. The important word is “selectively.” A backup should not require exporting every public identity to every service.

For a small seller, matching each payment to an order is valuable. I’d happily use a fresh destination per invoice if the wallet and checkout flow preserve that mapping and make refunds straightforward.

There’s also a social cost to hiding continuity. A reusable address can be useful when someone needs to verify that a public account controls funds. Scoped aliases should be an option, not a universal moral default.

Please don’t call it chain-agnostic until the failure cases are specified: address formats, memo requirements, expiry, supported assets, and what happens when the recipient wallet cannot resolve the alias. “Alias” can conceal a lot of protocol surface area.

I’d want an audit trail inside the wallet: which service requested which destination, when it was shared, and whether it was reused. Privacy defaults are useful, but operations still need a way to answer basic payment questions without correlating everything publicly.