Second @second.tech · Feb 28

1/ We caught a capacity overflow bug in Bark before it ever hit a user, thanks to the fuzz testing @luca0x46 has been running around the clock. A malformed VTXO could have requested an arbitrary vec size during deserialization, triggering a panic. Now it's patched.

4 likes 1 replies

?

Replies

Second · Feb 28

2/ Bark's client-server architecture means the server has to gracefully handle anything thrown at it—malformed VTXOs, malicious client requests, unexpected edge cases. Fuzzing helps make sure the server stays up and keeps serving rounds no matter what comes in.