SLIMEWIRE
LAUNCH OS GUIDE
Open Launch OS
FROM CA TO COMPLETE OPERATION

Launch OS playbook.

Use one Launch Passport to keep the brand, links, Telegram configuration, website, listings, content and emergency controls consistent.

1. Forge the Launch Passport

Open Launch OS from anywhere

No SlimeWire account, terminal login or wallet connection is required.

Paste the CA or supported coin link

Choose Official Dev Project or Community Takeover. CTO mode is clearly labeled and does not claim affiliation.

Press Forge Launch OS

SlimeWire resolves the coin identity/PFP, creates the public HQ, generates content and stores the project.

Save the private edit link

It reopens every customization setting on any device. Keep it private because anyone with that link can edit the project. The separate public HQ link is safe to share.

Follow the readiness checklist

It identifies the exact remaining platform-owned steps instead of pretending everything is connected.

2. Brand Kit

Choose a voice, color, tagline and description. The banner and community PFP are rendered from the coin image plus SlimeWire launch artwork.

3. Telegram automation

Open the Telegram tab

Tap “Add bot to group.”

Select the group and approve permissions

Telegram requires this human group-selection step. The setup code identifies the exact Launch Passport.

Automatic setup runs

Buy Bot, Raid Bot, Rose and Scan Bot turn on; the coin CA, welcome copy and raid defaults load.

Fine-tune when needed

/settings opens controls. /raid <X link> starts a pinned raid. /cancel raid stops it.

The bot needs Pin Messages, Delete Messages and Restrict Members permissions for the complete experience.

4. X setup

X does not expose account-creation or Community-creation APIs. Launch OS removes the surrounding work:

  1. Open X signup from the Content tab or connect an account you already control.
  2. Complete X’s own email/phone/CAPTCHA requirements.
  3. Upload the generated avatar/banner.
  4. Copy the generated bio, launch post and pinned post.
  5. Save the final X URL under Website so the HQ and listing dossier use it.
  6. If available, use X OAuth or X Delegate later instead of sharing passwords.

5. Public Launch HQ and links

The public HQ is created immediately. It displays the exact CA, project mode, official links, market tools, holder/airdrop maps and crisis notice.

Enter X, Telegram, website, Discord and Farcaster URLs in the Website tab. Link Sentinel rejects malformed or unsafe protocols and shows what is still missing.

6. Listing Assistant

ServiceAutomatedHuman step
DEX ScreenerCA, chain, description, links, logo and page shortcutEnhanced profile/CTO order if desired
CoinGeckoReusable application dossierAccount, verification post, form and CAPTCHA
JupiterToken-page and readiness shortcutAny external verification process

Save order IDs, application notes and submission state inside the project.

7. Content system

Edit and copy five synchronized templates: launch post, pinned post, Telegram welcome, milestone post and emergency post. Keep the CA and Launch HQ URL intact. Do not automate fake engagement or duplicate spam.

8. Launch-day command center

Market metrics can be temporarily unavailable while new pools index. A blank metric is shown honestly rather than fabricated.

9. Crisis and migration procedure

Activate Crisis Mode

The public HQ immediately displays the warning.

Copy and publish the emergency post

Post it from the project’s real X/Telegram accounts.

Stop active campaigns

Use /cancel raid and pause scheduled content.

Correct links

Update the Launch Passport and replace group pins.

Document migrations

Record the new CA and application references; never silently substitute contracts.

Recommended operating order

Passport → Brand → Telegram → Website links → X → Listings → Content review → Command Center.

A successful launch is never guaranteed. Launch OS removes setup mistakes and fragmented tooling; it does not manufacture buyers, liquidity or trust.