zackcoburn
commented
6 years ago Yep, this is someone who has written a smart contract that trades with EtherDelta. It does two trades at once, locking in an arbitrage, and either fails on both or succeeds on both. The code isn’t verified, but such a contract would be relatively simple to write. We can tell what it does because it outputs two EtherDelta trade events. Whoever is doing this is running a script that then submits his trades through this smart contract.
On Sun, Nov 5, 2017 at 4:31 AM Sean Anderson notifications@github.com wrote:
Hey there,
So, I've got the basics of my bot up and running, but I notice that it's sometimes up to two blocks behind other bots that are trying to snipe orders mine is interested in. I've been doing my best to figure out ways to speed things up to hit an earlier block and, in doing so, I came across something interesting.
When I look at EtherScan entries for a normal trade, https://etherscan.io/tx/0xf43794b1505f8d53b9116be8800d4d8b7e8e3a16f3249cd778cbcbb41210c4ee, it has a couple of key features:
- To:Contract 0x8d12a197cb00d4747a1fe03395095ce2a5cc6819 (etherdelta_2)
- Input data is partially human readable
By contrast, a trades that I suspect is automated: https://etherscan.io/tx/0x0b4a8885086b6885116fd3d1d1c6b68915129b795b94c59afe81e43239b406c0
- Contract 0xf44072eda87ede9613b6ae1b812de8a60ade27a2
- Input data is hex buffer.
Could you shed some light on how this works?
Presumably the input data is a more raw format which means they're able to transmit less over the wire...?
How on earth does sending to another contract work, though? Have they written their own smart contract which is internally interface with EtherDelta? I'm not sure how that would be beneficial unless they've managed to do something malicious. If this is not what's occurring... an enlightening explanation would be nice!
Thanks! :D
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/etherdelta/etherdelta.github.io/issues/236, or mute the thread https://github.com/notifications/unsubscribe-auth/APEqPQzIEq8WNWUZKeHIm75Mnp34DFRqks5szYCHgaJpZM4QSUNy .
-- Zack Coburn
NOTICE: This e-mail transmission (and/or the attachments accompanying it) may contain confidential information belonging to the sender which is protected by law. The information is intended only for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this information is strictly prohibited. Any unauthorized interception of this transmission is illegal. If you have received this transmission in error, please promptly notify the sender by reply e-mail, and then destroy all copies of the transmission.
MeoMix
Hey there,
So, I've got the basics of my bot up and running, but I notice that it's sometimes up to two blocks behind other bots that are trying to snipe orders mine is interested in. I've been doing my best to figure out ways to speed things up to hit an earlier block and, in doing so, I came across something interesting.
When I look at EtherScan entries for a normal trade, https://etherscan.io/tx/0xf43794b1505f8d53b9116be8800d4d8b7e8e3a16f3249cd778cbcbb41210c4ee, it has a couple of key features:
By contrast, a trades that I suspect is automated: https://etherscan.io/tx/0x0b4a8885086b6885116fd3d1d1c6b68915129b795b94c59afe81e43239b406c0
Could you shed some light on how this works?
Presumably the input data is a more raw format which means they're able to transmit less over the wire...?
How on earth does sending to another contract work, though? Have they written their own smart contract which is internally interface with EtherDelta? I'm not sure how that would be beneficial unless they've managed to do something malicious. If this is not what's occurring... an enlightening explanation would be nice!
Thanks! :D