Protocol verification tools have grown more expressive with every paper, and harder to pick up with every release. Most end up used by the group that built them and almost nobody else. Verifpal goes the other way: it is built around the person writing the model, with a small language you can read out loud, an active attacker, and output that names the attack instead of leaving you to reconstruct it. When I published it in 2019, that choice was expensive: its paper called its own soundness argument “an incomplete, semi-formal, in-progress set of results,” and the fair verdict was that Verifpal was a teaching aid resembling a verification tool. That verdict was correct. People used it anyway, on Signal, TLS 1.3, MTProto, ProtonMail, and during the design of Zoom’s end-to-end encryption.
Seven years later, Verifpal has matured from toy to instrument. While the 2019 engine searched forward, the current engine starts from an unresolved query and searches backward through the conditions needed to violate it. Before reporting an attack, a separate validator checks that the attacker controls every modified slot and can derive every injected term, re-executes the protocol, and evaluates the query again. We prove that every reported attack is reachable in the bounded sequential-replay semantics defined here, independently of solver correctness. Because this semantics reuses a clone’s fresh values across sequential replays, it can admit witnesses that replication would exclude; the output labels such witnesses.
The language now supports key encapsulation, explicit weakening assumptions, concurrent sessions, and multiple peer configurations. We compare Verifpal’s results and counterexamples with those of ProVerif, Tamarin, and Scyther on a corpus of classical protocols. Verifpal provides bounded counterexample search rather than unbounded proofs: it complements these tools, but does not replace them.
This talk will also cover a critique against the entire field of protocol modeling and analysis tools, Verifpal included: symbolic verifiers are exploratory instruments, much closer to an interactive notebook for reasoning about a protocol than to any real assurance or proof tool, and reading a verdict from Tamarin, ProVerif or Verifpal as more than that has always been presumptuous. In order to truly advance the field of protocol modeling, it must be reframed for what it really is. Only then will we be able to realign our incentives on priorities to focus on who it can really benefit: real-world industry practitioners, not academics.