✨Advanced Token Launch Guide

A small but growing number of token launches are using more involved launch methods. Learn how to adjust. Knowing how to adjust can give you an edge vs other traders.

Standard procedure

Standard procedure is to add the trade methods that the smart contract uses to launch a token, to your buy swap transaction. When the Trade Method is called, for example Add Liquidity, or OpenTrading, it is seen in the Mempool and then Buyswap transaction is immediately sent.

Readyswap makes this easy.

Click the Magic Wand and Readyswap will read the contract code and implement the Trade Methods the may use for initializing trading on the contract. Done!

Variations

Uniswap V2 pools and Uniswap V3 Pools

It is still uncommon but we are starting to tokens launch using Uniswap V3 pools rather than the dominant tech, Uniswap V2 pools.

As an added complication, there are multiple kinds of V3 pools that a smart contract deployer might use.

Readyswap makes this easy too! Readyswap auto-locates all pools related to the contract Uniswap V2, and V3 options, and buy-swaps with the pool with the highest liquidity.

Private transactions

Still uncommon, but sometimes the smart contract deployer will send OpenTrading command via a private transaction that does not use the Mempool so will not be seen by any Sniper Software.

How to Identify

Go to the Deployer wallet. Find this in the basic contract information section of tufext.com.

You will then see the deployer's actions.

In the simple launch case above, click on Add liquidity which was used as the launch method.

The Timestamp was confirmed (see image above)- which tells us it was seen by the Mempool and there is no Mev/Flashbot warning.

Alternatively, you might see this:

No confirmation, which tells us it was sent via a private transaction

Or Mev Transaction / Flashbots warning, which tells us the Deployer used a flashbot service for Open Trade.

Previously automatic entries would not work with these transactions as they are not seen in the Mempool.

Readyswap has been updated to Blockscan for these methods as well, in case private transaction is used, so traders are the earliest buyers in the next block, with all other buyers doing similar.

Multiple Method Launches

Another useful method to know is when a contract can go live with multiple methods.

You can see these Multiple Methods in both Readyswap - click the magic wand or on Tufext.com

Readyswap is scanning for all but in these cases you will likely revert because 2 conditions need to be met before the trade goes live. When Readyswap sees the 1st it will execute the buy-swap and then fail.

Lets adjust when we see multiple trade methods.

Scenario 1. The developer adds Liquidity, then OpenTrades

1. Add LP method 0xf305d719 2. Then Open trade or enable trade or whatever is there 0x8a8c523c

This scenario is the most likely because usually, the developer is adding LP, then opening the trade. In this case, if you check the deployers wallet and LP has been already added you can leave it, as the Add LP method will not be called again

90% of the time they do it this way.

Scenario 2. The opposite

The Deployer Opentrade and later, just inject LP so you need to have the Add LP method in.

Easiest to check the deployer wallet for the actions he is taking.

Tomiieb says that he does not bother to scan Add LP because 90 % of the time they go with scenario one, but he actively monitors the deployer wallet to watch what they are doing so he can quickly change in case he is doing anything differently.

To remove a MethodID, like Add Liquidity. click the X in the MethodID box.

or click in the empty space which will open a dropdown list of all contract MethodID

And you can uncheck, Add liquidity (or equally check other methodIDs too)

Multi-Method Example

Following a new launch. Name: ah shit here we go again. Contract Address: 0x024cdd5fc7564d2699962567d286aaed254cbb5b Deployer Wallet: 0x72404dd13b14EfAB3e1a98D2895c6965a99e479c Tomiieb commented in real-time. Let's look at the deployer wallet

Tomiieb comment on above: You can see now deployer has started to do changes. Most likely he will inject 2-2.5 eth of lp

Tomiieb comment on above: Approve for LP add Soon he will Add LP

Yes, Add LP has been completed.

Tomiieb comment on above:

And now just the enable trade missing so scenario one (described above) is active

On Tufext.com you can see the symbol showing that LP has been added, but the token is not live yet.

Back to Readyswap

Tomiieb comment on above:

So the correct scan is this.

Since LP has already been added you don't need the Add LP method, but if you are starting to scan now, you can leave it since its already called and it will be not called again.

The deployer can do more things if he wants to, but to kick off and launch, the only thing he needs to do is enable trade using 0x8a8c523c.

Deployers call these functions by different names Open trade, Enable , trade, Start token, depend on the Contract Address. The Deployer can name these as as they want.

Often you can see they don't do an add LP - they just directly transfer.

Example Launched

Tomiieb comment on above:

There you go!

Example follow up

This is a great example of using a Multi-wallet set-up. You don't know when a token is going to launch, You can set up and scan a contract address for Open trade on Wallet 1. You will get notification when its live.

You can switch to Wallet 2 where you can start scanning, in case more tokens are on your radar from your tufext.com research or other input sources.

No Add Liquidity called, Liquidity transfer injected Variation.

Name: Azookey Contract Address: 0x06Da99b63a165F4F1D8C908eC09CAAB3047014Eb Deployer Wallet: 0xad3acf7d7ea47eda6e0a8f6fbc1fcb900b309293

You can see in this example below no Add Liquidity Function was called.

Liquidity was added via injection, the transfer of tokens and then ETH, then they called Open Trading

Video Tutorial reviewing Developer Actions

Useful to build up knowledge of deployer actions. As you monitor deployer wallets you will see deployer action patterns - which can be a source of Alpha unique to you!

Deployers launch token after token. If yousee a token that was successful (found with Tufext checksum or similar contract search from research a current unlaunched token) look into it further. Lets define success as a) didn't rug, b) got buyers, c) dipped and d) got more buyers post dip, and e) reached a good market cap. If you see the same deployer launch action patterns play out in real-time on the new token prior to launch - you can assume it's the same deployer with a new fresh wallet. This can give you confidence in a new token. How the market will receive the token is not guaranteed, but you have put the odds in your favor.

This is an edge in probability, and you can also use the previous tokens mcap high, as the potential for current token and exit target.

Review this video below to learn the steps and methods to review tokens prior to launch and build up your blockchain and new token launch knowledge.