How this workshop works

Everything here is published by The Forge Notes Desk. That is an editorial byline, not a person: there is no invented author, no photograph, no biography and no claimed credential anywhere on this site. Pages are written and revised by the desk, and the modified date on each note is real and moves when the page changes.

What the workshop covers

The subject is how a Solana token is actually made, and what each construction decision permits afterwards. That means the mint account and the fields inside it, the two optional authorities, decimals and the arithmetic that follows from them, associated token accounts and the rent they carry, the metadata account and the document it points at, the Token-2022 extension set, and the shortcuts a launchpad takes on your behalf.

It also covers the reverse direction, which is how a reader who did not create a token can establish what it is. That work is a fixed sequence of account reads rather than a judgement, and it is the reason the field guide exists as a separate note rather than as a paragraph at the end of another one.

Where the facts come from

Field names, account sizes, instruction names, limits and behaviour are taken from the token programs and the metadata standard themselves, not from a launch interface, a tooltip or a screenshot of one. Where an interface uses a friendlier word than the program does, both words appear so a reader can search either one.

Numbers appear on this site under three conditions and no others. They are protocol facts, such as the lamport relationship or an account size. They are arithmetic derived from a documented parameter, with the inputs shown so anyone can repeat the calculation. Or they are labelled explicitly as illustrative, in which case they describe no particular token and no particular fee schedule.

There are no statistics on this site about how common anything is, because the desk has no dataset that would support one. There are no ratings, review counts, testimonials, case studies with invented outcomes, or figures attributed to research that does not exist.

Irreversibility comes before instruction

The organising principle of the whole site is that some steps cannot be undone and most can. Where a step is permanent, the warning sits above the explanation rather than in a footnote, and notes containing irreversible steps carry a list of them before the first section, so a reader who scrolls no further still sees the ones that matter.

Reversible steps are marked as reversible too. Treating everything as dangerous produces documentation that nobody reads carefully, which is its own failure. The point is to make the difference visible, not to make the subject sound frightening.

What this workshop will not publish

Two categories are excluded permanently, and requests for either are declined rather than answered privately.

The first is anything whose purpose is to deceive a buyer. Nothing here describes how to make a live mint authority appear revoked, how to present a supply figure that does not match the raw amount, how to disguise a distribution, how to construct a liquidity arrangement that looks locked without being locked, or how to make any check on the field guide return an answer the underlying state does not support. Explaining how to verify those things is the entire purpose of the site; explaining how to defeat the verification is the opposite of it, and the line is not negotiable.

The second is a verdict on a named token, wallet, team or launchpad. Account state is public and can be described. Intent, competence and honesty are not stored anywhere on chain, and converting a set of fields into a judgement about people would be an opinion presented as a finding. The workshop describes what a reader can check and leaves the conclusion where it belongs.

What this site is not

It is not financial advice, and it contains no price opinions, targets, entries or exits. It is not a service: there is no audit offering, no paid report, no retainer and no bespoke analysis behind the contact address. It is not a launchpad, a tool or a product, and it does not run anything on your behalf.

It also does not claim completeness. The token programs and the standards around them change, tooling changes faster, and a workshop note is accurate as of its modified date and no later. Where the desk has not tested something, the page says so rather than filling the gap with a confident sentence.

Corrections

A specific, checkable correction is the most useful thing anyone can send, and it will always get a faster response than a general complaint. Errors of fact, definitions used inconsistently across two pages, a protocol detail that has changed, or an inference that does not follow: all of those get checked and, where they hold, edited. The route is the contact page, and the desk would rather be corrected than consistent.