Goat Trading audit

Sherlock31 Mar 2024Code version: not recorded (see the report)

Audit competition · firm’s term: security review

Sherlock reviewed Goat Trading (Goat Trading audit) on 31 Mar 2024: 7 findings, 0 critical; all marked fixed.

No open critical findings

Open the report Open Goat Trading’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings7

Statuses are the security firm’s own, from its report.

Severity	Open	Acknowledged	Fixed
Critical	0	0	0
High	0	0	1
Medium	0	0	6
Low	0	0	0

HighLiquidity provider fees can be stolen from any pairFixed

The report gives no description here.

MediumInitial Liquidity provider can bypass the withdrawal limitFixed

The report gives no description here.

MediumIt's possible to create pairs that cannot be taken overFixed

The report gives no description here.

MediumLegitimate pools can be taken over and the penalty is not fair.Fixed

The report gives no description here.

MediumNo check for initialEth in GoatV1Pair.takeOverPool().Fixed

The report gives no description here.

MediumSome unusual problems arise in the use of the GoatV1Factory.sol#createPair() function.Fixed

The report gives no description here.

MediumThe router is not compatible with fee on transfers tokensFixed

The report gives no description here.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of Goat Trading’s security record

Goat Trading

Audits1 audit by 1 firmLast audit Mar 2024, by Sherlock.

Critical findingsNo open critical findingsIn 1 report.

Open Goat Trading’s security record

Security firm

Sherlock

46 projects reviewed · 67 reports · latest Sep 2026

See Sherlock’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.