Overview
A BITTER-named token appeared on Base.
A token using the Bitter name and ticker was deployed on Base by a third party. It is not the official Bitter project, and bitter.sh did not create, deploy, or control it. This site explains what appeared and shows how to check any token like it by contract, not by name.
Boundary
A fee path is not a founder signature.
The token's launch data pointed a fee-recipient route at @ruemic. That can look like endorsement if you only glance at the surface.
The public Bankr launch page is the source to check for that handle-to-recipient mapping; BaseScan is where you check the contract and address activity.
But fee recipient, deployer, token owner, market maker, and project owner are different roles. Collapsing them into one story is how people get misled.
Guides
Read the parts that answer your question.
When someone launches your token before you do
The human-readable version of what happened, why it mattered, and why I chose to explain it instead of quietly ignoring it.
Read the storyTutorialHow to verify a token on Base without trusting the name
A practical checklist for checking a token address, source, owner, supply, events, and links without relying on branding.
Learn the checksRolesFee recipient does not mean founder
Why a wallet that can receive fees is not automatically the deployer, admin, promoter, or creator of a token.
Separate the rolesMechanicsHow token fees actually move
Pool fees, platform splits, claimable balances, and claimed funds are not the same thing. This page walks through the path.
Follow the fee pathBitterWhat Bitter actually is
The token borrowed the name. The real project is about making AI-built software easier to operate, preserve, and improve.
Meet the real projectWhy this is useful
On-chain facts are public, but interpretation is still work.
A block explorer can show you transactions. It will not tell you whether a brand opted in, whether a fee route is endorsement, or whether a name on a market page means anything beyond metadata.
That is the educational value here: take one messy real case and make the checking process legible enough that the next person can do it faster.
Bitter
Bitter is not this token.
Bitter is the operating layer for AI-built software: a place for generated projects to keep their context, ship real changes, and keep improving after they are first built.
Common questions
Fast answers before you read deeper.
Is the BITTER token on Base the official Bitter token?
No. It was deployed by a third party. The Bitter project at bitter.sh did not create, deploy, or control it.
Did Bitter launch a coin or token?
No. Bitter is software, not a token. A separate party launched a token that uses the Bitter name.
What is the token contract?
The BITTER-named token covered here is 0x696aCE6f17B966Dd667501b6952b56f7B8653ba3 on Base.
Why does the fee route matter?
Bankr lists @ruemic as the fee recipient for this launch and maps that recipient to a Base address. That can make a token look connected from the outside, but it does not prove who created, controls, or endorses the token. Check the Bankr launch page or the launch API. Read the role map.
How do I check a token using a project's name?
Start from the contract address, separate the roles, and compare the token against the project's own site. Use the checklist.