documentation

A Hoodstampy launch produces a native Pump.fun token — it trades on the Pump bonding curve, graduates to PumpSwap, and uses Pump's native holder rewards where supported. Hoodstampy does not run its own AMM or bonding curve.

The addition is that the token's media is written on-chain into Solana transaction history, cryptographically tied to the mint. Once confirmed, it cannot be edited or taken down, and it does not depend on any server Hoodstampy controls.

1. Connect a Solana wallet and open /create.
2. Give the coin a name, ticker, and description, and drop in the media to inscribe.
3. Optionally set an initial dev buy, a custom creator tax, and X / website links.
4. Review the transaction preview — chunk count, on-chain size, and creator tax are shown before you sign.
5. Approve once. Hoodstampy creates the coin and inscribes the media, then confirms on-chain.

The whole flow runs client-side against public programs; no private key ever leaves your wallet.

Because the SPL Memo program requires valid UTF-8, content bytes are base64-encoded. Each memo is a compact, deterministic record. The first memo is the manifest; the rest are ordered content chunks:

manifest  SCRB1|M|<mint>|<creator>|<mime>|<len>|<sha256>|<total>
chunk     SCRB1|C|<mint>|<sha256>|<index>|<base64 data>

The manifest carries the protocol version, mint, creator, MIME type, original byte length, the SHA-256 of the full content, and the total chunk count. Every chunk repeats the mint and content hash, so it is bound to the exact file it belongs to.

1. Generate the Pump mint keypair in the browser, so the mint address is known up front.
2. Compute the media SHA-256 and split it into size-measured chunks.
3. Upload Pump-compatible metadata (image + JSON, including any X / website links) to Pump's IPFS.
4. Create the native Pump.fun coin, with an optional atomic creator buy.
5. Inscribe the manifest and chunks as SPL Memo transactions.
6. Reconstruct the content from Solana and verify the SHA-256.

Hoodstampy serializes each transaction message client-side to decide how many inscription transactions are required — the count is never hardcoded. Every transaction is signed in a single wallet approval, then sent and confirmed on-chain; a failed launch resumes from the last confirmed step and only re-signs what is left.

The content gateway /api/content/[mint] locates the mint's memos on Solana, orders the chunks, concatenates the bytes, and recomputes the SHA-256. It only serves the content when the hash matches the manifest — corrupt or incomplete data is never served as verified.

GET /api/content/<mint>        # verified bytes, original MIME type
GET /api/inscriptions/<mint>   # on-chain manifest (mint, creator, hash, size)

Supported types: PNG, JPEG, WebP, GIF, MP3, WAV, plain text, and HTML. Images can be resized and re-encoded to WebP in the browser; audio is stored byte-for-byte and never silently altered.

Larger files simply need more inscription transactions — more base fees — but still only one wallet approval. The transaction preview shows the exact chunk count before you commit, so the cost is never a surprise.

At launch you can set a custom creator tax — Pump.fun's configurable per-trade creator fee, routed to you. It is only offered when the on-chain Pump config allows it, and is clamped to Pump's ceiling (currently 3.00%). Leave it on Default to use Pump's standard fee schedule.

You can also attach an X (Twitter) handle and a website. Both are written into the coin's Pump.fun metadata, so they show up wherever the coin is listed. The website defaults to hoodstampy.fun unless you change it.

Every launch appears on the shared board. It merges the on-chain index with launches from your own browser, and pulls live market data (price, 24h volume, liquidity, market cap) from DexScreener in batches.

• King of the Hill crowns the coin with the highest live 24h volume.
• Sort by volume, market cap, liquidity, or launch age.
• Filter by status (trading vs. still on the bonding curve) and by media type, or search by name, ticker, or mint.
• A live activity ticker scrolls the newest launches.

• MIME type is validated from the actual file bytes, not just the extension.
• The SHA-256 is shown before signing and re-verified when the content is reconstructed.
• HTML snapshots are self-contained: CSS is inlined and images are embedded as data URIs, so nothing loads from an external server. They render only inside a sandboxed iframe under a CSP that permits inline styles and data-URI images but blocks all scripts, external origins, and wallet, parent, popup, or navigation access.
• No server holds a private key; every transaction is signed by the connected wallet.

NEXT_PUBLIC_SOLANA_RPC_URL=      # a Solana mainnet RPC endpoint
NEXT_PUBLIC_APP_URL=            # this app's public URL
# optional
NEXT_PUBLIC_SOLANA_NETWORK=mainnet-beta
NEXT_PUBLIC_SCRIBE_MAX_CONTENT_BYTES=262144  # default; ~256 KB

Pump.fun runs on mainnet-beta, so use a mainnet RPC. There is no program id to configure — Hoodstampy relies only on programs that are already deployed.

Does Hoodstampy run its own token contract?

No. Every coin is a native Pump.fun token minted through Pump's own programs. It trades on the Pump bonding curve, graduates to PumpSwap, and keeps Pump's native fee and holder-reward behavior. Hoodstampy only adds the on-chain media layer.

Where does the media actually live?

In Solana transaction history, as SPL Memo instructions bound to the mint by its content hash. There is no external image host to expire — anyone with an RPC endpoint can reconstruct the exact bytes and verify the SHA-256.

What happens if a launch fails halfway?

The flow is resumable. Each transaction is confirmed before the next is sent, so a failed launch picks up from the last confirmed step and only re-signs the inscriptions that are still missing.

Why do fresh coins show $0 volume on the board?

The board reads live market data from DexScreener, which only indexes coins once they have a DEX pool. A coin still on the Pump bonding curve has no pool yet, so it legitimately reads $0 until it graduates.

Can I edit the media after launch?

No. That is the point — the inscription is permanent. Verify the preview and the SHA-256 before you sign.