Hey guys. Does anyone know how to mimic a sell on uniswap using web3.py. I know I can do a .call() on one of the uniswap swap functions, but as far as I can tell, I need to HAVE that token that im 'pretending' to sell, in my wallet and also approved before the .call() will properly function. How do I go about mimicking a buy and approve so that I can do a 'test' sell without actually having to buy the token. This is all to test for honeypots.

Like how does the likes of rugbusters do a sell check without actually owning the token in question

Do the buy,approve sell all in a single transaction. So if sell throws, buy also will fail

Cant call multiple functions in a single web3.py call

Deploy a custom contract and call that

So you think I'd have to create my own contract and call that huh

Yea

Cost a bit in gas though

Fork it on testnet and then test

Or create a general purpose contract, with customizable token address and include all functions. Then simply check if gas estimation fails or not

Thought of doing that but not sure if I can get truffle to fork via cli commands or something. Trying to automate everything

If you are trying to automate, I think this is the best approach

Include a function where you can change token address

Everything else would be the same

Yea I guess you're right. Never deployed a contract before, only played around with Web3. Gotta start somewhere!

Can you guys take this to PM please

😀

these are all old

Random generator with seed without an oracle but using dao method of seeding or user contribution but also verifying it to avoid duplicates and authenticity, this limits costs and also helps achieve the best VRF

other external data maybe added to get more randomness

good for dice, lottery and many games based apps

as people can assume others are scammers

This world, I see myself as a learner, so I take joy helping others, because through that I learn from others.. we all started as newbies at some point in time ...

Thanks man

Could you stop arguing for a moment and answer one of my questions please? hahha

ask

Well since I will have 2 BNB in the LP as a start, do you think it's a good idea limiting the maxTx to 0.2% of the total supply in the first hour and then changing it each milestone (20k marketcap - 30k - 40k etc)
And if I wanted to have a "normal" maxTx is it ok if I set it at 1% of the totalSupplY? I mean, what's a normal TX for a 1Quadrillion totalsupplY?

Another thing is the lockwallet function. Am I the only one able to lock my own wallet or is people able to write that through BSCSCAN? I need the Dev team wallets locked but I wanted control over this

Sorry my english isn't the greatest right now

2bnb for liquidity

that will finish in 1 sell

That's why I want to prevent that through the maxTX

and by the way, 4% of each transaction goes into liquidity

if you are going to sell to people, why dont you ut at least 50% into liquidity

What do you guys mean

dont make what @r0b3rt_0x said seem t be true

1 Quadrillion totalsupply

12% TAX
4% holders
4% liquidity
2% marketing wallet
2% community wallet

you mean allocation?

I am going to burn the 50% right before the launch
15% will go into a "burn" wallet which I will lock
1.5% goes towards the marketing wallet
And 2% is split between the 4 team members, so 0.5% each

Community wallet is basically a giveaway wallet, we will be doing live raffles, randomly picking 1 wallet from the holders that has minimum holdings into it

and giveaway tangile prizes such as iPad, phones etc

or just use that wallet as a buyback whale

Why would you make fun of that

I am looking for help, not for judgement

Because I am willing to burn some of it at each milestone

and I will lock it between each burn

address _burnWallet = 0x000000000000000000000000000000000000dEaD;
These most people use this for burn

Yes, I know it's that

just to show in the holders list on bscan how much they burn

this doesnt reduce your supply, well correct me if am wrong

But I am keeping 15% of totalsupply so I am able to send a certain % of that to the dead address

No function needed here, only the lock which I would be using anyway to lock the dev wallets

no I will not

Jeez can't you just help instead of inspecting all of the project 😂

🤣😂

Well since I will have 2 BNB in the LP as a start, do you think it's a good idea limiting the maxTx to 0.2% of the total supply in the first hour and then changing it each milestone (20k marketcap - 30k - 40k etc)
And if I wanted to have a "normal" maxTx is it ok if I set it at 1% of the totalSupplY? I mean, what's a normal TX for a 1Quadrillion totalsupplY?

Another thing is the lockwallet function. Am I the only one able to lock my own wallet or is people able to write that through BSCSCAN? I need the Dev team wallets locked but I wanted control over this

oh my god, here we go again

Anybody?

0.2$ will still be huge

2bnb is too small

aslo depends on your initial price

think 0.1% is better?

so with 2bnb, i suggest you make the tokens too little, like example 10m tokens in lp

What about the lock function we were talking about. Is anybody able to lock its own wallet through bscscan?

function lockTimeOfWallet() public view returns (uint256) {
return _tLocked[_msgSender()];

This means that anybody can lock their own wallets right?

why do you want to lock someone's wallet

I want to lock the devs wallets

that is terrible

oh, I see, you need to add a timelock to it

example is

plain and simple use the openzepplin, timelock, audited code is the best to use

the lock will only apply to your token contract

well, he said it

So, I am no pro as you could tell

https://bscscan.com/address/0xe5d46cc0fd592804b36f9dc6d2ed7d4d149ebd6f#writeContract

the contract is this one

please hire a dev

he will implement it

As far as I can tell it should be implemented already, am I right?

So is anyone willing to help? I am paying BNBs

Seems like it's the only way to have an answer here

You guys think it's possibile to give reflections to holders in Cardanos?

what is i update the totalSupply by writing

totalSupply -= balancesof(_burnwallet);

Or one of us can keep a list of people by userid (not username), who are actually good verified people who have delivered?

You cannot change anything in a deployed contract unless you've set it behind a proxy

That's is risky

yeah i tried it

didnt worked lol

the _Burn function reduces from total supply

on openzeppelin ERC20. if you want the 0xdead addr to be excluded

then do it from the total supply function

send to address(0);

good point

do the burn function

on the contract

it won't let you transfer to 0 normally

😂

True, just subtract from supply and add event to address(0)

i tried it wont work

I am sure it's a safemoon code

The burn is slightly different if it's safemoon code

How can I do with it then...

Deduct the amount to burn from

rTotal and tTotal

Let me get you the exact code

Zak comes highly recommended 💪

_rTotal = _rTotal.sub(_rBurnAmount);
_tTotal = _tTotal.sub(_tBurnAmount);

emit Transfer(address(this), address(0), _tBurnAmount);

to understand your question well, where is the burn coming from, burning as part of fee?