ARC MAINNET / X-NATIVE LAUNCHES
Type the idea.
Open the gate.
A mention to @argatebot turns your token concept into an Argus launch on Arc. No new trading venue. One direct path to the chain.
A launch begins
as a sentence.
State the name. Choose the ticker. Add one image. The rest of the route stays out of your way.
@argatebot launch token name Argate ticker GATEFour moments.
One destination.
Argate handles the movement from social input to a specific onchain launch. Each step has a job; none asks you to learn a new interface.
Write
Mention @argatebot with a token name and ticker. Attach the image that will identify it.
Resolve
Argate collects the details, checks the request, and prepares one defined launch action.
Execute
Your wallet submits the launch through the Argus Portal on Arc Mainnet.
Return
After confirmation, the bot replies with the contract address and its Argate page.
Built around the launch.
Nothing extra.
Conversation is the interface.
The request lives on X, alongside the people who will see the launch first.
Creator stays the creator.
The Argus transaction originates from your provisioned wallet on Arc.
Trading stays with Argus.
Argate opens the route to launch. Argus remains the venue for the token afterward.
THE NATIVE SIGNAL
$GATE_
The token associated with the Argate ecosystem. Contract details and a trading destination appear here only when verified and published.
A narrow door
by design.
A request to launch should authorize a launch, not a general-purpose wallet action.
Defined execution
Argate prepares the reviewed Argus launch function on Arc. It does not offer arbitrary contract calls.
Known limits
Each immutable X user ID may reserve at most two launch slots per UTC day.
Scoped gas support
When enabled and needed, sponsorship covers only the eligible launch gas shortfall within its cap.
Know the route
before you post.
See the command format, image requirements, wallet behavior, and what happens after confirmation.