Take the 2-minute tour ×
Bitcoin Stack Exchange is a question and answer site for Bitcoin crypto-currency enthusiasts. It's 100% free, no registration required.

Is there a list of problematic blocks? I mean blocks in official blockchain that may cause carelessly written bitcoin client to stuck after receiving them? Can you provide a link for further reading about different type of such blocks and ways to cope with them?

Note: The most similar question I found is Is there a listing of strange or unusual scripts found in transactions?

share|improve this question

closed as not constructive by Nick ODell, Highly Irregular, cdecker, eMansipater, Lohoris Feb 8 '13 at 19:52

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

    
This question is impossible to answer without knowing what defects these hypothetical clients have. –  Nick ODell Feb 7 '13 at 8:06
    
Hi fafkulec, this question is getting votes to be closed because there's not really any way to answer it, and the bitcoin stack exchange is really designed for questions that can be answered authoritatively and concretely. This isn't any reflection on you--it's just how the site stays on track instead of drifting into a kind of general forum full of impossible-to-verify opinions. –  eMansipater Feb 8 '13 at 5:33

1 Answer 1

Lets see, I can't provide you a list with reference, but off the top of my head:

  • There are blocks that have the same coinbase transactions as previous blocks (I have heard of two, seen one so far)
  • There are transactions in a block that send a lot of coins to an address of "0" (they were intended for MtGox, but someone made a mistake in their code)
  • There are transactions that have multiple opcodes for verifying signatures
  • There are a lot of transactions that put some data on the stack and get rid of it
  • There are transactions that use other verification methods than signatures (for example, passwords)

Those are to my knowledge the cases that could cause the most trouble for poorly implemented clients

share|improve this answer

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