Smart contract audits for the code you plan to release.

WebThree Consulting offers smart contract security reviews as a separate service from development. Tell us what your contracts do, which version needs review and what is changing before your next release.

Discuss my contract audit

Start with a free diagnosis. The contract audit is a separate engagement.

Start with what needs reviewing.

You may be preparing a first release, changing a live contract or revisiting code that has already been reviewed. Each starts with a different question.

For a first release, describe what the contracts are meant to do. For a change, explain what is different and which parts of the product depend on it. If there was an earlier review, identify the code version it covered.

That context makes the scope discussion specific to the code you intend to use.

Make the boundaries clear.

A contract sits within a wider product. It may depend on other contracts, privileged accounts or information supplied from elsewhere. Those connections matter when deciding what a review should cover.

Bring the questions you need answered:

  • Which contracts and code version need review?
  • What other contracts or systems do they depend on?
  • Who can change settings, move funds or update the code?
  • What is already deployed, and what is still changing?
  • Are there known concerns or previous findings to discuss?

These are starting points for agreeing scope. A review of one part of a product should not be treated as a review of every connected system.

Read findings against the code they cover.

An audit provides information for a security decision. It cannot guarantee that a contract is free of vulnerabilities.

The code version and review boundaries matter when interpreting findings. If the code changes afterwards, those findings need to be understood in that context. Keep the release decision tied to what was reviewed and what has changed since.

Questions about audit fit

Is a smart contract audit separate from hiring you to build?

Yes. Smart contract auditing is a separate service. You can ask about a review without asking us to develop the product.

How much does a smart contract audit cost?

The starting point is the work to be reviewed. A single contract and a group of connected contracts present different scopes. Describe the codebase, its dependencies and any changes since an earlier review so we can discuss the scope before a quote.

Is the free diagnosis the audit?

No. The free diagnosis is the first step in discussing your needs. The contract audit is a separate engagement with its own agreed scope.

What should I have ready for the first conversation?

A description of the contracts, their language and chain, their current status and the release or change you're planning. Mention any previous review and the concerns you want to discuss. You do not need to send private code through the initial form.

Can an audit guarantee the contract is safe?

No. An audit can inform your security decisions, but it cannot eliminate every risk. Its findings relate to the code and scope reviewed.

Tell us which contracts need a review.

Start with what the contracts do and why you are seeking an audit now. We can discuss whether the review you need fits our service before you commit to an engagement.