to clarify for everyone
This BNB are lost forever, stuck in contract.
If there is no function to withdraw/transfer BNB from contract to X address, you cannot move them in any way

nono i mean, how those BNB has gone on contract?

from the AddLiquidity function i guess

ohhhhh wtf

as BNB holder i say ty for this burn

haha

this add a centralizaton problem, owner can withdraw BNB on contract when he want.
But sometimes, it saves projects

agreed
at this point wish it was more centralised though :P

yeah i mean.. as developer i'm between two fires
1) i don't put it if not requested, but if something happnen, i can't do anything
2) i always insert if not requested, but the owner of project could do the "bad guy"

me personally picked 2

better safe then sorry

a colleague of mine had that same exact problem, but he totally forgot about that topic and gg for BNBs

I considered using an out-of-gas vulnerability to get CA to reduce its perceived value of 'balanceBefore' in addLiquidity
but have no experience with that

sometimes clients dont have the experience to request stuff like this, though. imo a sweep should be standard in all contracts

and the most professional projects can always rug at any time, ca is not limiting factor

out of gas will revert the transaction, you cannot alter the state of the contract.balance

100% agree

need more juice!

I had enough

then probably your wallet/whatever you're using to send the tx, calculated a wrong gasValue, 42k

What gas values should I take?

depends on the transaction you need to do, always ask the rpc node for the correct gasValue

https://ethereum.stackexchange.com/questions/19665/how-to-calculate-transaction-fee

How to do it using the web 3.py

if estimateGas or callStatic reverts, then there is another problem and it's not the gas

where self.blockchain is an istance of web3.Web3 connected to rpc

Thanks

What if instead of withdraw, u add a function to allow owner add the stuck bnb to liquidity?