SmarDex contract 0x346c…f920 on Arbitrum

0x346c0ca93354383a31d78d4944290d51f3b3f920

As of 21 Nov 2026, Trustblock’s record holds 0x346c0ca93354383a31d78d4944290d51f3b3f920 on Arbitrum as a contract of SmarDex. 1 audit report on Trustblock lists this address: Paladin, 23 Nov 2023. 6 findings in it are recorded as open or acknowledged.

Audit reports that list this address1

Each report’s scope as stored on Trustblock names this address on Arbitrum.

AuditSecurity firmDateCommit named in the reportReport
Audit Report - Smardex(Update)PaladinNot recorded (see the report)Open

Open and acknowledged findings in these reports6

2 High, 1 Medium, 3 Low. In the firm’s own words; statuses are the firm’s, from each report.

HighContract owner can benefit from own swapAudit Report - Smardex(Update) · PaladinAcknowledged

The report gives no description here.

The audit on Trustblock · Open the report
HighInvalid/malicious pair can be pushed into the factory storageAudit Report - Smardex(Update) · PaladinAcknowledged

The report gives no description here.

The audit on Trustblock · Open the report
MediumInconsistency when fetching pairs can result in issuesAudit Report - Smardex(Update) · PaladinAcknowledged

The report gives no description here.

The audit on Trustblock · Open the report
LowPairs that were unintentionally not added cannot be added once whitelist is closedAudit Report - Smardex(Update) · PaladinAcknowledged

The report gives no description here.

The audit on Trustblock · Open the report
LowPotential mismatch in frontend and Solidity calculation can result in transaction revertAudit Report - Smardex(Update) · PaladinAcknowledged

The report gives no description here.

The audit on Trustblock · Open the report
LowSafeguard might overflowAudit Report - Smardex(Update) · PaladinAcknowledged

The report gives no description here.

The audit on Trustblock · Open the report

The SmarDex security record · Every SmarDex address · This address on the explorer