OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Smart Contracts

Auditing

Auditing is Callisto’s smart-contract security audit request and reporting workflow, documented in the EthereumCommonwealth GitHub repository. Requesters can submit open-source contracts for human review through GitHub Issues or an open Telegram channel, follow the request discussion, and consult completed reports in repository issues. The README describes Standard, Advanced, and Corporate review options, with the Co

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Auditing — OpenViST project profile in Smart Contracts.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use the workflow when an open-source contract is in its final development stage and ready for security review. The README recommends separate debugging and testing tools for finding and checking code issues during development.

Who it is for

  • Teams preparing an open-source smart contract for a human security review.
  • Token and NFT project developers considering the documented Standard audit path.
  • Requesters who want to track an audit discussion and consult published reports.

Documented uses

  • Submit a smart-contract audit request through GitHub Issues or Telegram.
  • Follow the request thread and locate the completed report.
  • Compare the stated review paths for standard, non-standard, and post-launch-support needs.
Before you choose

Requirements & limits

The README allows requests through GitHub Issues or an open Telegram channel. It describes paid audit options and says a first audit may be considered free following a public announcement, subject to recognition and queue handling. Published reports are available in repository issues.

  • Standard is described for common project types such as ERC20, ERC223, ERC721, ERC721A tokens, and NFTs; Advanced is for non-standard projects needing more careful review.
  • The README specifies two auditors for Standard and three for Advanced and Corporate.
  • Corporate includes bug-bounty handling and one month of technical support regarding security enhancements.
  • The README says any user can request an audit of an open-source contract, even without developer confirmation, while queue priorities determine handling.
  • Updated contracts undergo a full re-audit according to the README; it suggests modular contracts or automated tests as ways to avoid unnecessary re-audits after changes.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Provide public recognition links for an audit request

Add links to public announcements to an existing audit-request discussion for consideration for a free audit.

Before you start

  • An audit request already submitted.
  • A public announcement of the audit request on a social media platform.

Steps

  1. Announce the audit request publicly, for example on Twitter, Reddit, Bitcointalk, or Facebook.

  2. Add links to the public announcement in the audit request’s comment thread.

Expected outcome

The announcement links are available in the request discussion for the team to consider when tracking recognition and audit priority.

Guide limitations

  • The README says projects gaining more traction and social media recognition will be audited for free within the month; others may be left for the next month or processed on a paid basis. This is not a guarantee of a free audit.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
14 October 2026
Original website title
EthereumCommonwealth/Auditing · Official homepage title · retained in its source language
How we review sourcesSuggest a correction