-
Notifications
You must be signed in to change notification settings - Fork 890
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy the safemoon code to Remix.ethereum #45
Comments
Hello, |
it's still not a problem on the route I'm not sure where to change it, I located the route in the code but I don't know where to change it |
Someone told me that I need to add the ability to exclude some addresses from the swapAndLiquify function and add the Router and Pair addresses I'm not sure how to do it lol |
well I don't know, they said it was the question of the route but I don't know how to modify it I'm still analyzing the codes. If someone can contribute it would be good |
Has anyone solved this issue?. |
i know ist now. but i think i wont tell someone, because its make me rich |
Could you help me, please? |
So if your using the bsctestnet than you have to search that does the contract address mentioned on line#758 exists or not on the tesnet. As I converted the contract to use pancake swap instead of uniswap, and my contract didn't get deployed, was getting error |
I implanted SAFEMOON.sol connected via MetaTask in BSC Testnet. It just changed the NAME and the symbol, the tokens I didn't receive, I was reading it's a route error because of Pancakeswap that migrated to version 2.
However, the deployment continues to fail, although it tries in different ways. Does anyone have any ideas? in the Pancakeswap route code, uniswap
which line do I replace in the current code and which code should I put in and which line or lines?
The text was updated successfully, but these errors were encountered: