2

In May 2017, an "attacker" created a contract that attempts to create many other contracts(using many JUMPDEST operations in the creation bytecode) until it runs out of gas.

I see the gas improvemnts of EIP-150, but don't see where this attack would be mitigated today.

Is this "attack" still possible?

One of the txs

Reddit thread

  • After reading the Reddit thread I still don't understand the attack vector. Who gains and how? – Lauri Peltonen Jun 25 at 17:07
  • I believe it was an attempted DoS – Bert Kellerman Jun 25 at 19:24
3

From this reddit message it was fixed in geth 1.6.5 https://www.reddit.com/r/ethereum/comments/6ene3u/the_attacker_is_back_account_related_to_devcon2/

Pull request with the fix: https://github.com/ethereum/go-ethereum/pull/14570

core/vm: Use a bitmap instead of a map for jumpdest analysis

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.