Reports batch

[davxy]

No description provided.

[clearloop]

interesting tests, hit my recent optimizations lmao

[dakk]

The table shows that jampy is failing at 1756792661, but I can't find the report in fuzz-reports/0.7.0/reports/jampy/

[sourabhniyogi]

For 1756792661, it appears this is the first case where we have invalid state transition (requiring that we respond with a post-state-root being the same as the pre-state-root) -- in this case, we believe, due to an invalid guarantee signature in the first state transition (00000027.bin) making it invalid -- and where we consider the second state transition valid. Are we misunderstanding what is going on or is there something incorrect about how our fuzzer target is dealing with the first invalid state transition?

[vekexasia]

For 1756792661, it appears this is the first case where we have invalid state transition (requiring that we respond with a post-state-root being the same as the pre-state-root) -- in this case, we believe, due to an invalid guarantee signature in the first state transition (00000027.bin) making it invalid -- and where we consider the second state transition valid. Are we misunderstanding what is going on or is there something incorrect about how our fuzzer target is dealing with the first invalid state transition?

My fuzzer had issues with it as well. but target handled it fine.

If you're replciating the traces yourself like I am doing, i now set pre_state as cur, state, try to apply 27 (failure - state remains the old one), then try to apply 28 (ok)

[sourabhniyogi]

For 1756792661, it appears this is the first case where we have invalid state transition (requiring that we respond with a post-state-root being the same as the pre-state-root) -- in this case, we believe, due to an invalid guarantee signature in the first state transition (00000027.bin) making it invalid -- and where we consider the second state transition valid. Are we misunderstanding what is going on or is there something incorrect about how our fuzzer target is dealing with the first invalid state transition?

My fuzzer had issues with it as well. but target handled it fine.

If you're replciating the traces yourself like I am doing, i now set pre_state as cur, state, try to apply 27 (failure - state remains the old one), then try to apply 28 (ok)

Ok will see how to get it to behave and implement v1 features at the same time, thank you!