pull down to refresh
Nope. The bugs are in validation code added on top of deserialization; actual deserialization wouldn't have those issues.
reply
Ah! I didn't realize that. Thank you.
reply
pull down to refresh
Nope. The bugs are in validation code added on top of deserialization; actual deserialization wouldn't have those issues.
Ah! I didn't realize that. Thank you.
My understanding is that the bugs (both times) were in block deserialization code. People want to write bitcoin-processing applications in a variety of languages, which means we’re going to have parsers in different languages. Having only one implementation of the full node wont change that.