Provider directory · Technical review not assessed
0xGuard
Review the source evidence before requesting a proposal. Confirm that the assigned team, scope and deliverables match your project.
Official provider website
Evidence and engagement scope
Source check: . A provider statement is attributed information. A confirmed field refers only to the cited artifact.
- Audit networks
- EVM, Solana, NEAR, Sui, Aptos, TONProvider statement · Checked 2026-09-05. Stated on the provider website; scope must be agreed for each engagement. Source for audit networks
- Audit languages
- SolidityProvider statement · Checked 2026-09-05. Stated on the provider website; scope must be agreed for each engagement. Source for audit languages
- Services and methods
- Smart contract auditProvider statement · Checked 2026-09-05. Stated on the provider website; scope must be agreed for each engagement. Source for services and methods
- Protocol types in reviewed reports
- DEX and farming contracts, Tomb Finance forkConfirmed in cited evidence · Checked 2026-09-05. Types observed in the report examples below, not an exhaustive provider portfolio. Source for protocol types in reviewed reports
- Current pricing
- Request a scoped quote; no current price verifiedInsufficient evidence · Checked 2026-09-05. Not established from the public sources checked in this pass. Request current evidence from the provider.
- Availability
- Confirm directly with providerInsufficient evidence · Checked 2026-09-05. Not established from the public sources checked in this pass. Request current evidence from the provider.
Public report examples
These observations apply to named scopes and code revisions. They do not establish the safety of a current deployment.
OpenSwap V2
Audit ended: . Source checked .
- Protocol type
- DEX and farming contracts
- Scope
- MasterChef, OpenSwapBridge, Ownable, OpenSwapToken and UniswapV2Pair; Solidity on Binance Smart Chain.
- Code revision
- Not established in the inspected document
- Follow-up evidence
- The conclusion says all high-severity and most low-severity issues were fixed. No fix commit is specified in the inspected report.
- Limit
- Historical review. The listed contract names do not identify a current deployment or prove that all findings were closed.
MiniVerse
Audit date: . Source checked .
- Protocol type
- Tomb Finance fork
- Scope
- The report identifies Solidity contracts on Fantom and lists the checked contract addresses.
- Code revision
- Not established in the inspected document
- Follow-up evidence
- No independently traceable fix revision was established in this review. Read the findings and conclusion in the PDF.
- Limit
- A report about this fork is evidence of that engagement only; deployment changes and current operation were not checked.
Sources were checked on September 5, 2026. This is a bounded public-source review, not a technical endorsement. Report examples cover named versions only. Confirm the proposed scope, price and available team with the provider.
DSA research and technical review
0xGuard analysis: report evidence and historical limits
This provider has a structured source record. A dedicated original technical dossier has not yet been completed. See the directory-wide evidence study for the source-check method and limitations.
No independent committee assessment or technical score has been issued. The proposed review procedure requires two qualified reviewers, conflict checks, recent relevant reports and supported findings across seven criteria.
What to include in your request
- Code repository, intended revision, chain, language and protocol design.
- High-risk operations, trust assumptions, privileged roles and exclusions.
- Target start, budget, release deadline and required fix-review allowance.
- A request for three recent comparable project reports and the reviewers assigned to your project.