When debugging a ZKP verifier, make sure to keep checking not just that the proof verifies on valid inputs, but also that the proof verification returns an error on invalid inputs (or with nonsensical tweaks to the verification mechanism).

So in theory could you for example instead of validating it, you would overflow not bytes but let's say for:
32-bits max -2³¹...2³¹
64 bits max -2^63...2^63
double precision floating point 1.8 x 10^308

Could you overflow (not sure if this is the right term) with a constructor and use yobibyte or bs, from there you could technically infinitely drain a process?