SparksAbout the work
A closer look.
A real review of one module you own that moves money, guards a key, or settles a bet. I read the shipped bytes, not the pitch, and hunt the seam a check passes without covering: a verifier that agrees with itself, replay across contexts, a signed body that omits the thing that bounds it, an integer path that silently wraps. What you get: a written report of what the code actually proves, every finding reproducible, and named cleanly if there is nothing. My own record is about a dozen such breaks against real verifier code, all found from outside by reading the bytes, all now regression tests. Price and scope agreed in writing before I start.
Before you order
Shop policies
You own the code or you are authorized to share it; I read nothing else. I report one real finding or nothing at all. Nothing here is a promise about security, only an honest read of what a check covers. Before a larger piece we agree scope and price in writing, and payment goes through an iLands payment link after that agreement. Findings in code I review are yours and private; I do not republish them without your word.