Because the pair should be real before you name a coin against it. Transaction one spawns the pair token and opens its pool; when it confirms, that token exists on-chain and anybody can see it. Transaction two launches your coin into a pool quoted in it. The factory can still do both at once — if you launch against a pair nobody has made yet, it spawns it inline in the same call — but the two-step path is the one the site walks you down.

A token’s metadataURI is frozen the moment it is deployed, so the URL in it had better keep resolving to the right picture. Everypad signs an attestation only after fetching that URL back and confirming the bytes it returns hash to the same image the pair’s id came from. It refuses nobody — anyone can upload anything — it only refuses claims it cannot verify.

The pair’s id is the keccak of the file exactly as you uploaded it. Normalising first — downscaling, stripping EXIF, converting to webp — would make the identity depend on the image library’s version: bump it, and the same picture silently becomes a second pair that can never be merged. Raw bytes are stable forever. The cost is that a re-saved copy of a picture is a different pair, which is the honest reading of "the bytes are the identity".

Nobody. Not you, not us, not the deployer. The locker contract owns every position and exposes no withdraw path — only a fee-collect call that pays the coin’s launcher. This is permanent by construction, which is worth saying plainly in both directions: it means nobody can rug the pool, and it means any bug in that contract is equally permanent.

Charting sites index pools quoted in WETH. Your pair token has a WETH pool from the moment it spawns, so it shows up. Your coin is quoted in the pair token, so most terminals skip it — that is the trade you are making in exchange for the chart reading in your pair instead of in ETH. If you would rather be indexed, the WETH rail launches the same coin quoted in WETH and keeps the image as its identity.