Everything you need to understand the Arclans launch flow, from writing a clear X post to finding the canonical token page and trading venue.
Arclans is an X-native interface for launching tokens on Arc. It lets a user express a launch request in an ordinary X post by mentioning @arclansbot, naming the token, providing its ticker, and attaching an image.
Arclans is not an independent launchpad. Argus is the underlying launch venue: launches are executed through Argus, and the resulting market trades there. Arclans focuses on making that flow legible from X and giving each completed launch a canonical page.
The flow begins with a public launch request. Arclans reads the request, identifies the token name and ticker, and checks that the information needed for a standard launch is present. A single token image can travel with the request as an attachment.
If the request is complete and clear, the token is launched through Argus on Arc. Arclans then replies with the token contract address and a link to its canonical Arclans token page. That page is the reference point for verified launch details and the direct route to the Argus market.
Start a new X post and mention @arclansbot. State the token name and ticker in the same post, then attach one image that represents the token. Keep the request direct enough that a person could identify the intended name and ticker without guessing.
@arclansbot launch Arclans $CLANSArclans validates the launch intent before anything is executed. If required information is missing, the bot asks for it. If two interpretations are possible, the request waits for clarification.
You do not need to memorize one rigid command. Arclans recognizes common launch language and can understand small command typos when the launch intent remains clear. The following examples express the same request:
@arclansbot launch Arclans $CLANS@arclansbot create Arclans $CLANS@arclansbot deploy Arclans ticker CLANSFlexible syntax does not mean that critical information is inferred. Arclans does not guess a token name or ticker. Missing or ambiguous fields must be resolved before a launch can continue.
Attach one token image directly to the X post that contains the launch request. Keeping the image and command together makes the intended asset clear and avoids separating launch context across multiple posts.
Use a square, clearly recognizable image that remains readable at small sizes. The attached image becomes part of the token’s visual identity and is intended to appear on its canonical Arclans page.
Token launches are associated with the user’s Arclans wallet flow. The wallet relationship connects the launch request to its creator without requiring the public website to act as a wallet or transaction interface.
Never share private keys or recovery phrases in an X post, reply, or token description. Public launch instructions should contain only the token information needed for the launch.
Arc is the network on which Arclans launches occur. The network is a core part of every completed launch record and is shown on canonical token pages so users can distinguish the correct contract from similarly named tokens elsewhere.
When checking a token, verify both the network and the contract address. A matching name or ticker alone is not enough to establish identity.
Argus is the launch and trading venue used by Arclans. Arclans provides the X-native interface and canonical token reference, while Argus handles the underlying launch venue and market.
A completed Arclans token page links directly to that token’s Argus market. This separation keeps the informational role of Arclans distinct from trade execution.
Arclans provides sensible defaults for a standard launch. Users do not need to manually supply a long list of technical parameters simply to create a token through the normal flow.
The request still needs the identity-defining fields: a clear token name, a clear ticker, and its image. If the intended launch falls outside the standard configuration, the request must be clarified instead of silently assuming custom values.
V1 trading happens through Argus. The Arclans website does not present a simulated swap, collect trade amounts, or ask visitors to connect a wallet. Its role is to show canonical launch information and direct users to the correct venue.
Use the Trade on Argus link on a completed token page. That link is derived from the token’s canonical contract address.
Every completed Arclans launch is intended to receive a canonical page using its token contract address:
https://arclans.world/token/0x…A populated page can identify the token image, name, ticker, contract address, creator, network, launch venue, launch configuration, and launch transaction. If no completed launch is associated with an address, the page shows a neutral not-found state rather than invented token or market data.
Arclans validates launch intent before execution. Ambiguous commands are held for clarification, required fields are not guessed, and the contract address on a canonical token page should come from a completed launch.
Users should still verify the complete contract address, network, and destination before interacting with any token or external market. Arclans does not claim that a token is safe or valuable merely because it was launched through the interface.
No. Launch, create, and deploy phrasing are supported when the token name and ticker are clear.
Arclans asks for the missing field. It does not guess critical token information.
Yes. Attach one image directly to the launch post.
Trading happens through the token’s Argus market on Arc.
Use its canonical Arclans token page and compare the full contract address and network before following the Argus trading link.