cryptosnif
Pepe Unchained (PEPU)
Documentary contract0xadd39272e83895e7d3f244f696b7a25635f34234
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.
Examined promise
This dossier examines the documented purpose and mechanisms of Pepe Unchained (PEPU) on the Ethereum network. The stated aim is to provide a useful documentary explanation of the token as recorded in community-maintained registries. This examination does not constitute an independent operational verification or audit of the deployed code. It focuses on the claims found in the source summaries and their exact code versions.
Established facts
The pinned Trust Wallet Ethereum integration record identifies Pepe Unchained with the symbol PEPU and contract address 0xadd39272e83895e7d3f244f696b7a25635f34234. The record specifies 18 decimal places, which concern amount representation and do not measure supply or value. The entry is labeled ERC20 and active within the registry. The general ERC-20 specification defines a standard interface for fungible tokens in smart contracts. It requires totalSupply and balanceOf reads, transfers, and third-party transfers after authorization. An allowance is the amount a named spender may use; a repeated approval overwrites that amount. The specification also describes Transfer and Approval events. Name, symbol, and decimal-place metadata are optional in the standard. The wallet project's integration registry is 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.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity, and complete incident history remain unverified. No deployed implementation, rights, ownership, safety, supply, use, or investment outcome was checked. The general ERC-20 specification is separate from this specific token implementation. 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. The registry scope explicitly excludes brand-new tokens from submissions, so this source cannot provide an exhaustive inventory of recent launches.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The attributed registry claim states: "Pepe Unchained The future of meme coins. A Layer 2 blockchain built for Speed, Security, Low Fees–and of course–Memes." 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 explains those stated aims with that attribution only. The scoring criteria remain unclassified and unknown due to the lack of verified data.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. No public admission of operational status exists beyond the registry metadata. The missing essential criteria include identity, supply, and control. The calculated score status is unrated because the necessary evidence for independent verification has not been provided or observed.
Evidence that would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to alter this verdict. Calibration and editorial review would follow the submission of such evidence. Without these, the current unrated status and zero coverage persist. The documentation review is not an independent operational verification.
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 Pepe Unchained
The pinned Trust Wallet Ethereum integration record names Pepe Unchained with symbol PEPU, contract 0xadd39272e83895e7d3f244f696b7a25635f34234 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: "Pepe Unchained The future of meme coins. A Layer 2 blockchain built for Speed, Security, Low Fees–and of course–Memes." 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.