The labels contract

What it can do

Any wallet can attach one label to a spender: a name of 1 to 32 plain characters, a category, and an optional https link (the link text is in the event, its keccak-256 hash is stored). The same wallet can replace or remove its own label at any time.

Any wallet can flag a spender once, with a reason code, and take its flag back. The contract keeps totals per spender: labels, flags, and counts per category and per reason. It lists every spender ever labelled or flagged, in first-seen order.

What it cannot do

It cannot hide, remove or rank anyone else's label or flag. There is no owner, no admin, no pause, no fee and no upgrade path; the code that is deployed is the code that runs, for good.

It has no payable function, no receive and no fallback, so it cannot hold ETH or tokens. It never calls a token. Revoking a permission is a call your wallet makes to the token itself, not to this contract.

It cannot tell whether a label is true. A label is a public note signed by the wallet that wrote it.

Codes

Categories: 1 Exchange router, 2 Lending, 3 NFT marketplace, 4 Bridge, 5 Launchpad, 6 Token permit service, 7 App or game, 8 Other.

Flag reasons: 1 Unexpected transfers reported, 2 Imitates a known app, 3 Source not published, 4 Linked from a phishing site, 5 Abandoned or replaced, 6 Other.

Where it is

Not deployed yet. Until it is, the labels page runs in practice mode: labels and flags you write are signed with your wallet and kept in your browser only, so you can see how it will work. Nothing is sent.