cryptosnif
LimeWire (LMWR)
Documentary contract0x628a3b2e302c7e896acc432d2d0dd22b6cb9bc88
Unrated · 0% Evidence coverage
Operational strength remains unproven; unrated with 0% scoring coverage.
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes.
Inspect the evidenceThe source review explains documented mechanisms. Independent network checks remain pending.
Promised Scope
This dossier examines the documented purpose and mechanisms of LimeWire (LMWR) on the Ethereum network, identified by contract address 0x628a3b2e302c7e896acc432d2d0dd22b6cb9bc88. The analysis is limited to the provided documentary summaries and registry entries. It does not constitute an independent operational verification, audit, or investment recommendation. The goal is to explain the stated aims of the token within its recorded context while clearly distinguishing between project claims and verified facts.
Established Facts
The primary source for this identity is a pinned Trust Wallet Ethereum integration record. This document names LimeWire Token with the symbol LMWR and assigns it the contract address 0x628a3b2e302c7e896acc432d2d0dd22b6cb9bc88. The record specifies 18 decimal places, which concern amount representation and do not measure supply or value. The entry is labeled ERC20 and active. The community-maintained description states that LimeWire is returning as the first Web3 subscription platform for artists, brands, and creators. This description is an attributed registry claim, not an independently established issuer statement. The general ERC-20 specification defines a standard interface for fungible tokens in smart contracts. It includes functions for reading total supply and balances, executing transfers, and managing allowances. An allowance is the amount a named spender may use, and repeated approvals overwrite previous amounts. The specification also defines Transfer and Approval events. Name, symbol, and decimal metadata are optional in the standard. A wallet label establishing ERC20 compliance establishes no independently checked implementation or security.
Unknowns
No live network observation was performed. The deployed bytecode, current controllers, and actual network operation remain unverified. Independent control, beneficial ownership, usage patterns, client adoption, supply distribution, concentration, liquidity, and complete incident history are unknown. The Trust Wallet Assets README notes that inclusion does not imply a direct partnership with listed projects and that additional token information is optional and unavailable on-chain. The active status is a metadata label with no live-network validation. No deployment bytecode, controller permissions, reserve assets, or security audits have been established. The scoring coverage is 0%, resulting in an unrated status. Missing essential criteria include identity verification beyond registry labels, supply data, and control mechanisms.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The distinction between a registry claim and an operational reality remains critical. Without independent verification of the smart contract implementation, it is impossible to confirm if the token behaves according to the ERC-20 standard or if it possesses any functional utility. The lack of verified supply and control data means that economic risks and governance structures are entirely opaque. Users relying solely on this documentary record cannot assess the safety or legitimacy of the asset beyond the textual description provided by the registry maintainers.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. The available evidence consists only of community-maintained registry entries and generic technical specifications. These sources provide a documentary record but do not validate the project's claims, code integrity, or economic model. The verdict is based on the absence of independent operational verification rather than negative findings. The dossier serves as a reference for the stated purpose without implying endorsement.
Evidence That Would Change It
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to alter this assessment. Verification of the deployed bytecode against the claimed functionality is necessary. Evidence of actual user adoption, transparent supply distribution, and clear control mechanisms would reduce the current uncertainty. Independent security audits and a complete incident history report would also contribute to a more comprehensive evaluation. Until such evidence is provided, the status remains unrated and dependent on documentary records alone.
Each check earns its result.
| Check | Weight | Result |
|---|---|---|
| Exact asset identityEssential | 3% | Verification pending |
| Observable use | 15% | Verification pending |
| Economic role of the token | 10% | Verification pending |
| Supply mechanismsEssential | 10% | Verification pending |
| Ownership concentration | 8% | Verification pending |
| Value capture | 7% | Verification pending |
| Control powersEssential | 10% | Verification pending |
| Security verification | 7% | Verification pending |
| Decision process | 8% | Verification pending |
| Accountability | 7% | Verification pending |
| Incident history | 6% | Verification pending |
| Operational continuity | 4% | Verification pending |
| Execution conditions | 5% | Verification pending |
Family-specific checks: Observable usage, token necessity and dependencies.
Inspect the evidence
Sources behind this analysis
Trust Wallet: captured Ethereum record for LimeWire Token
The pinned Trust Wallet Ethereum integration record names LimeWire Token with symbol LMWR, contract 0x628a3b2e302c7e896acc432d2d0dd22b6cb9bc88 and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry ERC20 and active. Its community-maintained description states: "LimeWire, the iconic brand that helped millions of users to disover their favorite music in the early 2000's is back as the first Web3 subscription platform for artists, brands and creators." Every project, economic, partnership, performance, supply, date and adoption statement within this quoted description is an attributed registry claim, not an independently established issuer statement or operational observation. This dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The general ERC-20 specification is separate from this token implementation. Treat the generic application family as a documentary contract subject; its economic niche and scoring criteria remain unclassified and unknown.
Inspect the primary source ↗Trust Wallet Assets: blockchains/ethereum/info/info.json (bbe582d25a22)
The pinned wallet blockchain-information file names the network Ethereum, symbol ETH, and lists its project website and explorer. That named network context accompanies token records in the repository's Ethereum subtree. This identifies the documented integration network without reproducing its operation. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.
Inspect the primary source ↗Trust Wallet Assets: README.md (bbe582d25a22)
The Trust Wallet Assets README describes a community-maintained registry of token information and logos across blockchains, used by the wallet and other projects. It says additional token information is optional and unavailable on-chain. Anyone can submit assets, and inclusion does not imply a direct partnership with the listed projects. It also explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches. The README states that its scripts and documentation use the MIT license. This source is the wallet project's own integration registry, maintained with community submissions. Its project descriptions are documentary claims from that registry, not independently verified issuer statements or operational observations. The active status is a metadata label, with no live-network validation. No deployment bytecode, controller, supply, reserve, use, concentration, liquidity, security audit, incident completeness or investment return has been established.
Inspect the primary source ↗Ethereum ERC-20: pinned token interface specification
The pinned ERC-20 specification describes a standard interface for fungible tokens in smart contracts. It defines totalSupply and balanceOf reads, transfers, third-party transfers after authorization, approval and remaining allowance. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification says callers must handle a false transfer result and describes Transfer and Approval events. Name, symbol and decimal-place metadata are optional in the standard. These interface requirements describe what a conforming implementation should do. A wallet ERC20 label establishes no independently checked compliance, actual deployed implementation, controller permissions, token use, supply or security. No token transaction was performed in this review. Copyright and related rights are waived under CC0.
Inspect the primary source ↗Only original summaries are distributed. Licensed raw market data stays private.