13.1 Who Is Responsible for Terra Classic? Validator Duties in a Fully Decentralized Chain (Post-TFL)
13.1.1 Why this appendix exists
A recurring source of confusion in Terra Classic discussions is the gap between technical decentralization and operating responsibility.
Many participants correctly say: “Terra Classic is decentralized.”
That is true in the narrow protocol sense (no central company runs the chain today).
But a second question is usually left unanswered:
If there is no Terraform Labs, no Do Kwon, and no formal operating company — then who is responsible for the chain’s functioning, decisions, and outcomes?
This appendix answers that question directly.
It does not argue that validators are “owners” of Terra Classic in a legal-corporate sense. It argues something more precise and more important:
In a fully decentralized post-TFL reality, validators are the chain’s de facto operating authority because they control the only durable execution layer that remained: consensus, governance voting power, treasury gating, and practical coordination capacity.
That makes validator responsibility broader than “just run a node.”
13.1.2 The legacy Terra rulebook already defined validator responsibilities
Before the May 2022 collapse, old Terra Docs (Terraform Labs-era documentation) already described validator responsibilities in clear terms.
The Validator FAQ explicitly stated that a validator must:
run the correct software versions,
provide oversight and feedback on the deployment of community pool funds,
and remain active in the community.
It also clarified several governance-relevant principles that still matter today:
validators did not need to be publicly identified (identity optional),
delegators were expected to choose validators partly on reputation, voting history, uptime, and transparency,
and delegator stake could be slashed if the validator misbehaved (so validator quality directly affects delegator risk).
This matters because it proves an important point:
Even in the pre-crash hybrid era, validators were never “only infrastructure operators.”
The original design already treated them as governance actors, treasury overseers, and community stewards.
In other words, the responsibility model was always broader than server uptime.
13.1.3 What changed after the collapse: the operating center disappeared
Pre-crash Terra did not operate as a purely decentralized chain in the practical, operating sense.
It functioned as a hybrid model:
a public, permissionless Cosmos SDK / Tendermint Proof-of-Stake chain with validators, staking, and on-chain governance,
plus a strong, founder-led legal and operating center (Terraform Labs, with Do Kwon as the public face and strategic decision-maker).
That hybrid structure matters because it clarifies what exactly disappeared in May 2022.
13.1.3.1 What the hybrid model looked like before the crash
Before the collapse, Terraform Labs (TFL) and Do Kwon performed many roles that went far beyond “writing code”:
Protocol creation and core development
TFL created and launched the Terra chain and core protocol components.
TFL led major technical development, upgrades, and ecosystem-level engineering direction.
Token design and economic architecture
TFL designed the tokenomics and monetary mechanics of the LUNA/UST system.
TFL shaped and promoted the stablecoin thesis and the economic model that underpinned the ecosystem.
Roadmap, strategy, and ecosystem direction
TFL/Do Kwon effectively set the strategic direction, priorities, and narrative of the ecosystem.
Even with on-chain governance in place, the company/founder layer drove the roadmap and “what Terra is trying to become.”
Funding and capital formation
TFL raised capital, allocated resources, and financed ecosystem development.
It played the central role in ecosystem funding decisions and strategic deployment of capital.
Product and growth leadership
TFL was central to building, subsidizing, and promoting flagship applications and growth loops.
In practice, it drove adoption efforts, partnerships, and market-facing ecosystem promotion.
Public communications and representation
TFL/Do Kwon acted as the recognizable external operator and spokesperson layer.
Media, counterparties, and market participants had a clear entity/person to interface with.
Crisis and market defense functions (later phase)
The Luna Foundation Guard (LFG), while formally separate, functioned as a strategic extension of the TFL-led model, especially in peg-defense planning and reserve management.
At the same time, Terra also had genuine decentralized elements:
independent validators,
delegated staking,
on-chain governance proposals and votes,
community pool and public chain operations.
So pre-crash Terra was not “100% centralized” and not “fully decentralized.”
It was a hybrid system: decentralized infrastructure + centralized strategic/operator layer.
13.1.3.2 What disappeared after May 2022
After the Terra ecosystem collapse, the hybrid model broke.
For the purpose of this report, the following post-crash context is treated as established:
Terraform Labs no longer operates Terra Classic as a live chain operator,
Do Kwon is no longer part of chain operations,
and Terra Classic now functions without a legal entity acting as a formal operator.
This means Terra Classic retained the decentralized infrastructure layer (validators, staking, governance), but lost the centralized operating center that previously handled:
strategy,
execution coordination,
public representation,
capital formation,
ecosystem promotion,
and legal-operational interfacing.
That creates the central post-crash governance fact:
Terra Classic became more decentralized in structure, but also lost the only entity that previously concentrated execution accountability.
13.1.3.3 Why this creates a responsibility transfer problem
When the operating center disappears, the chain still needs the same categories of work to be done:
software upgrades,
governance execution,
exchange coordination,
infrastructure reliability,
documentation,
public communications,
legal/compliance interfacing,
and ecosystem positioning.
The work does not disappear. Only the operator disappears.
So the post-crash question is not whether Terra Classic needs these functions.
It is:
Who inherited them, and under what authority model?
This report’s answer remains:
Validators inherited the core execution responsibilities by default (because they control the consensus/governance machinery),
but Terra Classic did not build a replacement institutional layer (legal/operating entity, mandate framework, or accountable operator structure) to handle the non-consensus responsibilities professionally.
That missing institutional layer is one of the report’s key structural findings.
13.1.4 The key logic: responsibilities do not disappear when a legal entity disappears
A common mistake is to assume:
“No company = no one is responsible.”
That is false in system terms.
When the central operator disappears, responsibilities do not vanish. They are redistributed to whoever still controls the system’s decision and execution mechanisms.
In Terra Classic, the remaining durable mechanisms are:
Consensus (validators run and secure the chain),
Governance execution (validators vote and determine proposal outcomes),
Treasury/Community Pool gating (validator votes determine spending approval),
Operational coordination capacity (validators and core contributors coordinate upgrades, endpoints, docs, exchange readiness, and incident response in practice).
Therefore, the answer to “who inherited the functional responsibilities?” is:
Validators (collectively), with elevated responsibility for the validator subset that actually controls most voting power and execution coordination.
Delegators and investors still matter politically and economically — but they are not the primary execution layer.
13.1.5 Post-TFL validator responsibility model for Terra Classic
Below is the report’s recommended responsibility framework for Terra Classic validators based on the chain’s actual post-crash structure, not on idealized decentralization narratives.
The key principle is simple:
After TFL/Do Kwon disappeared, validators did not inherit only technical duties.
They inherited the chain’s full operating responsibility surface — either to execute directly, or to formally create/authorize accountable structures that execute on the chain’s behalf.
This distinction is essential.
Validators are not required to personally do everything (e.g., marketing, legal coordination, investor communications).
But they are responsible for ensuring these functions exist, are properly mandated, and are accountable to governance.
In other words, validators inherit responsibility in two ways:
Direct responsibility (what they must do themselves), and
Institutional responsibility (what they must create, authorize, or supervise if they cannot do it themselves).
13.1.5.1 Consensus and protocol continuity responsibility
This is the minimum, non-controversial layer.
Validators are responsible for:
running correct software versions,
maintaining uptime and signing performance,
protecting keys and infrastructure,
avoiding slashable behavior,
and keeping the chain operational.
This is directly aligned with both old Terra validator documentation and the current Terra Classic docs lineage (which still preserves the validator FAQ / responsibilities logic).
Interpretation:
In a post-TFL environment, this is necessary but not sufficient. “Chain still produces blocks” is only a baseline condition, not proof of healthy stewardship.
13.1.5.2 Governance decision responsibility
Validators are governance actors with concentrated power because:
voting power is stake-weighted,
delegator participation is low in practice,
and validators determine the outcome of most consequential proposals.
That means validators carry responsibility for:
proposal review quality,
voting rationale quality,
consistency of governance standards,
and the downstream consequences of what they approve, reject, or ignore.
Interpretation:
If governance outcomes are weak, delayed, contradictory, or non-executable, that is not a “community problem” in the abstract. It is a validator governance-quality problem.
13.1.5.3 Treasury and community-pool fiduciary-like responsibility
Old Terra docs already framed validator responsibility as oversight over community-pool fund deployment.
In Terra Classic, this duty is stronger than before because there is no central operator left to absorb execution risk.
Validators therefore have a fiduciary-like stewardship role (not necessarily a legal fiduciary role) over treasury decisions:
demand scope clarity,
demand milestone clarity,
require proof of delivery,
require post-delivery verification,
and prevent recurring budget leakage into non-compounding outcomes.
Interpretation:
Approving spend without execution controls is not neutral governance. It is negligent stewardship.
13.1.5.4 Network coordination responsibility (upgrades, exchanges, infra readiness)
Terra Classic still requires real-world coordination:
exchange upgrade coordination,
wallet compatibility readiness,
endpoint reliability,
docs updates,
release communication,
and incident handling.
No legal entity performs this centrally now.
So in practical terms, validators (and validator-adjacent contributors) inherit responsibility for:
coordination completeness,
timing discipline,
status communication,
and operational readiness across external dependencies.
Interpretation:
In a fully decentralized chain, coordination is not “someone else’s job.” It is a validator responsibility unless validators explicitly create a better authorized operating structure.
13.1.5.5 Information integrity and control-plane transparency responsibility
Old docs allowed validator pseudonymity. That may be acceptable for a narrow consensus role.
It is not enough for a post-collapse chain where validators (directly or indirectly) influence:
docs,
endpoints,
wallets,
governance outcomes,
and public ecosystem surfaces.
Validators therefore carry responsibility for information integrity, including:
clear attribution (“who runs what”),
conflict-of-interest disclosure,
distinction between official / unofficial surfaces,
accurate communication during upgrades or incidents,
and control-plane transparency (domains, docs, RPCs, wallet surfaces, infra operators).
Interpretation:
A decentralized chain can tolerate pseudonymity. It cannot tolerate opaque control over critical public infrastructure and communication surfaces.
13.1.5.6 Security assurance responsibility (chain-level, not only validator-level)
Validator duty is not limited to avoiding slashing.
In the current Terra Classic context, there is a broader chain-level security responsibility:
publish security practices,
support independent review culture,
enable auditability where feasible,
and reduce operational single points of failure.
This report treats the lack of demonstrated post-2022 chain-level audit/bounty assurance as a confirmed fact in the evidence base. That increases the burden on validators to prove security posture through process, transparency, and documented controls.
Interpretation:
“Nothing broke recently” is not security assurance. It is only absence of observed failure.
13.1.5.7 Strategy, roadmap, and vision responsibility
This is one of the most important inherited responsibilities.
Before the crash, TFL/Do Kwon set the strategic direction and public vision for the ecosystem. After the collapse, that function did not disappear — but no formal replacement was created.
As a result, validators collectively inherited responsibility for:
defining what Terra Classic is trying to become,
setting strategic priorities,
approving a realistic roadmap framework,
and ensuring continuity between funded work and long-term goals.
This does not mean validators must personally author world-class strategy documents.
It means validators are responsible for ensuring that Terra Classic has:
a credible strategic process,
a published roadmap owner (or owner structure),
execution milestones,
and measurable outcomes.
If validators do not have the skill or time to do this directly, they remain responsible for:
appointing qualified people,
funding professional planning work,
and creating an accountable structure to own roadmap production and reporting.
Interpretation:
A chain without strategy is not neutral. It is unmanaged.
13.1.5.8 Marketing, promotion, investor relations, and public positioning responsibility
This is another inherited TFL-era function that became structurally orphaned after 2022.
Pre-crash, TFL/Do Kwon handled:
ecosystem storytelling,
market positioning,
external visibility,
and counterpart communication.
Post-crash, Terra Classic still needs:
clear public positioning,
investor-facing communication,
ecosystem updates,
and relationship maintenance with external stakeholders (exchanges, wallets, builders, media, researchers).
Validators do not need to become marketers themselves.
But validators are responsible for ensuring that this function exists in a credible, accountable way.
That includes responsibility to:
define what communication is “official” vs community commentary,
mandate who can communicate on behalf of the chain (if anyone),
require disclosure and accountability for public-facing roles,
and fund/oversee professional communications where needed.
Interpretation:
If no one is authorized to represent the chain, Terra Classic becomes hard to trust, hard to evaluate, and hard to integrate.
13.1.5.9 Legal and compliance responsibility (institutional, not personal)
This area requires the clearest distinction.
Validators are not automatically the personal legal representatives of Terra Classic.
But in a post-TFL chain with no legal entity, validators still inherit institutional responsibility for legal/compliance readiness because they control whether a lawful operating interface is created.
Terra Classic still interacts with a real legal world:
exchanges,
service providers,
public communications,
trademarks/branding risks,
and potentially regulated counterparties.
Therefore validators are responsible for ensuring that Terra Classic has an adequate legal/compliance interface — which may include:
legal counsel engagement,
governance-approved legal wrappers for limited functions,
policy frameworks for official communications and counterpart contact,
and basic compliance procedures for funded public-facing activities.
This responsibility can be executed in two ways:
directly (validators coordinate and fund legal work), or
institutionally (validators create/mandate a legal entity or operator body for limited approved functions).
Interpretation:
“Decentralized” does not remove legal reality. It only changes who must create a lawful operating structure.
13.1.5.10 Funding, capital formation, and liquidity coordination responsibility
Before the crash, TFL played the primary role in capital raising, resource deployment, and ecosystem financing.
Post-crash, Terra Classic has no founder-company capital allocator.
That means validators inherited responsibility for the chain’s capital formation logic, including:
treasury funding standards,
external funding strategy (if any),
liquidity-support priorities (where governance-approved and lawful),
and capital allocation discipline across technical, product, and ecosystem work.
This does not mean validators must personally raise private capital.
It means validators are responsible for deciding whether Terra Classic:
will remain treasury-only,
will seek grants/partners/third-party capital support,
or will build a formal ecosystem development structure capable of funding growth responsibly.
If validators choose “no external capital strategy,” that is also a strategic decision — and they own the consequences.
Interpretation:
Lack of a funding model is still a model. It is a validator-owned choice unless a new mandated structure is created.
13.1.5.11 Institutional design responsibility (the missing post-crash layer)
This is the umbrella responsibility that links all others.
After TFL disappeared, Terra Classic needed not only technical survival but also institutional redesign:
what functions should remain validator-native,
what functions require professional operators,
what legal wrapper (if any) is needed,
and how accountability flows back to governance.
That redesign largely did not happen.
Nothing in the post-crash Terra Classic model inherently prevented the chain from creating a governance-approved, limited-scope operating structure (for example):
a legal entity for exchange coordination,
a communications body,
a foundation-like service entity,
or contracted operators with explicit mandates and reporting duties.
Such a structure would not make Terra Classic “centralized” if:
governance authority remained on-chain,
validator voting remained the control layer,
mandates were explicit and revocable,
and reporting remained public.
This would be a new hybrid operating model, but not the same as the pre-crash TFL model.
Pre-crash hybrid model:
strong founder/company control over strategy, capital, and ecosystem direction.
Potential post-crash hybrid model (still decentralized at the chain layer):
validator-governed chain,
with limited, governance-mandated operating entities for specific functions.
Validators therefore inherit responsibility not only to “operate the chain,” but to decide whether to build this missing institutional layer — and to be accountable if they do not.
Interpretation:
The absence of an operating entity was not an unavoidable consequence of decentralization. It was a governance choice (active or passive).
13.1.5.12 Community representation responsibility (without pretending to be “the company”)
Terra Classic has no central company spokesperson.
That does not mean external stakeholders can interact with “nobody.”
Validators therefore carry a limited but real representation duty:
not to claim ownership of Terra Classic,
but to ensure the chain is representable,
understandable,
and operable for external counterparties.
This includes:
maintaining professional public communication standards,
making governance and upgrade status legible,
reducing ambiguity around who can answer what,
and ensuring there is a documented path for counterparties to engage the ecosystem.
Interpretation:
A chain without an operator still needs an operating voice. If validators reject that role, they must build a legitimate alternative.
13.1.6 What remains the responsibility of delegators and investors
This appendix does not assign all responsibility to validators.
Delegators and investors still have responsibility for:
due diligence,
delegation choices,
governance participation when possible,
and challenging poor performance.
Old Terra docs also placed responsibility on delegators to choose validators by trust, track record, and transparency criteria.
However, the structural distinction is critical:
Delegators/investors provide capital and legitimacy,
Validators execute consensus and control the governance control plane.
So while delegators share ecosystem responsibility, validators carry higher operational responsibility because they retain the chain’s primary execution authority.
13.1.7 Decentralization does not prohibit a governance-mandated operating entity
A persistent false dichotomy in Terra Classic discussions is:
either Terra Classic is decentralized,
or Terra Classic has an entity that handles operational functions.
This is incorrect.
A decentralized chain can remain fully validator-governed at the protocol layer while still creating a limited-scope, governance-authorized operating entity for functions that require legal or professional execution, such as:
exchange relations,
official communications,
legal/compliance work,
vendor contracting,
and ecosystem operations.
The key design condition is not “no entity.”
The key condition is who controls the mandate.
If the entity’s role is:
limited,
transparent,
revocable,
and accountable to on-chain governance,
then Terra Classic remains decentralized in governance while becoming more operationally capable.
This is not a return to the pre-crash TFL model.
It is a different model: decentralized chain governance + accountable execution interfaces.
13.1.8 The post-TFL responsibility transfer test (practical rule)
A simple test can be used throughout this report and future analysis:
If a function is necessary for Terra Classic to operate or improve, and there is no legal operator to perform it, then responsibility defaults to validators — unless validators formally create, authorize, and maintain a credible alternative execution body.
Examples:
Protocol upgrades → validator responsibility (or validator-authorized delivery team with clear mandate)
Treasury spend oversight → validator responsibility
Upgrade/exchange readiness coordination → validator responsibility
Control-plane transparency (docs/endpoints/wallet disclosures) → validator responsibility
Public narrative quality for counterparties → validator responsibility (or delegated, but still accountable)
This test avoids two common failures:
pretending Terra Classic still has a central operator,
or pretending no one is accountable because the chain is decentralized.
13.1.9 Why this matters for the rest of the report
This appendix is not a philosophical note. It is a foundation for interpretation across Chapters 5, 11, and 12.
If Terra Classic is:
fully decentralized in practice (no TFL / no operator),
validator-governed in execution terms,
and structurally dependent on validator coordination,
then poor outcomes cannot be explained away as “bad luck” or “market only.”
They must be evaluated as:
governance quality outcomes,
operator-quality outcomes,
and accountability outcomes within a validator-run system.
That is why the report’s diagnosis is not anti-validator.
It is pro-accountability.
And in a post-TFL Terra Classic, accountability begins with naming the role correctly:
Validators are not just node operators.
They are the chain’s de facto custodians of execution quality.