cryptosnif
Ethereum Classic (ETC)
Documentary contract0x3d6545b08693dae087e957cb1180ee38b9e3c25e
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.
Promise
This dossier examines the documented purpose and mechanisms of Ethereum Classic (ETC) as recorded in the Trust Wallet registry for BNB Smart Chain. The aim is to explain the stated token-specific purpose, define the relevant technical standards, and assess the limits of documentary evidence. No independent operational verification or market analysis is included.
Established facts
The pinned Trust Wallet integration record identifies a token named Ethereum Classic with the symbol ETC on the BNB Smart Chain network. The record specifies a documentary address of 0x3d6545b08693dae087e957cb1180ee38b9e3c25e and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The entry is labeled BEP20 and active. The community-maintained description states that this is a BNB pegged Ethereum Classic token issued by Binance on Smart Chain, with a price pegged to Ethereum Classic at a ratio of 1:1. These statements are attributed registry claims, not independently established issuer statements. The Trust Wallet Assets README confirms this is a community-maintained registry where inclusion does not imply a direct partnership with listed projects. The ERC-20 specification defines a standard interface for fungible tokens, including functions for total supply, balance checks, transfers, and allowances. An allowance is the amount a named spender may use. A wallet label establishes no independently checked compliance or actual deployed implementation.
Unknowns
Present independent control, beneficial ownership, usage, client adoption, supply, concentration, liquidity, and complete incident history remain unverified. The dossier may explain stated aims but cannot confirm deployed bytecode, current controllers, or network operation. No live network observation was performed. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified.
Consequences
Documentary mechanisms alone cannot establish actual network behavior or investment outcomes. The active status is a metadata label with no live-network validation. Missing evidence does not make the project fraudulent or unsafe, but it prevents any assessment of operational strength or safety. The absence of independent verification means all claims regarding peg stability, issuance, or utility remain unproven.
Verdict
Operational strength remains unproven. The asset is unrated with 0% scoring coverage. Critical missing elements include identity verification, supply data, and control structures. The review is limited to documentary records provided by the wallet registry.
What would change it
Reproduced identity checks, independent dated network observations, and criterion-specific evidence would be required to move from an unrated status. Calibration and editorial review following such evidence would allow for a scored assessment. Until then, the dossier remains a static record of registry entries without operational validation.
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 BNB Smart Chain record for Ethereum Classic
The pinned Trust Wallet BNB Smart Chain integration record names Ethereum Classic with symbol ETC, documentary address 0x3d6545b08693dae087e957cb1180ee38b9e3c25e and 18 decimal places. Decimal places concern amount representation and do not measure supply or value. The record labels the entry BEP20 and active. Its community-maintained description states: "BNB pegged Ethereum Classic (ETC BEP20) is a token issued by Binance on Smart Chain; its price is pegged to Ethereum Classic (ETC) at a ratio of 1:1." 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. The dossier may explain those stated aims with that attribution. No deployed implementation, rights, ownership, safety, supply, use or investment outcome was checked. The generic application family identifies only a documentary token subject; its economic niche and scoring criteria remain unclassified and unknown. The general ERC-20 specification is separate from this token implementation.
Inspect the primary source ↗Trust Wallet: pinned BNB Smart Chain directory context
The pinned Trust Wallet smartchain network-context record identifies the community registry directory for BNB Smart Chain. This supplies documentary network context for entries in the same pinned directory. Promotional statements, network performance, consensus behavior, current deployment and control are not verified or admitted from this context.
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.