Chrome extension for X and pump.fun

Launch tokens from viral X posts before the feed cools down.

VIRL/X turns a tweet into a pump.fun launch draft, signs through an embedded Solana wallet, and submits through a managed backend.

Open source build See workflow

VIRAL SIGNAL

ReplyRepost

VIRL/XEMBEDDED WALLET ARMED

LaunchSettingsHistory

CURRENT SIGNALBreakout Frog $FROG

Image, name, ticker, source URL, and metadata ready.

Backend
OnlineNeed
0.0602 SOLMints
2

Built for the launch moment

One product surface: X controls, popup wallet, drawer editor, hidden instant runner.

The extension keeps the high-friction pieces out of the tweet flow. Users connect once, then choose between immediate execution or a compact edit pass.

Instant launch

Click the lightning control on X and submit through the hidden runner without opening another screen.

Editable drawer

Use the rocket control when name, ticker, image, or description need a final pass before launch.

Embedded wallet

Privy handles the Solana wallet session in the extension origin. Users arm once, then launch from X.

Managed backend

RPC, Sender, Pinata metadata, and public Privy config stay behind the backend instead of shipping secrets.

Readiness console

Balance, backend health, required SOL, launch status, and vanity pool count stay visible.

Open-source flow

The extension can be self-built while production hosting, abuse limits, and backend auth mature.

How it works

From tweet to submitted mint in four system steps.

Browse X

The content script watches posts and injects lightning and rocket controls into the native action cluster.

Extract signal

Tweet text, author, URL, avatar, and media become a token draft with launch metadata.

Sign and send

The runner signs with the embedded wallet, adds the mint signature, and submits through Helius Sender.

Open market

The mint is copied and the pump.fun coin page opens after submission when the setting is enabled.

Install options

Use the managed VIRL/X backend or run the full stack yourself.

Coming soon in Chrome Web Store

Managed backend

Use the hosted VIRL/X API. No Helius, Pinata, or Sender credentials on the client.

npm install
npm run build

# Load dist/ in Chrome extensions
# Backend: VIRL/X managed API

Self-hosted backend

Run the API yourself when you want full control over RPC, metadata, signing routes, and limits.

npm install
npm run server:dev
npm run build

# Load dist/ in Chrome extensions

FAQ

Straight answers for the presentation.

Is this a side panel?

No. The icon opens a normal Chrome action popup. Tweet actions use either instant mode or an in-page right drawer.

Do users paste API secrets?

No. The current product direction is managed backend mode so normal users do not ship Helius, Pinata, or Privy secrets.

Why warm vanity mints?

Generating a ...pump mint at click time is too slow. The hidden runner keeps a local pool ready while the user browses.

What is still risky?

Mainnet signing behavior, Helius Sender responses, pump.fun program changes, funding, and Chrome Web Store review still need live validation.