Getting up n running

[interzone2]

Hi. Thanks for sharing your work. I'm on a steep learning curve. Adapted scheduler.py to get variables module :

import sys
import os
from brownie import *
from math import floor
from time import sleep
script_dir = os.path.dirname( __file__ )
mymodule_dir = os.path.join( script_dir, '/Users/amh17/cake_sniper')
sys.path.append( mymodule_dir )
import variables
from variables import *
import itertools
import json

Running scheduler.py returns without error but does not spin up a script asking questions that I see in the code... not sure what's next...

I am running a BSC node at quicknode.

Added this at variables.py to get web3 working?

from web3 import Web3
web3 = Web3(Web3.HTTPProvider('https://young-withered-glitter.bsc.quiknode.pro/xxxxxx/'))

Assuming this should be my BSC wallet address?
TOKEN_TO_BUY_ADDRESS = web3.toChecksumAddress(xxxx)

I have not compiled / deployed anything. And assuming these address' will/should also be my BSC wallet holding the published contracts:

TRIGGER_ADDRESS_MAINNET = "xxxx" # addy changed for public repo
TRIGGER_ADDRESS_TESTNET = "xxxx" # addy changed for public repo

Next up I'm right now looking at Brownie files to find where to add?:

# those accounts name are supposed to be registered in your eth-brownie setup files
DISPERSER_ACCOUNT = "press1"
TRIGGER_OWNER = "bsc2"
TRIGGER_ADMIN = "press1"
MANUAL_EXECUTOR_SELL_SLIPPAGE = 5 # %
MANUAL_EXECUTOR_EMMERGENCY_BUY_ALLOCATION = 1 # BNB

My logic towards getting up and running:

1. Get variables.py and scheduler.py in correct shape.
2. Compile and publish the /contracts/ .sol contracts (after fixing them up for my build)
3. Compile and publish the /dark_forester/ .sol contracts (after fixing them up for my build)
4. Run dark_forester.go
5. Do I need to create a brownie-config.yaml in root?
6. I need a deploy.py script or there is another .py file in this build performing the function?
7. I have adapted initClient.go as such with my Quiknode URLs. This works and connects. There are no contracts live as I have not deployed yet.

// geth AWS server
	geth_http = "https://young-withered-glitter.bsc.quiknode.pro/xxx/"
	geth_ipc  = "https://young-withered-glitter.bsc.quiknode.pro/xxx/" 

I realise that all of this is probably a dog's breakfast interpretation ;) I'm trying to bootstrap myself.. in.. everything.. to get this thing running.. or at least testing.. :)

Any additional tips or directions very very welcome. Thank you!

[squidsuit0x]

Honestly im with you brother, your note's we're really helpful, but seems there's still a little to go. I'll try to reach out in the discord

[cryptoismad]

What discord you reaching out to?

[LamboPoewert]

Hi, @interzone2 @SVGintern @tuttowp

did someone succeed in running this bot? i'm still struggling. you can always add me on TG @cryptohunterseu

[SpikySec]

I think you need to call the main function at the end, unless he is calling it from somewhere else. just at the end of the script add

main()

[howlingforest1]

hey, i have no clue on how to run this. can someone direct me to a video or suggest what to start on?

[saantiaguilera]

If it's worth anything, I've made a bot heavily based on this one.. If u're still struggling to make this one run, check it out https://github.com/saantiaguilera/liquidity-sniper (the pending_txs mode is the exact same as what this bot offers)

[SpikySec]

that looks very good, it would be also better to create a tutorial for that?

[SpikySec]

can we use for example moralis or ankr nodes instead of our own geth ?

[saantiaguilera]

can we use for example moralis or ankr nodes instead of our own geth ?

• The supercycled cake_sniper uses the mempool to snipe, so it's a requirement to have a node with enough throughput. You can use a moralis/ankr node, but you will most probably need to pay for high tier one or else the bot will get ratelimited in a matter of seconds.
• My liquidity sniper allows you to choose between using the mempool to snipe (which of course, has also a requirement to have a node with enough throughput as this repository) but also allows you to snipe by looking at the new blocks added to the head of the chain (which is way less performant than observing the mempool which is a real frontrunning operation, but has close to zero resource usage and you probably can run it efficiently with a free node).

Regardless of it, it's highly risky to use an external node because of:

• well, ratelimiting yourself and depending on the current state of the blockchain (if it gets congested you will have more chances of getting rate limited)
• point of failure to the node provider
• latency, security and performance degrade (you've no idea how the node is working internally, where it's located, if it has other peers connected, etc)

In any case, run the numbers though.. Check the RPM of the pending txs arriving at a free node and crunch the values, if I had to guess I would say AT LEAST 100 req/sec for bsc mainnet on a non-congested day.

that looks very good, it would be also better to create a tutorial for that?

My liquidity sniper has the usage/setup section in the readme explaining how to set it up (+ some templates and example files for you to use in case you don't understand something). If you still don't understand something throughout it, message me so I can reword it.

As far as making a video explaining it or making guides, then I'm not going to because it adds more maintenance work whenever I make changes. The readme should suffice, if not hit me up and I reword/add whatever is missing

[minkmuck]

Can you make a video showing how to setup and launch the sniper?

[np-wauxhall]

@saantiaguilera awesome job, your bot is breathetaking! I'm lucky to find it and to have proper golang knowledge) Thank you for your work, the place in the heaven is already booked for you

[SpikySec]

@saantiaguilera thank you for the explanation, the only issue I have is that I had a look on how to setup a full bsc node and I think it requires a very high resources ram/cpu in addition to the amount of data 220+ GB to sync which would be very expensive and time consuming when running it an aws/azure in addition that those providers also blocks crypto traffic.

[SpikySec]

yea and forgot to mention the 1.2 TB of storage as the data is 500GB tar.gz file, and extracting it requires another ~600GB :) how do you create a full BSC node ? are you following any tutorial other than the one from BSC ? I want to check if I am doing something wrong

[cryptoismad]

You can make the node on hetzner ax51 dedicated with nvme drives. And it costs way less than aws. If you want I can pass you the commands I use to deploy a full node on bsc

[cryptoismad]

@cryptoismad please share. Thanks in advance.

• Write to me on telegram and I pass you the txt file to get the commands @cryptoismad on telegram. Tell me you found my tg here so I remember.

[interzone2]

Thanks @saantiaguilera for this very clear and detailed build of the liquidity sniper. I'm just waiting for full node snapshot build etc. at an ax51 server I set up for this project - thanks @cryptoismad

I have a question regards the chosen token to snipe - is there a method of identifying suitable pairs at the different AMMs? In your example we are identifying the target pair before building the contract and config then we run the sniper. I expect that any script that attempted to monitor multiple pairs would be way too resource intensive? :)

[vahoo5]

Hello is there a chance to get the txt file for installing a bsc node?

[minkmuck]

Sent you a message on TG. On Nov 18, 2021, at 11:53 PM, vishal2241 ***@***.***> wrote:  @saantiaguilera<https://github.com/saantiaguilera> can we have a chat on tg @LuckyDingo_0418 or discord LuckyDingo#418 — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWRO7T4ZBNBOXHKHJV4HULDUMXQ4TANCNFSM5A33CLIA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[interzone2]

Adding to the main thread again. Question on liquidity contract discovery.

The sniper needs the address of a new liquidity token before it has had liquidity added to it. Therefore at contract creation time at that address - do some liquidity creation events come from another wallet - I guess so, i.e. not necessarily the wallet where the minting contract is? Would that make sense? I can sometimes locate addresses for new tokens after they have launched - maybe very soon after - but this is not what the sniper is after is it? It is mint contract creation prior to having liquidity added - that be fair to say?

[ws1978]

hi guys. can this bot be used as a sandwich bot or just a new token sniper bot?

[interzone2]

Hi all - been struggling with getting BSC node up and running on hetzner ax51 - the dreaded '100 blocks' away from sync perpetually..

[BrokedTV]

Hi all - been struggling with getting BSC node up and running on hetzner ax51 - the dreaded '100 blocks' away from sync perpetually..

That's a bsc issue, you can find more support and suggestions on that on the official BSC github

[interzonez]

Good call!

[komeroto]

Hi i have this issue when runing the bot any idea ?

loading sellers...
panic: runtime error: slice bounds out of range [2:0]

goroutine 1 [running]:
dark_forester/services.loadSellers(0xaf45c0, {0xb00cf0, 0xc000122000})
/root/cake_sniper/dark_forester/services/sandwicherHelper.go:54 +0x5b8
dark_forester/services.TxClassifier(0xc0003f7ec0, 0xc000138048, 0xc00010eae0)
/root/cake_sniper/dark_forester/services/txClassifier.go:36 +0xc5
main.handleTransaction(...)
/root/cake_sniper/dark_forester/dark_forester.go:138
main.StreamNewTxs(0xc0003f6180, 0xc0001181f0)
/root/cake_sniper/dark_forester/dark_forester.go:131 +0xc5a
main.main()
/root/cake_sniper/dark_forester/dark_forester.go:162 +0x125
exit status 2