How the story is found

A coin's story is what the project says it is. Larpsium takes it from two places only, both written by the project itself: its website, and the launch record its creator put on chain when the coin was created. Listings, posts, and other people's descriptions are never used as the story.

The launch record (rule launch-record-v1)

Elysium launchpads such as BOXA, Kleos, and ElysPump take a coin's details when it is created and write them into the launch transaction: a short description, and usually a website, an X account, a Telegram group, and an image. Larpsium finds that transaction itself, from the chain:

1. It replays the token's Transfer logs from block 0 (the same replay used for the holders) and takes the transaction of the first mint, the one that created the supply.
2. It reads that transaction's receipt and input from Elysium's public RPC.
3. It decodes every text value in the launch event (and, failing that, in the launch call) and keeps the metadata object: the description, website, X, Telegram, and image fields.

Because the record was written in the very transaction that created this token's supply, it belongs to this contract; nobody else can change it later. It is still the creator's own statement: a description on chain is not proof that anything in it is true.

The report shows it under In its own words, with a link to the launch transaction on Elyscan. The investigation log says whether a launch record was found, which launchpad emitted it, and whether it names a website.

The website

The website is chosen in this order: a link you send with the check; else the website in the launch record; else a web address written inside the launch description; else, only for a coin with no launch record (for example a token bridged from HyperEVM), the website its launch venue lists. The answer always says where the link came from.

The site is fetched once, over HTTPS, as a public page: no sign-in, no scripts, up to 512 KB in 8 seconds. From it Larpsium keeps the page title, its own description (the meta description, else its first substantial line), the statements it makes about a working or planned product, any contract addresses it names, and links to public code. The page text itself is not stored.

A site that only renders with JavaScript may show little or nothing to a plain fetch; the report then shows what was there and says what could not be read. X and Telegram are linked but never read.

How the story is judged

The core pitch is checked three ways: does the project's own site answer, does it name the checked contract, and does it describe a working product or only plans.

• BACKED: the site answers, names this contract, and describes a working product.
• PARTLY BACKED: one or two of those hold.
• UNPROVEN: none can be shown; for example, only the launch description exists, or the site answers but names no contract.
• LARP (contradicted): the site names a different contract, or a site the project lists does not answer.

A coin with neither a launch description nor a website has no public story, and the answer says exactly that rather than "not assessed".

What it does not do

It does not run the product, read X, read Telegram, judge images, or decide whether a meme is funny. A good story is not a safe coin, and an honest one-line meme is not a lie: the story stamp only says how much of what the project claims can be shown.