VegaSec / Audit certificate

Audit completion certificate

VSS-20261004-QSURMWA6 · issued October 4, 2026 at 12:37 AM

signedvss-certificate-1coverage complete

Target and scope

Source
UniswapV3Pool.sol
Provenance
Etherscan verified source
Chain
ETHEREUM
Contract address
0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640
Contract name
UniswapV3Pool
Compiler
v0.7.6+commit.7338295f
File count
31
Source hash (sha256)
d47b480ad56b4f59c46ba8ee32b4545df3a99a467e4434d2c398f358765c5ddc

Public source: explorer record ↗

Analyzers

slither not recordedsemgrep 1.163.0

Findings by severity

0 critical2 high17 medium7 low19 informational45 findings3 warnings

Trust score recorded in the signed artifact: 0/100. Scores are a deterministic triage signal, not a safety guarantee.

Declared limitations

  • VegaSec runs static analysis only. Findings can include false positives, miss patterns the configured detectors do not cover, and never replace manual auditor judgement.
  • Scan ran slither and semgrep against a multi-file sandboxed bundle of 31 Solidity file(s). Imports resolve between the bundled files; dependencies outside the bundle (an npm package, another repo, a generated file) are NOT analyzed, and an unresolved import makes the run partial rather than clean.
  • Some detectors emitted warnings (see `warnings`); their output was still ingested but should be read with extra care.
  • This report is not a certification, audit attestation, or financial advice.

Integrity and signature

Integrity and authorship only. A valid signature proves these bytes came from VegaSec unchanged; it does not prove the audited contract is safe. Read the coverage status and the limitations above.

Canonical version
vss-canonical-1
Signature
Ed25519 · key vsig-2026-09
Report hash (sha256)
9b7f6f345aee15106894f27e6c36135fa05909febd90dd17eb600466648eed75
Certificate version
vss-certificate-1

Verify it without trusting this page

  1. 1. Fetch the signed bytes

    This endpoint returns the exact canonical bytes that were signed, with the signature in the response headers.

    curl -sS -D headers.txt -o report.json https://vegasec.je4ndev.com/api/public/report/VSS-20261004-QSURMWA6
  2. 2. Recompute the hash

    The sha256 of report.json must equal the x-vegasec-report-hash header and the report hash printed on this certificate.

    shasum -a 256 report.json
  3. 3. Verify the signature with the published key

    The signature is Ed25519 over sha256(report.json). The public keys are published as plain JSON; verify with any Ed25519 library using the key id from the headers.

    curl -sS https://vegasec.je4ndev.com/.well-known/vegasec-signing-keys.json
  4. 4. Or use the hosted verifier

    POST the report id to the public verification API, or open the verify page. A response of valid:true means the served bytes carry a valid signature from a published, non-revoked key.

    curl -sS -X POST https://vegasec.je4ndev.com/api/public/verify -H 'content-type: application/json' -d '{"id":"VSS-20261004-QSURMWA6"}'
  5. 5. Compare the facts on this certificate with the signed bytes

    severity_counts, analyzer_versions, generated_at, source_filename and limitations are fields of the signed preimage. Read them from report.json and compare with this certificate: a mismatch means the certificate does not describe the signed artifact.

    cat report.json
  • This certificate is generated from the signed Solidity report artifact. It states what was scanned, with which analyzers, and what the scan found.
  • It is static-analysis triage, not a certification, a formal audit attestation or financial advice. Findings can include false positives and can miss patterns the configured detectors do not cover.
  • Verification proves the artifact's integrity and authorship. It does not prove the audited contract is safe.

https://vegasec.je4ndev.com/certificate/VSS-20261004-QSURMWA6 · https://vegasec.je4ndev.com