Audit Report On-Chain Attestation Publisher

WHAT IT DOES

This tool connects to your EVM wallet and scans audit attestation registries across different EVM chains to check audit report publication status, report hashes, IPFS references, and attestation timestamps. It reads audit report metadata including auditor identity, audit scope, report versions, and linked smart contract addresses. The tool enables you to publish audit report attestations by registering report hashes with verification registries, minting attestation tokens for published reports, and confirming that a smart contract has undergone a security audit.

HOW TO USE

Connect your Web3 wallet using the Connect button. In the Audit Registry Configurations textarea, enter each audit registry you want to query in the format name:contract:chain—one per line. For example, "AuditRegistry:0x4b8a4D1F6a2Ff6b9A6B0F4A9A8F0A9A8F0A9A8F0:1" for an audit registry on Ethereum mainnet or "VerificationDAO:0x...:137" for a registry on Polygon. Enter the audited contract address in the Contract Address field. Click "Check Published Reports" to fetch publication status and report metadata from each registry. Click "Publish Audit Attestation" to register a report hash with a registry. Results appear in the Results card with a summary of registries, published reports, and pending attestations, followed by a detailed breakdown of each registry. Click "Attest & Publish" to confirm and publish pending audit attestations.

TECHNICAL MECHANISM: MULTI-REGISTRY AUDIT ATTESTATION DETECTION

The tool uses ethers.js to interact with audit registry contracts through a tiered ABI detection system. For publication status, it attempts hasReport(address) to check if an audit report has been published for a contract. For report metadata, it attempts getReportHash(address) to retrieve the report hash and getReportMetadata(address) to fetch both hash and timestamp. The tool supports publishing through publishReport(address, bytes32) and falls back to attestReport(address, bytes32). Attestation confirmation attempts attest(address) and falls back to confirmReport(address). All operations are executed sequentially with proper error handling for each registry.

WHAT IT CANNOT SEE

This tool cannot verify the quality or completeness of audit reports—it only reads on-chain attestation status and cannot audit the audit itself. It cannot validate auditor credentials or the accuracy of audit findings—the tool trusts the registry's recorded data and cannot independently verify auditor qualifications. It cannot ensure that the published report corresponds to the deployed contract version—the report may reference a different contract version than the one currently deployed. It relies on attestation registry interfaces and may not support all audit formats or standards—if a registry uses a non-standard ABI, reports may not be detected. It cannot prevent report forgery if off-chain storage is compromised—the tool relies on the registry's recorded hashes and cannot verify the integrity of off-chain report storage.

PLEASE NOTE

This tool signs transactions to publish report hashes and mint attestation tokens—ensure you trust the audit registries you configure. All state is in-memory and resets on page reload. The tool supports EVM chains only—Ethereum, Polygon, BSC, Arbitrum, Optimism, Avalanche, Base, and Fantom. Always verify that the contract addresses you enter are correct and correspond to the registries you intend to query. Audit attestations are statements of audit completion and do not guarantee contract security—always review audit reports and conduct your own security assessment.