# Steps

**How to Launch Your Custom Tax Token on Glow in 4 Simple Steps**

Launching a token used to require complex coding and expensive developers. With Glow, you can bring your idea to life in minutes. Follow this simple guide to deploy your custom tax token to the Solana.

**Step 1: Log in**\
Getting started is frictionless. Click "log in" in the top right corner.

* Glow integrates with **Privy**, allowing you to instantly create a secure wallet using just your Email, Google, or Twitter account.&#x20;

**Step 2: Define Your Token Details** \
Give your token an identity. Fill out the basic information:

* **Token Name:** e.g., Glow Coin
* **Token Symbol:** Your ticker (e.g., GLOW)
* **Token Logo:** Upload an eye-catching image (PNG, JPG, GIF, or SVG).
* **Description:** Tell the community the story or utility behind your project (Optional, but highly recommended).

**Step 3: Configure Your Custom Taxes  (The Glow Magic)**\
This is where Glow stands out from the rest. Design your tokenomics with complete freedom:

* Set your desired **Tax** percentages.
* Configure where the tax revenue goes (e.g., dev team, buy back or holding reward).
* Note: Glow's smart contracts handle all tax routing automatically on-chain.

**Step 4: Review and Deploy** \
You’re almost there!\
Take a moment to carefully review all your settings. **(Blockchain transactions are immutable, meaning you cannot change the token name, ticker, or tax settings after deployment).**

\
Once you are 100% satisfied, click **"Create Token"**. Approve the transaction in your wallet, and boom—your token is officially live on Glow’s internal bonding curve!

***

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://glowfun.gitbook.io/glowdotfun/getting-started/steps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
