Dmitry Petukhov
Dmitry Petukhov
`core.serialize.VarIntSerializer` now checks for value bounds of deserialized compact size integer. If it enconters non-canonical encoding, or the size bigger than `MAX_SIZE` (0x02000000) it throws DeserializationValueBoundsError I just noticed that...
https://github.com/petertodd/python-bitcoinlib/blob/ebc85bf3f75508aba92d3a94cd024670bf25be76/bitcoin/core/__init__.py#L425 if flagbyte != 1, then it will try to deserialize as non-witness, whereas Core in `UnserializeTransaction` checks that flags are actually expected (only first bit is expected now) and...
in `CTransaction.stream_deserialize()`, if it detects that witness is signalled, it just tries to deserialize the witness and does not check if it is null. Core has a check in this...
For easier comprehension of the report, and also to improve accuracy of the display of the conditions, I decided to change the way the conditions in the paths are displayed...
Due to trivial error, the 520-byte limit was not set for witness 0 when first accessing it. This limit will be usually set in other places, too, so it is...
And add a note to the report that tells if model values are independent of each other, or inderdependent
When we know that the upgradable opcode will definitely behave like `OP_SUCCESS` - when there's no possibility that it will behave as normal, we can stop the execution with a...
I think it would be great to detect 'effect-less' code fragments like `DUP DROP DUP DROP 2DUP 2DROP DUP DROP`, because it also can help detect the bugs, just like...
> > I'm doing the first case, so hiding the impossible things would be good for me right now, but the second case is definitely a real thing too. >...