Finding Bugs in Tapioca with Invariant Testing
In this video I go over 2 bugs I found in the Tapioca C4 Invitational Contest with Invariant Testing
Library Encoding error
Causing a DOS
Finding these bugs is the culmination of a couple of ideas:
Stateless fuzzing to constantly test library idempotency
Using the fuzzer to find a precondition
The first MO is pretty straightforward and we recommend every client to always test their libraries as these are very simple bugs to spot and fix
The second process is more nuanced and as more manual reviewers participate in contests and audits will become a more important source of bugs
Run invariant tests in the cloud with Recon:
https://getrecon.xyz/