Starting points, not price tags.

Because a fixed price for “an audit” is either padded to cover the worst case or quoted before anyone read the code. Scope drives price: 2,000 lines of a staking contract and 2,000 lines of a perpetuals margin engine are not the same engagement. We quote a fixed figure after a free scoping review, and that figure does not move unless the scope does.

Up: novel economic design, many external integrations, upgradeable architecture, thin documentation, low test coverage, non-EVM chains, and urgency. Down: a well-documented fork of known code, high test coverage, a tight scope, and flexible timing. Test coverage is the biggest lever a team actually controls — good tests let us spend time hunting instead of reconstructing intent.

No. Scoping takes us under two working days and produces a written scope, a trust-boundary sketch and a fixed quote. If we are not the right firm for the job, we will say so at that point rather than quoting for work we should not take.

Fifty percent to book the slot, fifty percent on delivery of the report. Remediation verification is included in that price — it is not billed separately. Retainers are billed monthly in advance. We invoice in USD and can accept stablecoins or bank transfer.

Yes, for every audit tier. Re-reviewing your fixes is part of the engagement, not an upsell — an audit that ends before the fixes are checked has not finished doing its job. What is billed separately is a full re-audit after substantial new development, because that is new code.

Yes. We reserve capacity for public-goods infrastructure and price it differently. Tell us what you are building and what you can fund — we would rather do the work at a workable number than not do it.

Say so. Sometimes the answer is a narrower scope — audit the two contracts that hold funds rather than all nine. Sometimes it is a pre-deployment assessment plus an invariant suite instead of a full audit. And sometimes the honest answer is that you should ship less code until you can afford to review the code you have.