pons stores a token’s logo as a string capped at 512 bytes and its description at 2048. Both caps were found by binary search against the live factory, which reverts MetadataTooLong() one byte past them. That is nowhere near enough for an image, let alone audio.

So the payload goes somewhere else. Our registry writes it as contract bytecode — the SSTORE2 pattern — at roughly 200 gas per byte to write and 3 to read, against 20,000 gas per 32-byte slot for a naive SSTORE. On a chain running at 0.067 gwei that makes inscribing cheaper than the 0.0005 ETH launch fee itself.

The launch and the inscription happen in one transaction. Our router calls pons, takes the token address it returns, and writes every payload against it before the transaction ends — so there is no window where a token exists without its contents.

The 512 bytes are not wasted. Each launch generates a small deterministic SVG and puts it in logo. That is the only payload that renders outside this site, because ERC-20 has no metadata standard and wallets read token lists rather than chain state.