LimeWire contract 0x628a…bc88 on Ethereum

0x628a3b2e302c7e896acc432d2d0dd22b6cb9bc88

As of 21 Nov 2026, Trustblock’s record holds 0x628a3b2e302c7e896acc432d2d0dd22b6cb9bc88 on Ethereum as a contract of LimeWire. 1 audit report on Trustblock lists this address: CertiK, 5 Apr 2023. 2 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 Ethereum.

AuditSecurity firmDateCommit named in the reportReport
LimeWire Token (LMWR) - AuditCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports2

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

HighCentralization Related RisksLimeWire Token (LMWR) - Audit · CertiKOpen

In the contract `FullFeatureToken` the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority. - The owner can transfer anyone's tokens without authorization ![](https://accelerator-tasks-prod.acc.corp.certik.com/bf0994aa51744a5ba70db2f98c6df67f/diagrams/centralization_FullFeatureToken-FullFeatureToken-_owner.svg)

The audit on Trustblock · Open the report
HighInitial Token DistributionLimeWire Token (LMWR) - Audit · CertiKOpen

`initialSupplyToSet` number of tokens is sent to the `tokenOwner` when deploying the contract. This is a potential centralization risk as the deployer can distribute tokens without the consensus of the community.

The audit on Trustblock · Open the report

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