Fake token and impersonation claims

A copied symbol can misdirect users, but a mismatch alone does not prove who copied it or why. A useful comparison states the claimed identity and the exact conflict.

Begin with the exact claim: which network, contract/mint, domain or social channel is represented as official? Preserve the public declaration and its observation time. Compare network-bound identifiers before names, symbols and logos. If a channel claims asset A while its link points to B, record that contradiction directly instead of assigning a human identity to the channel operator.

Separate three tests: technical asset equality, issuer/channel declaration and independent corroboration of the declaration. A matching contract link can establish that two pages reference the same asset, but it does not prove their authenticity. A self-authored site and its reciprocal social account share a dependency. Archived conflicting declarations may support a mismatch finding while intent remains unknown.

Radar can be used to read a bounded asset context; this exercise generates no report. Do not turn an unresolved identity into a fake-token label merely because metadata are similar. Use claim-level states and preserve the exact mismatch that another reader can inspect.

Exact asset equality: compatible network and identifier match.

Declaration: what a publisher claims about affiliation.

Impersonation hypothesis: proposed misleading affiliation requiring evidence beyond resemblance.

ILLUSTRATIVE: a paper announcement at cedar.example declares network N / asset A. A separate page at support.example uses the same CDR symbol and says “official migration,” but links to N / asset B. No real sites, assets or humans exist; there is no independent authority proof for either page.

Mint comparison of A/B with identical CDR symbols, declaration lanes and a highlighted exact-ID conflict. No scam badge or alleged-person portrait.

Caption: Fictional identity conflict; exact mismatch does not establish an impersonator’s intent.

SPECIFICATION_ONLY — the rendered visual has not been produced or independently reviewed.

The stipulated links identify different asset labels and the second page makes a conflicting official-migration claim. Metadata similarity is observable only in this fixture.

It proves no real impersonator, malicious intent, theft or authentic issuer. A genuine migration or a mistaken link remains an alternative until admissible authorization evidence is available.

Equating a symbol with an asset; treating issuer self-links as independent identity proof; naming an alleged operator from funding; calling every mismatch fraud.

Write a claim comparison with asset, declaration, source dependency and conclusion columns. State the evidence needed to distinguish an authorized migration from misleading affiliation.

• Compare exact network/identifier first.
• Preserve the claimed affiliation and date.
• Distinguish source consistency from independence.
• Keep human identity and intent unestablished without an evidential bridge.

An asset mismatch can be reported precisely without turning resemblance or a declaration into verified identity.

• A symbol is not an asset identifier.
• A declaration and its authenticity are different claims.
• Conflicting links do not independently establish malicious intent.

P13-L02

Use the named ZECOIN tool only as an evidence-reading context. This lesson creates no tool output, account session or entitlement. Offline exercise; do not sign, deploy, approve or fund anything.

• ERC20: ERC-20 standard — Token interface and allowance semantics; the standard does not establish issuer identity or safe permissions. Boundary: Mechanism documentation only; original illustrative values are stipulated, not observations. Historical records have separately frozen provenance and explicit collection gaps.

ILLUSTRATIVE — entirely fictional offline inputs; no current observation.

null — no real observation

1

null

needs_review