8.2.1 Method: what “partner-readiness” means in this report

Definition used here. In this report, partner-readiness is the practical ability of Terra Classic to be integrated, supported, and recommended by serious third parties (exchanges, wallets, custody providers, RPC/LCD providers, indexers, analytics, institutional desks, and credible builders) without creating outsized operational, reputational, or user-safety liabilities.

This is intentionally not a “community sentiment” or “brand vibe” discussion. It is an operational risk register:

• Can a partner confidently point users to canonical resources?

• Can a partner defend the integration decision under scrutiny (compliance, PR, user safety)?

• Can a partner reduce support burden (clear docs, clean entrypoints, incident ownership)?

• Can a partner avoid being pulled into ecosystem confusion (mislinked “official” accounts, “whitepaper” ambiguity, impersonation vectors)?

Evidence standard. This article uses the same evidence discipline as the rest of the report:

• Evidence = verifiable platform surfaces and primary-source incidents (e.g., exchange/profile links, official resource hubs, documented scam vectors, and observed “authority graph” inconsistencies).

• Interpretation = what these signals imply for partner risk and integration behavior.

8.2.2 Partner-Readiness Scorecard (0–5): rubric + current state

How to read this. The score is not “how good Terra Classic is.” It is: how safe it is for a partner to touch it—to list, integrate, recommend, or build on it—without inheriting avoidable risk.

8.2.2.1 Scoring rubric (0–5)

5 — Institution-grade

• Canonical website/docs are stable and widely mirrored across major aggregators/exchanges.

• Clear ownership of incident comms and authoritative social accounts (or formal substitutes).

• Minimal ambiguity about what is “official.”

• Low exposure to impersonation/unsafe discovery paths.

3 — Integratable but noisy

• Working integration is feasible, but partners must add disclaimers and extra support effort.

• Some conflicting entrypoints exist (docs vs “whitepaper,” legacy socials, inconsistent profiles).

• Known scam vectors require active mitigation and user education.

1 — High-friction / high-liability

• Discovery paths are unreliable; “official” surfaces are inconsistent.

• No stable authority graph; support and comms ownership unclear.

• Impersonation/unsafe onboarding risks are active enough to impact brand safety.

0 — Operationally unsafe

• Partners cannot responsibly route users because canonical entrypoints are missing or deceptive.

• The integration materially increases fraud/support exposure.

8.2.2.2 Scorecard (current state snapshot)

Dimension A — Trust surface safety (0–5): 2/5

• Evidence: High-signal scam/impersonation vectors exist and are repeatedly discussed (governance proposal phishing, fake support, fake announcements, fake validator identities).

• Interpretation: Partners must assume a non-trivial “user-loss risk tax” and increase warnings, which directly reduces partner willingness to promote or deeply integrate.

Dimension B — Communications ownership (0–5): 1/5

• Evidence: Terra Classic has no official marketing org, no official social media accounts, and no “single comms owner” that can be treated as authoritative by third parties (per confirmed constraints).

• Interpretation: In any incident, partners cannot reliably reference an “official statement.” That increases reputational exposure and support burden.

Dimension C — Identity coherence / canonical entrypoints (0–5): 2/5

• Evidence: Major market surfaces (exchange/aggregator profiles) show “website” links updated to terra-classic.io, but “whitepaper” links pointing to classic-docs (not a whitepaper), and social links pointing to legacy/incorrect accounts (e.g., old Terra/TFL accounts).

• Interpretation: The chain’s authority graph remains noisy: partners inherit ambiguity about what is canonical.

Dimension D — Legal/PR overhang (0–5): 1/5

• Evidence: Persistent public association with the 2022 collapse + ongoing narrative volatility (“meme,” “$1,” “burn salvation,” “Do Kwon legal overhang,” etc.).

• Interpretation: Many partners treat Terra Classic as “headline-sensitive.” Even if integration is technically fine, PR risk blocks deeper partnerships.

Dimension E — Operational ownership / supportability (0–5): 2/5

• Evidence: Critical surfaces exist (docs, ecosystem hub, endpoints lists, community-led resources), but ownership is not institutionally centralized; the ecosystem relies on community continuity and ad-hoc stewardship (already established across Chapters 7 and 5).

• Interpretation: For partners, this is “works today, unclear tomorrow.” That forces conservative integration posture.

Overall partner-readiness score (weighted): ~1.6/5

• What it means: Terra Classic can be integrated, but it is not partner-ready in the sense required for confident, growth-oriented distribution. Integration tends to be passive (listing/availability) rather than active (promotion, ecosystem programs, official campaigns, deep wallet integrations).

8.2.3 Reputation carry-over risk: legacy association as a “default discount”

This report does not re-litigate the collapse. The relevant point for partner-readiness is structural:

• Terra Classic inherits reputational debt from the 2022 failure and from the historical association with Terraform Labs-era identity.

• That debt persists even if the chain is technically functional and community-led.

Why this matters operationally:

• Partners that serve mainstream or regulated users face a higher burden to justify “why support this asset/chain” when the default external narrative is still collapse-adjacent.

• Even neutral integrations (e.g., a wallet adding chain support) trigger:
  support tickets, user confusion, and reputational questions.

Evidence signals inside corpus (summary, non-repetitive):

• Persistent “Do Kwon legal overhang” narrative (from narrative inventory work).

• Persistent “zombie chain / dead chain” narrative that coexists with “community-led revival” narrative (conflicting narrative set).

• Reliance on third-party and community comms rather than an institution-grade communications owner (ties directly into partner safety).

Interpretation (bounded):

• This creates a “default discount” in partner behavior:

  • Passive availability is more likely than active partnership.

  • Marketing collaboration is unlikely without a safe comms and identity layer.

  • Any volatile attention spike increases perceived PR risk (see 8.2.4).

8.2.4 Narrative volatility as operational risk: attention that doesn’t map to fundamentals

Chapter 8.1 already inventories the narratives. Here we use that inventory as a risk lens: narratives are not just “stories,” they shape partner exposure.

8.2.4.1 The pattern

Terra Classic repeatedly exhibits attention cycles that are:

• highly narrative-driven (meme dynamics, price targets, burn milestones, legal drama),

• and weakly coupled to measurable fundamentals (application activity, user growth, sustained product delivery).

This is not a moral judgment; it’s a partner-readiness problem because partners are punished by:

• sudden user influx + support burden,

• headline association,

• and reputational spillover when attention fades or reverses.

8.2.4.2 Why partners care (mechanism)

Partners optimize for:

• predictable support load,

• stable “official” routing for users,

• controlled messaging,

• and reduction of fraud/impersonation exposure.

Narrative volatility increases:

• impersonation attempts (“fake legal notice,” fake support, fake giveaways),

• misrouting (“whitepaper” confusion, wrong socials),

• and user expectations (“$1” targets, “burn salvation” inevitability).

• Recommended content: timeline that layers:

  • 1–2 attention proxies already used in earlier demand/off-chain sections (e.g., CEX volume spikes, social spikes),

  • against 1–2 fundamentals proxies from the report (e.g., on-chain activity, measurable app layer signals).

• The goal: show the decoupling visually, not argue it.

Interpretation (bounded):

• Terra Classic’s current distribution is attention-reactive, not product-led.

• That is compatible with survival, but it is hostile to partner-grade growth programs.

8.2.5 Identity coherence risk: the “authority graph” is noisy where partners need it clean

Authority graph concept (simple): If a partner lists or supports Terra Classic, users will ask:

• What is the official website?

• Where is the official documentation?

• Where is the whitepaper?

• Which social accounts are real?

• Which wallet should I use?

Partners need these answers to be:

• canonical, consistent across major surfaces, and safe to follow.

8.2.5.1 Evidence: canonical website improved, but the rest remains inconsistent

Specific, high-signal set of inconsistencies:

• Binance profile surface

  • Website links to terra-classic.io (updated).

  • “Whitepaper” links to classic-docs (not a whitepaper; Terra Classic has no whitepaper).

• CoinMarketCap profile surface

  • Website links to terra-classic.io (updated).

  • “Whitepaper” links to classic-docs (not a whitepaper).

  • Socials link to old/wrong accounts (e.g., old Terra/TFL accounts), while Terra Classic has no official socials.

• CoinGecko profile surface

  • Website links to terra-classic.io (updated).

  • Socials link to old/wrong accounts (e.g., old Terra/TFL accounts).

  • “Whitepaper” links to classic-docs (not a whitepaper).

8.2.5.2 Why this matters to partner-readiness

This is not cosmetic. It creates real integration risk:

• User misrouting risk: users follow wrong “official” socials and get scammed or misinformed.

• Support burden: partners face avoidable tickets (“why does the official link go to X?”).

• Trust deficit: institutional integrators interpret incoherent profiles as governance/comms immaturity.

• Recommended layout:

  • Left: the partner surfaces (Binance / CMC / CoinGecko / etc.)

  • Middle: what they point to (website/docs/whitepaper/socials)

  • Right: risk notes (misrouting, ambiguity, impersonation exposure)

• This becomes an “audit artifact” partners can understand instantly.

Interpretation (bounded):

• Updating “website” to terra-classic.io was necessary and positive.

• But website alone does not fix partner readiness if “whitepaper” and “social authority” remain unresolved.

8.2.6 Onboarding Integrity & Trust Surface

8.2.6.1 Executive signal

Terra Classic’s “community health” is easy to misread if we only measure forum sentiment, proposal drama, or validator politics (already covered elsewhere in this report). The unique, decision-grade lens for this chapter is different:

The community’s real health is visible in what an outsider experiences in the first 5–10 minutes:

• Can they find an authoritative entrypoint?

• Can they choose the right wallet without landing on the wrong chain?

• Can they stake without being funneled into ambiguous community tools?

• Do “official” profiles (exchanges/aggregators) reduce risk — or amplify confusion and scam surface?

The onboarding audit shows a consistent pattern: Terra Classic’s trust surface is fragmented, and that fragmentation directly increases scam/impersonation blast radius—even when core chain operations are stable.

8.2.6.2 What we mean by “community health” in this subchapter

In this chapter, community health = onboarding integrity, not “vibes.”

We define onboarding integrity as:

1. Authority clarity — newcomers can reliably identify the “default” official resources (or clearly see that no official org exists).

2. Low-risk paths — the first actions (wallet, staking, explorer, burns, governance) can be completed without stepping onto ambiguous domains or “connect wallet” traps.

3. Impersonation resistance — the ecosystem makes it hard for scammers to hijack attention using fake proposals, fake support, fake announcements, and cloned sites.

This is not a PR problem. It’s a systems design + governance ownership problem.

8.2.6.3 Trust surface map (where reputation becomes UX)

The onboarding path audit (Feb 2026) makes the trust surface tangible. In practice, newcomers encounter 5 trust layers:

1. Search layer (what ranks for “official website”, “LUNC staking”, “wallet”)

2. Directory layer (the community hub / resource index)

3. Wallet layer (where the first irreversible mistake can happen)

4. Action layer (stake, burn dashboards, “governance”, dApps)

5. Third-party profile layer (exchanges/aggregators that users treat as authoritative)

The key finding: the trust surface is wide and inconsistent, which means onboarding depends on user sophistication rather than ecosystem guardrails.

8.2.6.4 “Onboarding path audit” summary (UX meets reputation)

A) Search does not produce a single authoritative “home”

For queries like “Terra Classic official website” and “LUNC staking”, top results skew toward docs mirrors, community blogs, and third-party guides/tools—often mixing Terra Classic and Terra 2.0 references.

Implication: Terra Classic’s first impression is not “this is a coherent ecosystem,” but “I’m not sure what’s real.”

B) The “official” hub explicitly signals ambiguity

Even the hub presented as the de facto entrypoint frames itself as community-curated and emphasizes the absence of an official site—creating immediate authority ambiguity.

That transparency is honest, but it also means: there is no institutional trust anchor.

C) Wallet choice contains a high-impact misrouting risk

The wallet list flows can lead users to a wallet UI that defaults to LUNA (Terra 2.0) rather than LUNC, without a strong interstitial warning. This is a classic “wrong chain / wrong asset” onboarding failure.

D) Staking path breaks into community tooling (not a guided delegator flow)

The audit notes staking guidance that references multiple wallets and warns about APR/unbonding, but lacks a single guided “safe staking” path that reduces error.

E) “Burn dashboards” behave like dApps, not neutral analytics

Multiple burn-tracking destinations encourage wallet connections or include promotional/affiliate clutter. This blurs the line between “observe” and “act,” which is exactly where scams thrive.

F) Even the governance feedback loop looks “unofficial”

The improvement/proposals board sits on a third-party platform, is not strongly branded in-flow, and requires sign-in—raising authenticity doubts for newcomers.

8.2.6.5 “Official entrypoints” proof pack (third-party profiles amplify confusion)

This section matters because, in the absence of a foundation/marketing org, users treat exchanges and aggregators as the authority layer.

The audit documents that major third-party profile pages commonly:

• label the “website” as the community hub,

• link “whitepaper” to documentation (not a true whitepaper),

• include social links that may not reflect Terra Classic’s current reality (creating impersonation room).

High-signal example from the audit:

• CoinGecko includes social icons (Reddit/Twitter/Telegram/Discord) on the Terra Classic listing, which can create implied offici al ownership is unclear.

• CoinMarketCap provides minimal community linking and points “whitep itepaper), which produces a different but still ambiguous trust surface.

• Binance “how to buy” flow to Terra Classic resources, meaning users often stay exchange-dependent for understanding staking/burn mechanics.

Why this is not cosmetic: these pages are where new money enters. If entrypoints are inconsistent, the ecosystem’s trust boundary becomes porous.

8.2.6.6 Scam / impersonation evidence (high-signal incidents only)

We do not attempt to list every scam. We only include incidents that demonstrate structural weaknesses in Terra Classic’s onboarding trust surface.

Incident class 1 — Scam links inside governance/proposals (wallet-adjacent surface)

Classic Agora forum threads document repeated concern about scam proposals and malicious links being surfaced in governance contexts, and the community discussing mitigation approaches.

Why it matters: this is not “someone got scammed on Telegram.” This is scam adjacency to the governance UX, which many users assume is part of the “official” product surface.

Incident class 2 — Exchange email spoofing / delisting panic scams (CEX trust hijack)

A concrete example is the community discussion around fake Crypto.com delisting emails (reported by multiple users), showing how easily LUNC holders can be targeted through exchange-trust channels.

Why it matters: new/returning users often onboard through exchanges first. If the exchange-message layer is hijacked, users get pushed into rushed withdrawals, fake support links, or seed-phrase traps.

Incident class 3 — Fake “burn/news/legal notice” viral artifacts (attention hijack)

When a chain has:

• no canonical announcement channel,

• no official whitepaper,

• inconsistent third-party profile links,

…then viral “official-looking” artifacts become a highly effective scam vector. This is the same structural pattern observed in Dec 2025: attention spikes are easy; trusted routing is not.

Bottom line: Terra Classic’s biggest security vulnerability for newcomers is not the base chain. It’s trust-layer spoofing enabled by fragmented identity.

8.2.6.7 What the evidence implies

This chapter’s core conclusion is uncomfortable but operationally precise:

Terra Classic’s reputation risk is “designed in” by missing trust primitives:

• no canonical entrypoint (or not consistently propagated),

• no canonical “default stack” (wallet/explorer/staking path),

• no canonical announcement surface,

• weak separation between read-only analytics and “connect wallet” tooling,

• inconsistent third-party profile hygiene.

As a result:

• sophisticated users survive,

• newcomers churn or make errors,

• scammers get leverage from ambiguity,

• attention spikes (like Dec 2025) fail to convert into safe, sustained participation—because the funnel is leaky at the trust 85file4

8.2.6.8 Measurement hooks: how to track onboarding integrity over time

This article’s claims are grounded in an onboarding-path audit and observed inconsistencies across third-party “authority surfaces” (exchanges, aggregators, and community hubs).

To make onboarding integrity measurable (and therefore governable), the following measurement hooks can be tracked quarterly. These are not recommendations; they are proposed observables that can confirm whether the trust surface is tightening or fragmenting.

1. Entrypoint Coherence Index (ECI)
   Definition: Share of top third-party profiles (major exchanges + major aggregators) that converge on the same canonical website and explorer entrypoints, and do not route “whitepaper” to non-whitepaper documentation.
   Why it matters: Newcomers treat these profiles as official authority; inconsistent routing increases spoofing and misrouting risk.

2. Social Authority Mislink Rate (SAMR)
   Definition: Count (and %) of major profiles that link to social accounts that do not clearly represent Terra Classic today (e.g., legacy/TFL-era handles presented without context).
   Why it matters: In a no-official-socials reality, mislinks create a high-leverage impersonation zone for scammers.

3. Wallet Misrouting Risk (WMR)
   Definition: Presence of onboarding paths where a user intending Terra Classic is routed into Terra 2.0 or ambiguous default-asset contexts without a strong warning.
   Why it matters: This is a “first irreversible mistake” risk: wrong chain, wrong asset, wrong mental model.

4. First-Run Staking Clarity Score (FSCS)
   Definition: Whether a newcomer can reach a correct “stake LUNC” flow from the main entrypoint with (a) correct wallet choice, (b) correct chain context, and (c) no detours to wallet-connect “tools” during learning mode.
   Why it matters: Staking is Terra Classic’s primary product; onboarding friction here is equivalent to product friction.

5. Connect-Wallet Exposure Ratio (CWER)
   Definition: On the “burn / metrics / dashboards” route, ratio of destinations requiring wallet connection vs. read-only analytics.
   Why it matters: Mixing “observe” and “act” surfaces increases accidental wallet-connect exposure and broadens scam blast radius.

These measurement hooks create an auditable bridge between reputation (what people believe) and UX (what people experience), using evidence that is visible and repeatable.

8.2.6.9 Key takeaways

1. Terra Classic’s trust problem is not the chain; it is the trust surface.
   The onboarding audit shows the largest risk concentrates in entrypoints, routing, and authority cues—exactly where newcomers rely on shortcuts.

2. “No official website / no official socials” is honest, but it expands impersonation room.
   When authority is intentionally decentralized, the ecosystem must rely on consistent cues (domains, profiles, labels). Where those cues diverge, spoofing becomes cheaper.

3. Third-party profiles function as de facto governance outputs.
   Because many users onboard via exchanges/aggregators, the correctness of “Website / Whitepaper / Socials” links becomes a practical governance responsibility—even if the chain has no foundation.

4. Wallet and chain-context ambiguity creates “wrong chain” errors at the first critical step.
   The audit documents how a newcomer can be pushed into a Terra 2.0 context during Terra Classic onboarding, which is not a minor UX defect; it is a structural trust failure.

5. The scam pattern is consistent with fragmented identity.
   Where canonical announcements, canonical support, and canonical routing are missing, scam vectors concentrate around: (a) “official-looking” messages, (b) fake support, (c) cloned sites, and (d) governance-adjacent link traps. The evidence collected via community threads and platform reports reflects those recurring vectors.

Net implication: Terra Classic can remain technically stable while still being reputationally fragile—because the fragility lives in onboarding and authority routing, not consensus.

8.2.7 Trust infrastructure gaps: incident ownership, status, and supportability

This section addresses what partners need during normal operations and especially during incidents.

8.2.7.1 Trust infrastructure partners expect (baseline)

Most partner-grade ecosystems have at least one of:

• a canonical status page (or a canonical “incidents” channel),

• authoritative comms ownership,

• well-defined support routing for users,

• and a stable “source of truth” map.

8.2.7.2 Terra Classic reality (as evidenced across the report + constraints)

• There is no official marketing org / foundation / legal entity running communications.

• There are no official social media accounts that can issue binding statements.

• Resource hubs and documentation exist, but are community-led, and therefore not institutionally guaranteed.

8.2.7.3 Partner implication

• During incidents, exchanges/wallets cannot link to an “official statement.”

• This increases:

  • time-to-resolution confusion,

  • rumor dominance,

  • and impersonation success rate (scammers exploit silence or ambiguity).

Interpretation (bounded):

• This is a structural readiness gap: it does not require “better sentiment”; it requires hardened trust infrastructure and comms authority.

8.2.8 Stablecoin baggage and integration constraints: practical (not legal) partner blockers

This report avoids legal advice. This section is about practical partner behavior in markets where perception and compliance scrutiny matter.

8.2.8.1 Why stablecoin legacy matters even if the chain “moved on”

• Terra Classic’s brand is historically intertwined with algorithmic stablecoin failure.

• Partners that serve mainstream users will treat this as:

  • elevated reputational exposure,

  • elevated compliance/PR review friction,

  • and a reason to avoid promotional partnership, even if they keep passive markets open.

8.2.8.2 Partner implication (practical)

Even when:

• chain security is acceptable,

• staking works,

• and apps exist,

partners may still choose:

• minimal surface support (basic trading markets, limited wallet messaging),

• no co-marketing,

• no “official partnership” framing,
  because the stablecoin narrative remains a lightning rod.

Interpretation (bounded):

• This acts like a “hidden tax” on growth and distribution: it raises the threshold for partners to publicly endorse the ecosystem.

8.2.9 Key takeaways (no recommendations)

1. Terra Classic is integratable, but not partner-ready by institutional standards.
   The chain can be supported, but partners must accept extra support, routing, and reputational overhead.

2. The main blocker is not “lack of features” — it is the lack of a clean authority graph.
   When major profiles show “whitepaper” links that are not whitepapers and socials that are not authoritative, users get misrouted and partners inherit the consequences.

3. Narrative volatility behaves like operational risk, not just community culture.
   Attention spikes that don’t map to fundamentals increase impersonation attempts and support load, which makes serious partners cautious.

4. Community-led resources reduce friction, but cannot substitute for comms ownership.
   Without a recognized comms owner (or functional equivalent), incident trust defaults to rumor and impersonation dynamics.

5. Reputation carry-over remains a default discount on partnership depth.
   Even where technical integration is fine, PR sensitivity and historical association push partners toward passive support rather than active ecosystem collaboration.