Code is not the only contract
A protocol is a stack of promises: the code, the website terms, the docs, the public announcements, and the votes. Disputes start where those promises do not match. We read the code with technical advisors, and we read the surrounding statements the way the other side’s lawyer will.
Before a launch, we focus on the choices that create liability: who holds the admin keys, who can upgrade the contracts, how fees can change, which data feeds the system depends on, and who is actually “the team” once a foundation or a DAO is announced.
After something breaks
Hacks and hostile votes are legal events, not only technical ones. We help clients freeze what can be frozen, keep the evidence, talk to users without admitting facts that are still unknown, and decide whether to negotiate, sue, or fix the code and move on.