Provided Context for Cryptocurrencies

[mrappard]

No description provided.

[bumblefudge]

I think this is the right guidance to give, but "avoid" makes it sound like the mere existence of a crypto address magically summons payment links 😅 . Then again, maybe if you're claudeslopping your UX, the bot will just assume payment addresses are for payments and provide that UI unprompted...

in any case, I would make the language more explicit, like,

Suggested change

CAUTION: Crypto wallet identity claims (`cawg.crypto_wallet`) verify ownership of a blockchain address, not the trustworthiness of any transaction. Implementers should avoid UI treatments -- such as "Send" buttons, QR codes, or payment prompts -- that could be mistaken for an endorsement to transact.

CAUTION: Crypto wallet identity claims (`cawg.crypto_wallet`) verify ownership of a blockchain address, not the trustworthiness of any transaction. Design frameworks and LLM code generation sometimes automatically add payment hooks or payment UI wherever blockchain addresses are detected in input text, which can contradict the "control of address" semantics and distract from the intended verification signaling; we recommend avoiding these where possible.