FARTPAD starts with a simple constraint: a coin's identity begins as text. A word, a phrase, or an inside joke becomes an ASCII artifact that can be reviewed, named, and carried into a proposed FARTCOIN pair. That constraint shapes both the interface and the architecture.
The current release is an interactive browser preview. Its working layer covers character generation, identity editing, local drafts, exports, and compatible wallet connections. AI generation, token launches, liquidity creation, and trading are not connected. Understanding that boundary makes the technology easier to explain.
Characters are the source material
ASCII artwork is a grid of ordinary characters, with spaces and line breaks doing as much work as the visible marks. FARTPAD keeps that artwork as a string and displays it in a monospace text block. The preview uses text rendering rather than interpreting the generated artwork as HTML, so a character remains a character.
The prompt field accepts up to 120 characters. The local generator checks recognizable subjects such as cats, frogs, moons, ghosts, and clouds, then selects an original scene template. Other prompts pass through a custom 5-by-7 glyph alphabet: the input is normalized, reduced to letters and numbers, and rendered as a short character study. A hash of the prompt and variation number determines its decorative pattern.
This is a deterministic pipeline. The same prompt, style, and variation produce the same result; no model inference happens behind the button. Classic, Dense, and Light apply character substitutions to the result. Variations change selected details while preserving the underlying illustration. Suggested names and tickers also come from local rules, and the creator can edit both before saving.
A draft is a portable object
A coin idea is represented by its prompt, artwork, name, ticker, style, and intended quote asset. Saving adds a draft identifier, variation number, network label, and update timestamp. FARTPAD stores up to 50 drafts in the browser's local storage, allowing a creator to reopen or delete an idea during later visits to the same browser context.
That storage is local to the browser; it is not an on-chain registry or a cloud account. The export tools give the idea a separate life: TXT preserves the character artwork, while JSON carries the identity and draft settings. Copying the ASCII keeps its text form intact. A future metadata service could build on this draft format, but the exported object itself does not create a token.
Connecting a wallet has a precise meaning
FARTPAD detects compatible Phantom and Solflare providers exposed by the browser. It calls the selected provider's connection method, receives a public key, and updates the displayed address when the wallet changes accounts or disconnects. The current code requests no message signature and submits no transaction.
This matches the distinction in Phantom's connection documentation: a connection shares the account's public key, while message signing and transactions are additional requests. In a production launch flow, the transaction review and wallet signature would be explicit steps with their own costs and outcomes.
Why the quote asset matters
The source fixes the intended quote mint to 9BB6NFEcjBCtnNLFko2FqVQBq8HHM13kCyYcdQbgpump, matching the address published on FARTCOIN's website. That value is included in saved drafts and JSON exports. It expresses the product's central rule: every proposed market pairs the new token with FARTCOIN.
Making that rule real requires an on-chain integration. Raydium LaunchLab binds its quote mint through a GlobalConfig; a launch would need a compatible configuration for FARTCOIN. The configuration cannot simply be invented by a frontend, and creating one requires protocol authority. No such availability is established by this preview.
A separate route could use a Raydium CPMM pool, where the creator supplies both assets and the initial deposit ratio establishes the opening price. That involves funded liquidity and a signed pool-creation transaction. A bonding-curve launch and a directly seeded pool are different economic designs; the production architecture still needs to choose and verify its path.
The next layer: generation, metadata, settlement
The proposed AI layer would accept a prompt through a backend, generate character artwork, and validate its dimensions and output format before returning it for review. Keeping model credentials on that backend would let the browser remain a creation surface. The original ASCII and a rendered image could then be published with durable token metadata.
After review, a transaction builder would create the mint, apply explicit supply and authority settings, attach metadata, and prepare the chosen FARTCOIN liquidity or launch instructions. Before signing, it should verify mint addresses and show costs, allocations, and authority decisions. Confirmation and indexing would turn a draft into a visible on-chain record. The aim is to preserve one coherent identity from the first character through the final transaction.