Terra Classic Stewardship Council (TCSC)
(EXPLORATORY)
A Coordination and Roadmap Framework for Terra Classic
Summary (TL;DR)
Terra Classic has strong technical contributors and an active community, but governance has become fragmented, reactive, and prone to rapid reversals. This proposal introduces the concept of a Terra Classic Stewardship Council (TCSC): a lightweight, elected coordination body whose role is to provide a public roadmap, technical signal, and coordination layer for the chain.
This proposal is exploratory. A “Yes” vote signals that the community wishes to pursue this direction in principle. If approved, the specific operational details (composition, budget size, election mechanics, reporting cadence, etc.) will be refined collaboratively during a defined debate and design period before any binding implementation proposal is submitted.
This structure does not replace governance, does not control validators, and does not introduce centralized authority. It is intended to reduce wasted effort, improve execution clarity, and provide a stable reference point for builders, validators, and external partners.
Purpose
The purpose of the TCSC is to address a persistent coordination failure on Terra Classic:
**• Repeated proposal reversals**
**• Fragmented development priorities**
**• Difficulty maintaining a durable roadmap**
**• Confusion for builders and partners about the chain’s direction**
Decentralized governance determines who gets a vote.
Stewardship determines whether direction is sustained long enough to execute.
The TCSC exists to provide coordination without compromising decentralization.
Scope & Mandate
What the TCSC does:
**• Draft and maintain a public Terra Classic roadmap**
**• Review governance proposals and publish non-binding alignment signals:**
**•** ✅ **Aligned with roadmap**
**•** ⚠️ **Needs revision**
**•** ❌ **Not aligned with roadmap**
**• Facilitate coordination between:**
**• L1 developers**
**• L2 / application builders**
**• validators**
**• ecosystem initiatives**
**• Publish:**
**• weekly status summaries**
**• monthly roadmap progress reports**
**• Serve as an official coordination interface for:**
**• builders**
**• partners**
**• ecosystem contributors**
What the TCSC explicitly does NOT do:
**•** ❌ **Cannot veto proposals**
**•** ❌ **Cannot override governance outcomes**
**•** ❌ **Cannot control validators or delegators**
**•** ❌ **Cannot deploy code**
**•** ❌ **Cannot dictate funding decisions outside of community-approved budgets**
Governance remains fully on-chain and validator/delegator driven.
Legal / Operational Authority (Explicitly Out of Scope)
This proposal does not establish a legal entity and does not grant authority to:
**• sign contracts**
**• hold trademarks**
**• represent Terra Classic in legal or commercial negotiations**
**• interface with centralized exchanges in an official legal capacity**
These functions, if desired by the community, belong to a separate legal/operational layer and would require a dedicated governance proposal with appropriate legal review.
This proposal is intentionally limited to strategic coordination and roadmap stewardship only.
Structure (Conceptual)
The final structure will be specified in a follow-up implementation proposal if this exploratory proposal passes. The initial concept is:
**• A small council of domain-specific seats:**
1\. L1 Protocol Engineering
2\. L2 / Smart Contract & dApp Ecosystem
3\. Validator Operations / Network Security
4\. Tokenomics & Monetary Policy
5\. Product & UX (wallets, tooling, onboarding)
6\. BD / Partnerships / Integrations
7\. Community Representative (user-facing perspective)
*Each seat is domain-specific to ensure technical credibility.
**• Members elected by the community**
**• Fixed-term mandates with renewal via governance**
**• Transparent reporting requirements**
Details will be refined collaboratively during the post-approval design period.
Budget & Funding (Conceptual)
If implemented, funding would be requested via standard community pool spend proposals, with:
**• predefined budget categories**
**• transparent reporting**
**• time-boxed mandates**
**• multisig custody and public accounting**
• Signers should include:
**• 2–3 council members**
**• 1 neutral validator rep**
**• 1 community/trusted auditor role (could be rotating)**
No discretionary treasury authority is created by this exploratory proposal.
Reputation & Outreach Mandate
Terra Classic faces persistent perception challenges as a “dead chain.”
If implemented, the TCSC mandate would include:
**• regular “state of the chain” updates**
**• clear public roadmap communication**
**• consistent external-facing reporting to signal that Terra Classic remains active, governed, and building**
This is not marketing hype. It is credibility signaling.
Why This Does Not Threaten Decentralization
This model introduces coordination without coercion.
Validators retain:
**• full control over governance votes**
**• full control over consensus**
**• full operational autonomy**
The TCSC provides:
**• context**
**• roadmap continuity**
**• non-binding technical and strategic signals**
This strengthens alignment between validators, delegators, and builders without removing sovereignty from any party.
Comparative Precedent
No major proof-of-stake ecosystem operates on governance alone.
Thriving chains pair decentralized consensus with structured stewardship:
**• Ethereum**
Ethereum Foundation coordinates research, grants, roadmap direction, client diversity initiatives.
Governance is decentralized. Execution is coordinated.
**• Polkadot**
Web3 Foundation + technical councils guide ecosystem development, grants, and standards.
**• Cosmos / IBC ecosystem**
Interchain Foundation funds and coordinates core stack development, SDK evolution, and interchain standards.
**• Solana**
Solana Foundation handles validator programs, grants, partnerships, and ecosystem coordination.
**• Cardano**
IOHK, Emurgo, and the Cardano Foundation coordinate development, partnerships, and roadmap evolution.
These entities do not control consensus, but they provide coordination, roadmap coherence, and execution scaffolding. Terra Classic currently lacks this layer.
Exploratory Nature & Next Steps
A “Yes” vote on this proposal indicates community interest in pursuing a stewardship and coordination framework. It does not finalize structure, budget, or membership.
If approved:
**• a defined debate and design period will follow**
**• technical, validator, and community input will be incorporated**
**• a concrete implementation proposal will be drafted collaboratively**
This approach ensures that details are shaped with broad participation rather than imposed prematurely.
Validator-Facing Rationale (Short Form)
This proposal does not reduce validator sovereignty. It does not create an executive authority, veto power, or governance override. It introduces a coordination and roadmap signal layer to reduce governance churn and execution failure.
From a validator perspective, this structure:
**• reduces repeated policy reversals**
**• improves proposal quality before they reach governance**
**• provides a stable reference framework for long-term upgrades**
**• reduces reputational friction by clarifying chain direction**
Informal coordination already exists. This proposal makes coordination transparent, auditable, time-boxed, and revocable by governance.
This is not centralization. It is execution scaffolding for a decentralized system.