# Deploy SRG20 tokens

<figure><img src="/files/wEHM7LCtQbHk88ehz0Ba" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}

### <mark style="color:yellow;">You can find the SRG20 standard token contracts in the GitHub below</mark>

In the GitHub you will find the templates for SRG20\_BSC, SRG20\_ETH and for testing purposes also for testnet.

You can start developing your own project on the Surge ecosystem!
{% endhint %}

{% embed url="<https://github.com/SomeMoeCoding/Contracts/tree/main/SRG20%20standard%20CA>" %}

## <mark style="color:yellow;">NO STARTING LIQUIDITY NEEDED</mark>

*Note: the SRG20 template is a standard token with marketing and team taxes. Additional features (e.g. reflections, rewards, auto burn, auto LP etc.) have to be implemented into the SRG20 token by the dev teams.*

Variations of SRG20 standard template were already added to the Deployer Bot. [Read the next page to learn more about it!](/development/srg20-deployer-bot.md)

## <mark style="color:yellow;">Migrate your Uniswap / Pancakeswap LP to SURGE!</mark>

The process is very easy. Please contact the SURGE Team on Telegram to get technical support and guidance during the process!

## <mark style="color:yellow;">Join the Surge Developer Network!</mark>

{% embed url="<https://t.me/SurgeDevelopers>" %}


---

# 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://docs.surgeprotocol.io/development/deploy-srg20-tokens.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.