Role separation
The phrase “fee recipient” sounds simple until it points at a real person who did not launch the token. Then it becomes a social signal, not just an accounting label.
The role map
The account or system that created the launch transaction.
The address with admin power, if the contract exposes one.
The wallet or identity that may be able to claim a fee share.
The person or project whose name, website, or social identity appears in the launch metadata.
The pool where traders buy and sell the token.
Why this matters
In the BITTER case, the public launch data pointed a fee route at an identity associated with Bitter. That is enough to create confusion. It is not enough to prove that Bitter launched the token.
The clean way to read it is narrower: the launch attached a fee path to a named recipient. Whether that recipient opted in, claimed anything, or had token admin control are separate questions.
If a fee path could create endorsement by itself, anyone could manufacture endorsement.
How to talk about it
That describes the mechanism without claiming who created or endorsed the token.
That is a claim about origin. You need the deployer and project confirmation before saying it.
Claimable and claimed are different. A meter can exist before money ever reaches a wallet.