8

The documentation (https://github.com/ethereum/wiki/wiki/Subtleties) states that SUICIDE becomes effective at the end of the transaction, but in block 116525, the same contract was able to SUICIDE three times in three distinct transactions:

0x7476afface26678a6c236618a7079db7ce567a213dc75652378f3580e1a10f28
0x51826f28e829cb9425dbd1c77a2c77484d04d8b02ccab05934e5885d313fbe91
0xa6c23583bba9139ca7e168328a2d15978d90dfdd61a6be697abbec1846b59e01

is it a bug that has since been fixed, or is a SUICIDE only effective after a block is complete?

  • why do you say suicide has been called 3 times ? I see it only happening in the 1st you mention but can be wrong of course – euri10 May 10 '16 at 15:13
  • ethercamp explorer and debug_traceTransaction report it for all 3 transactions (could be a bug in both of these though) – fair glu May 10 '16 at 18:51
  • I only see it showing up once on ethercamp. – Tjaden Hess May 10 '16 at 22:26
  • What version of geth are you using? I get the bug on 1.5.0, do you see it on 1.4.3? – Tjaden Hess May 10 '16 at 22:43
  • I am on 1.5.0 from ppa:ethereum/ethereum-dev, I cannot see it in ethercamp anymore, must have gotten confused at some point :/ – fair glu May 11 '16 at 6:22
4

A SUICIDE operation is effective at the end of the transaction. I can replicate the issue, so it likely is a bug in the geth traceTransaction implementation, where the other prior transactions in the block are not taken into account.

Edit: this bug has been fixed

  • I submitted an issue feel free to chime in with your geth version, etc. – Tjaden Hess May 10 '16 at 22:59
  • 1
    Added a comment in issue #2542, and, yes, that is with 1.5.0 – fair glu May 11 '16 at 6:26

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.