Smart-contract audits
Manual review of on-chain logic: accounting, access control, upgradeability, oracle and economic assumptions, and the edges where they meet.
Dakara Research is a small, senior practice. We focus on crypto: smart contracts, protocols, bridges, wallets, and the infrastructure they depend on. We'll also review any codebase where the stakes are real. Every engagement is built on reproducible evidence and a clear path to a fix.
Closer to a field notebook than a war room.
A focused set of engagements. Most clients start with one and extend as trust builds.
Manual review of on-chain logic: accounting, access control, upgradeability, oracle and economic assumptions, and the edges where they meet.
The code around the contracts: bridges, keepers, indexers, signing services, node tooling. We also check codebases that share lineage with yours, where the same class of bug tends to recur. General codebase work outside crypto too, when the stakes justify it.
We map the full attack surface and validate every finding adversarially before it reaches you. We work alongside your existing program and keep the signal high.
Practical attack-path mapping so a review starts with shared scope and the questions that actually matter.
Fix validation, regression checks, and a concise verified-fix memo your team and stakeholders can rely on.
Findings are written for the engineer who has to fix them and the lead who has to decide. No drama, no padding. They cover what was tested, what we found, why it matters, and how we verified the fix once it closed.
Under a specific share-to-asset conversion path, rounding favors the caller. A scripted sequence drains a residual amount per cycle. Patch: round against the protocol on redemption; invariant test added.
Confirm scope, success criteria, access, timelines, and how disclosure is handled.
Concise progress notes. We don't dramatize partial leads before they're validated.
Severity, affected component, exploitability, evidence, impact, and fix guidance.
Final report, remediation review, verified-fix memo, and residual-risk notes.
A short note about your protocol or codebase, the surface you're worried about, and your timeline is enough to begin. We'll tell you honestly whether we're the right fit.