cryptosnif
EN ↗
EnglishFrançaisPortuguês (Brasil)EspañolLanguage keeps this subject. Country is selected separately on service pages.
Crash test / Application / CT-XEC-001

eCash (XEC)

BNB Smart Chain · Token contract · Documentation reviewed

Documentary contract0x0ef2e7602add1733bfdb17ac3094d0421b502ca3

The verdict

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 evidence
UnratedOverall score / 100
0%Evidence coverage
13 checks pending85% coverage and 3 essential checks required for a score
2026-10-06Documentation checked · Candidate method 0.1.0

Documentation review · Reviewed · catalogue-documentary-1

The source review explains documented mechanisms. Independent network checks remain pending.

Promise

The community-maintained Trust Wallet description presents an eCash narrative involving Bitcoin Cash continuity, consensus changes, staking and subchains.

This dossier examines that attributed description alongside the recorded BNB Smart Chain token identity; the described mechanisms remain outside a live-network verification.

Established facts

The pinned Trust Wallet record names BNB pegget eCash and records the symbol XEC.

The documentary identifier for the BNB Smart Chain entry is 0x0ef2e7602add1733bfdb17ac3094d0421b502ca3 (lowercase address display).

The entry records 18 decimal places and the labels BEP20 and active; these describe registry metadata, with no live deployment check in this dossier.

The registry README describes information and logos maintained through community submissions, with optional additional information unavailable on-chain.

Registry inclusion supplies a documentary reference and does not establish a direct partnership with the listed project.

Unknowns

The central unresolved question for this dossier is how that native-network narrative relates to the BNB Smart Chain representation recorded here.

This review has not reproduced deployed bytecode, current administrative permissions or supply rules for the recorded identifier.

It also leaves beneficial ownership, measured use and execution conditions open for separate investigation.

Consequences

This reading of the documentation leaves the proposed token role to be tested against enforceable rights and observable activity.

The next question to investigate is how that native-network narrative relates to the BNB Smart Chain representation recorded here, before relying on the registry description for any operational judgment.

Verdict

The verdict for this dossier is to keep the token unrated while those operational questions remain unresolved.

The documentary description offers a starting point for investigation; this review supplies no conclusion about investment returns or current safety.

What would change it

The assessment could change after a dated, reproducible identification of the deployed asset and its current supply and control rules.

For the proposition described here, the next investigation would establish how that native-network narrative relates to the BNB Smart Chain representation recorded here, with evidence tied to the same network and identifier.

Any resulting observation would need criterion-specific review before it could contribute to a calibrated score.

02 / Crash test

Each check earns its result.

Candidate method 0.1.0. Unknown results are excluded from the score calculation.
CheckWeightResult
Exact asset identityEssential3%Verification pending
Observable use15%Verification pending
Economic role of the token10%Verification pending
Supply mechanismsEssential10%Verification pending
Ownership concentration8%Verification pending
Value capture7%Verification pending
Control powersEssential10%Verification pending
Security verification7%Verification pending
Decision process8%Verification pending
Accountability7%Verification pending
Incident history6%Verification pending
Operational continuity4%Verification pending
Execution conditions5%Verification pending

Family-specific checks: Observable usage, token necessity and dependencies.

03 / Evidence

Inspect the evidence

Sources behind this analysis

Trust Wallet: captured BNB Smart Chain record for BNB pegget eCash

The pinned Trust Wallet BNB Smart Chain integration record names BNB pegget eCash with symbol XEC, documentary address 0x0ef2e7602add1733bfdb17ac3094d0421b502ca3 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: "eCash is the natural continuation of the Bitcoin Cash project. eCash follows through on key promises such as the innovative Avalanche consensus layer while also introducing concepts such as staking, fork-free network upgrades, and subchains." 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.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 14fa117c0aa8aad636a8525b0ff07b8bdbf185298faf8de7d29ec91e1454182b

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.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 9888dd19b8ace07b4a705771770ab5140129ba43ec4ce6e95932dd63af204278

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.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 51fc8f690972c850271ca0a6086516eae5ed411e94982fcae6534a4d08fccd73

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.

Retrieved . Scope: documentation. Current network operation remains unverified.

Inspect the primary source ↗

Snapshot SHA-256: 50d0bdc535ed8987ac5c124cb5f9c39606806c97e909aae66ef4b747dd9c93dd

Only original summaries are distributed. Licensed raw market data stays private.

Continue the investigation