We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello Etherscan Team- Thank you filtering out 0 value ERC20 'sponsored' transfers initiated by another address #91 (comment)
Recently the attacker(s) started using non-zero values for random ERC20 tokens initiated by another address
Would it be possible to filter out all sponsored transactions initiated by another address?
Thank you!
The text was updated successfully, but these errors were encountered:
Hola, equipo de Etherscan: gracias por filtrar las transferencias 'patrocinadas' de ERC20 de valor 0 iniciadas por otra dirección n.º 91 (comentario) Recientemente, los atacantes comenzaron a usar valores distintos de cero para tokens ERC20 aleatorios iniciados por otra dirección ¿Sería posible filtrar todas las transacciones patrocinadas iniciadas por otra dirección? ¡Gracias!
Hola, equipo de Etherscan: gracias por filtrar las transferencias 'patrocinadas' de ERC20 de valor 0 iniciadas por otra dirección n.º 91 (comentario)
Recientemente, los atacantes comenzaron a usar valores distintos de cero para tokens ERC20 aleatorios iniciados por otra dirección
¿Sería posible filtrar todas las transacciones patrocinadas iniciadas por otra dirección?
¡Gracias!
#121 (comment)
Sorry, something went wrong.
Bueno
No branches or pull requests
Hello Etherscan Team-
Thank you filtering out 0 value ERC20 'sponsored' transfers initiated by another address #91 (comment)
Recently the attacker(s) started using non-zero values for random ERC20 tokens initiated by another address
Would it be possible to filter out all sponsored transactions initiated by another address?
Thank you!
The text was updated successfully, but these errors were encountered: