-
Notifications
You must be signed in to change notification settings - Fork 29
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
Unlimited Allowances #17
Comments
Hi @Teatop1 I am not sure what you are trying to say? Are you saying that the gas fees to revoke are too high? That is out of our control but lately gas fees have plummeted |
I know exactly what you mean as I have the same issues. Your wallet has been compromised as with me soon as I send BNB from a miner to metamask it gets auto removed to some other address. The token itself is not good. Im just looking to see what I can do as I cannot change the address of the miner because if I were to reinstall a new wallet it wouldn't connect to my miner. I know it a real pain. |
Hello i have same problem.I ask for help. my wallet bsc/metamask stolen. every time I transfer funds to my wallet, they are automatically transferred to an address I don't know, emptying my bnb wallet. Can you help me please |
the same thing happen to me, but i try to find a way around it, i create a bot to revoke the hacker address but hte hacker sometime keep is wallet approve again, and we keep fighting all over again |
I am having the same issue and this is my main wallet |
On eth wallet, unlimited allowance associated with an erc20 token, wipes out every eth deposit sent to wallet address making it difficult to move out tokens. Tried revoke.cash , tac.dappstar and approved.zoke but they require sending out of 0.0eth with a network fee of $10 eth to complete txn. The impossibility of doing that is coz any eth deposit sent to that wallet address will automatically wipe out instantly deposit is confirmed, hence the eth wallet will be emptied before revoking. How can this be fixed or who can fix it
The text was updated successfully, but these errors were encountered: