A reply is the whole form.
One line of text mints a coin whose creator, creator fees and launch protections are set on-chain at deploy. The parser and every guard it enforces are real — run them. The on-chain deploy is not available: launching is closed until the launchpad opens, so the relayer signs nothing and every launch request is refused. The X side is not wired either: nothing here watches X, nothing replies in-thread, and the creator address is taken on your word alone.
Launching is closed until the launchpad opens. The parser and the guards are live — run them; the relayer will not sign until then.
Real
- The command parser and every guard it enforces — ticker charset, reserved and brand tickers, name sanitising. Type a command above and it runs, here, now.
Not wired
- The on-chain deploy. While launching is closed the execute endpoint refuses, so no coin is created, no protections are applied and no gas is spent. The relayer path is written and reviewed — it is simply not reachable from here until the launchpad opens.
- X mention ingestion — nothing watches X for replies. You paste the command here yourself.
- The auto-reply that would post the coin link back into the thread. That needs write-scope OAuth on the operator's X app.
- Identity. The creator address is self-declared — no X account is proven to own it.
The reply you would post
Mock composerReply to any post with a launch command and the relayer mints the coin, with you as the creator.
Illustration only — not a real post, and no such account is monitored.
Parsed by the relayer
Type a command to see what the parser makes of it.
Verified X path (not wired)
Waiting for input.