> ## Documentation Index
> Fetch the complete documentation index at: https://docs.archr.win/llms.txt
> Use this file to discover all available pages before exploring further.

# Your first launch from X

> Trigger a coin launch by mentioning `@archrdeploy !deploy SYMBOL` in a tweet.

The X (Twitter) trigger deploys the same on-chain shape as the [site launch](/getting-started/first-launch-site) (a plain 1B-supply ERC-20 with a permanently-locked Uniswap V3 pool), except the trigger is a tweet mention instead of a wallet signature.

There is no gas cost to the launcher from Reddit or X. The launch is broadcast on your behalf, and the addresses come back as a reply to your tweet.

<Note>
  X triggers do **not** support the dev-buy option. If you want to buy a share of your own coin's supply in the launch transaction, use the [site flow](/getting-started/first-launch-site) instead.
</Note>

## Command shape

Post a tweet that mentions the bot and contains a `!deploy` command:

```
@archrdeploy !deploy SYMBOL
@archrdeploy !deploy SYMBOL name goes here
```

* `SYMBOL` is the ticker: short, alphanumeric, uppercase by convention.
* `name` is optional; when omitted the coin's name defaults to the symbol.
* The command is case-sensitive on `!deploy`.
* Only the first `!deploy` in a tweet counts. One coin per tweet; two tweets in a row each launch their own coin.

## What the bot does

1. Reads new mentions on X.
2. Sanitizes the name and symbol per the rules on [launch → name and symbol rules](/launch/overview#name-and-symbol-rules).
3. Prices the launch tick from the live Chainlink ETH/USD feed on Robinhood Chain (fail-closed if the feed has aged out).
4. Calls [`TwitterFactory.launch(...)`](/network/contracts#twitterfactory), a separate launcher contract on the same chain with the same locked-LP guarantee as the Reddit and site factories.
5. Replies to your tweet with the coin address, pool address, and Blockscout link.

## Dedupe

Each tweet can trigger at most one launch. [`TwitterFactory`](/network/contracts#twitterfactory) enforces this on-chain: a duplicate `!deploy` on a tweet that already produced a coin reverts `AlreadyLaunched`.

## When a launch is rejected

The platform does not reply when a command cannot be launched. Common reasons a `!deploy` will not produce a coin:

* The command failed to parse.
* The bot cannot see the tweet (private account, mention was to a different handle, etc.).
* The platform is paused for maintenance.

If your tweet parses cleanly and the bot goes silent, check [@archrdeploy](https://x.com/archrdeploy); maintenance windows are posted there.

## After the reply

The bot's reply includes the coin's Blockscout URL. Open it and verify the same three properties as any launch:

* The token has a fixed supply of 1,000,000,000e18.
* The V3 pool exists at fee tier 1% (tickSpacing 200) and holds the full supply as single-sided liquidity.
* The LP NFT is held by the [`TwitterFactory`](/network/contracts#twitterfactory); the liquidity is permanently locked.

Trade on the swap widget at [archr.win/token/\<address>](https://archr.win) or any Uniswap V3 aggregator on 4663. See [trading overview](/trade/overview#where-to-swap).