# Terra Classic Website: Full Agent Context > Independent, community-maintained, open-source information website for Terra Classic, LUNC, and USTC. Terra-classic.money is an independent, community-maintained information website for Terra Classic. It is not the official Terra Classic website, not a governance authority, and not financial advice. Listings and links are informational only and do not imply endorsement, audit, custody safety, investment merit, or official status. ## Terra Classic Website Agent Context Independent, community-maintained, open-source information website for Terra Classic, LUNC, and USTC. ### Mission Provide a neutral, transparent, source-aware public information layer for Terra Classic users, builders, delegators, contributors, media, partners, and external observers. ### Canonical Pages - [Terra Classic - Independent, community-maintained information website for Terra Classic, LUNC & USTC](https://terra-classic.money/) - Independent community-maintained information website for Terra Classic: explore LUNC and USTC ecosystem resources, markets, roadmap, decentralization, open work, and builder links. - [Terra Classic Ecosystem Directory](https://terra-classic.money/ecosystem.html) - Explore neutral Terra Classic ecosystem links: applications, wallets, bridges, validators, developer resources, infrastructure providers, and community tools. - [Terra Classic LUNC and USTC Markets](https://terra-classic.money/markets.html) - Explore neutral Terra Classic LUNC and USTC market links across centralized exchanges and decentralized swap routes. - [Terra Classic Roadmap](https://terra-classic.money/roadmap.html) - Explore the Terra Classic decentralized roadmap: public L1 milestones and clearly labeled project-submitted L2 and community roadmap entries. - [Terra Classic Decentralization](https://terra-classic.money/decentralization.html) - A detailed, source-aware guide to Terra Classic decentralization, validators, delegators, governance, and community-owned infrastructure. - [Open Work for Terra Classic Builders](https://terra-classic.money/open-work.html) - Explore open Terra Classic work packages that independent builders, software houses, and contributors can prepare proposals or quotes for. - [Open Work Details for Terra Classic Builders](https://terra-classic.money/open-work-detail.html) - Review a Terra Classic open work package before preparing a public proposal or quote for community discussion and governance. - [About terra-classic.money](https://terra-classic.money/about.html) - Learn how terra-classic.money works as an independent, open-source, community-maintained information website for Terra Classic. - [Website analytics | terra-classic.money](https://terra-classic.money/analytics.html) - Public aggregate website analytics for terra-classic.money, generated from Google Analytics 4 through GitHub Actions. - [Privacy Policy - terra-classic.money](https://terra-classic.money/privacy.html) - Privacy Policy for terra-classic.money, the independent, community-maintained information website for Terra Classic. - [Terra Classic brand assets - terra-classic.money](https://terra-classic.money/brand-assets.html) - Download Terra Classic brand assets, including full logos, standalone signs, and key visuals for ecosystem communication and community materials. ### Machine-Readable Files - [site-index](https://terra-classic.money/data/site-index.json) - Canonical route, locale, metadata, and data-file index. - [ecosystem](https://terra-classic.money/data/ecosystem.json) - Neutral Terra Classic ecosystem directory records. - [markets](https://terra-classic.money/data/markets.json) - Informational LUNC and USTC market route records. - [roadmap](https://terra-classic.money/data/roadmap.json) - Public Terra Classic roadmap rows and milestones. - [open-work](https://terra-classic.money/data/open-work.json) - Open work packages, deliverables, acceptance criteria, and quote requirements. - [policies](https://terra-classic.money/data/policies.json) - Neutrality, contribution, support, and safety policy summary. - [faq](https://terra-classic.money/data/faq.json) - FAQ questions and answers from public site sections. ### Important Boundaries - The website is independent, community-maintained, and open-source. - The website is not currently the official Terra Classic website. - The website is informational only and does not provide financial, legal, tax, staking, validator, trading, or investment advice. - Core ecosystem, market, roadmap, and open-work content should remain neutral, source-aware, and free from hidden rankings or validator favoritism. - Paid or sponsored listings must be clearly separated from neutral core ecosystem content. - Corrections, listing suggestions, translations, and improvements should route through public GitHub contribution workflows. - Users should verify linked resources, wallet flows, contracts, market venues, and governance claims before acting. ## Terra Classic Website Policy Context Terra-classic.money is an independent, community-maintained information website for Terra Classic. It is not the official Terra Classic website, not a governance authority, and not financial advice. Listings and links are informational only and do not imply endorsement, audit, custody safety, investment merit, or official status. ### Policy Summary - **independent:** The website is independent, community-maintained, and open-source. - **unofficial:** The website is not currently the official Terra Classic website. - **informationalOnly:** The website is informational only and does not provide financial, legal, tax, staking, validator, trading, or investment advice. - **neutrality:** Core ecosystem, market, roadmap, and open-work content should remain neutral, source-aware, and free from hidden rankings or validator favoritism. - **paidSeparation:** Paid or sponsored listings must be clearly separated from neutral core ecosystem content. - **contributionModel:** Corrections, listing suggestions, translations, and improvements should route through public GitHub contribution workflows. - **userProtection:** Users should verify linked resources, wallet flows, contracts, market venues, and governance claims before acting. ### Open Source Principles - **Transparent by default:** Content changes, corrections, and improvements should be traceable through public contribution workflows. - **Neutral toward ecosystem participants:** The website should not secretly favor validators, builders, projects, tokens, contributors, or sponsors. - **Open to contributors:** Anyone can suggest improvements through the public contribution process. - **Source-aware:** Where possible, claims should be supported by direct links, public documentation, governance records, repositories, dashboards, or other verifiable sources. - **User-protective:** The website should distinguish between official, unofficial, community-made, paid, experimental, unverified, and risky resources. - **No financial advice:** The website provides information. It does not recommend buying, selling, staking, investing in, or using any asset, validator, project, product, or service. ### Contribution Paths - **Corrections:** Report outdated information, broken links, wrong labels, unclear descriptions, or missing context. - **New resources:** Suggest wallets, explorers, dashboards, governance resources, developer tools, documentation, or ecosystem entries. - **Translations:** Help make Terra Classic easier to understand for users across different languages and regions. - **Content improvements:** Improve explanations, add missing context, simplify complex sections, or help make the website more accessible. - **Open work packages:** Review public work requests and prepare proposals, quotes, or implementation plans for ecosystem needs. - **Design and UX feedback:** Suggest interface improvements that make the site clearer, safer, and easier to use. ### Donation And Support Boundaries - It does not buy rankings. - It does not buy validator preference. - It does not buy ecosystem placement. - It does not buy editorial control. - It does not buy governance status. - It does not buy official recognition. ## Terra Classic Website FAQ Context Terra-classic.money is an independent, community-maintained information website for Terra Classic. It is not the official Terra Classic website, not a governance authority, and not financial advice. Listings and links are informational only and do not imply endorsement, audit, custody safety, investment merit, or official status. ### Getting started #### What is Terra Classic? Terra Classic is a community-governed Layer-1 blockchain powered by LUNC. Validators produce blocks, delegators help secure the network through staking, and governance directs how the protocol evolves over time. #### Who controls Terra Classic? No single company, foundation, or individual controls Terra Classic. It is governed through on-chain proposals, validator voting, delegator participation, and community-led development. #### How do I start using Terra Classic? Start by choosing a compatible wallet, funding it with LUNC or another supported asset, and exploring staking, governance, transfers, and ecosystem applications. For larger balances, use strong wallet hygiene and consider hardware-wallet flows where available. #### What are transaction fees like? Terra Classic transactions use gas fees, and many transfers may also interact with the chain’s tax/burn logic depending on current governance parameters. Always check the fee shown in your wallet before confirming a transaction. #### Where can I track network activity and stats? You can track Terra Classic through block explorers, dashboards, governance tools, staking interfaces, and public network endpoints. For builders and operators, Terra Classic also exposes RPC, LCD, FCD, and gRPC endpoints for development and light workloads. ### Tokens and native assets #### What is LUNC used for? LUNC is Terra Classic’s native staking and governance asset. It is used to pay fees, secure the chain through delegation, participate in governance, and coordinate economic activity across the network. #### What is USTC? Is it a stablecoin? USTC is a native Terra Classic asset with historical stablecoin origins, but today it should be treated as a freely traded crypto asset, not as a guaranteed $1 redeemable stablecoin. Any future stable-asset design should be evaluated by its collateral model, liquidity, governance approval, and live market behavior. #### What makes Terra Classic’s asset layer unique? Terra Classic combines LUNC as a native speculative, staking, and governance asset with a broader multi-currency asset vision. Its roadmap includes fiat-pegged stable assets designed to expand settlement, FX-like utility, and on-chain liquidity over time. #### Are those stablecoins live today? Not all proposed Terra Classic stable assets are live as fully collateralized, production-ready assets today. The rollout is phased, with collateralization, liquidity, governance, and technical safeguards expected to mature step by step. ### Staking and rewards #### How does staking work on Terra Classic? You delegate LUNC to a validator, which helps secure the network and participate in consensus. Validators take a commission on rewards, while delegators receive the remaining rewards proportional to their delegated stake. #### What is the unbonding period? When you undelegate staked LUNC, it enters an unbonding period of 21 days and does not earn rewards during that time. #### What are the risks of staking? Main staking risks include validator downtime, slashing, poor validator performance, governance inactivity, commission changes, and market volatility. Your LUNC remains yours when delegated, but validator behavior can still affect rewards and risk exposure. #### How do I choose a validator? Look for validators with strong uptime, transparent communication, reasonable commission, active governance participation, and clear infrastructure practices. Diversifying across multiple reliable validators can reduce concentration risk. #### Can I move my stake without unbonding? Yes, redelegation lets you move bonded LUNC from one validator to another without waiting through the full unbonding period, subject to chain rules and cooldown limits. ### Governance and community #### How does Terra Classic governance work? Community members submit proposals, deposits bring proposals into voting, and validators and delegators vote on-chain. Passed proposals can update parameters, fund initiatives, trigger upgrades, or guide ecosystem direction. #### Why does governance matter for investors and institutions? Governance determines the rules that shape fees, upgrades, treasury spending, validator incentives, and ecosystem priorities. For investors and institutions, governance quality is a signal of whether Terra Classic can coordinate, execute, and manage risk credibly. #### What is the Community Pool / treasury used for? The Community Pool can fund protocol work, infrastructure, ecosystem tooling, public goods, audits, documentation, and growth initiatives—when proposals pass through governance. Strong proposals should define scope, budget, milestones, owners, and proof of delivery. #### How can I participate if I’m not technical? You can stake, vote, choose responsible validators, review proposals, join community discussions, report broken information, support builders, and help educate new users. Delegators can also override their validator’s governance vote if they want to vote directly. ### Burns and deflation mechanics #### What is the burn tax? The burn tax is an on-chain mechanism that can route part of eligible transaction activity toward reducing supply. Its rate, scope, exemptions, and implementation details are controlled by governance and should always be checked against current chain parameters. #### Does burning guarantee price increases? No. Burns can reduce supply, but price depends on demand, liquidity, utility, market structure, and broader conditions. Burns are strongest when paired with real usage, sustainable volume, and product adoption. #### How can I verify burns? Burns can be verified on-chain through explorers, burn addresses, tax module data, and community dashboards. For serious analysis, always use source data rather than screenshots or social claims. ### Ecosystem and use cases #### What can I do on Terra Classic today? You can send assets, stake LUNC, vote in governance, interact with wallets, explore DEX liquidity, use ecosystem applications, and build smart-contract products. The network also supports public endpoints and developer tooling for teams building on top of it. #### What are “Layer-2 projects” on Terra Classic? Layer-2 projects are independent ecosystem projects built around Terra Classic that may have their own tokens, tools, applications, and communities. They expand what users can do beyond the base chain while still drawing value from Terra Classic’s network and brand gravity. #### Is Terra Classic interoperable with other chains? Yes. Terra Classic supports interchain connectivity through IBC-related modules and cross-chain infrastructure, allowing assets and applications to connect across the broader Cosmos ecosystem where channels and relayers are active. ### Builders and developers #### What technology stack does Terra Classic use? Terra Classic uses Cosmos-SDK-style infrastructure, Tendermint/CometBFT-style consensus, CosmWasm smart contracts, IBC modules, and developer-facing RPC/LCD/gRPC endpoints. Builders can also use TypeScript tooling such as CosmES for app development. #### Can I deploy smart contracts on Terra Classic? Yes. Terra Classic supports WebAssembly smart contracts powered by CosmWasm, including contract upload, instantiation, execution, querying, and migration patterns. #### What languages and tools should developers use? Smart contracts are typically written in Rust because it has the most mature CosmWasm tooling. Front-end and app integrations can use TypeScript tooling, CosmES, wallet controllers, RPC/LCD endpoints, and localnet workflows for testing. #### How do I get my app listed or featured? Prepare a clear project profile with links, contracts, documentation, category, security notes, and live status, then submit it through the relevant ecosystem or website-maintainer channel. Projects with working products, transparent ownership, and verifiable on-chain activity should be prioritized. #### Are grants or funding available? Funding can be requested through Terra Classic governance or community-led initiatives, but it is not automatic. Strong funding requests should include milestones, budget, delivery owners, proof of work, maintenance plans, and measurable ecosystem impact. ### Institutions and public-sector partners #### Why would an institution consider Terra Classic? Terra Classic offers public settlement, community governance, global accessibility, low-friction blockchain infrastructure, and a native asset ecosystem with potential for payments, staking, DeFi, and multi-currency settlement experiments. #### How can we integrate Terra Classic for payments or settlement? A typical integration starts with wallet/custody setup, compliance review, RPC/LCD or node access, transaction monitoring, accounting flows, and a limited pilot. For production workloads, institutions should avoid relying only on public endpoints and should use dedicated infrastructure or run their own nodes. #### We want to introduce a new fiat-pegged stablecoin on Terra Classic—how does that work? Start with a clear asset proposal: target currency, issuer/collateral model, mint/redeem logic, liquidity plan, oracle assumptions, risk controls, legal/compliance perimeter, and governance path. From there, the community can evaluate whether the asset is technically safe, economically useful, and aligned with Terra Classic’s long-term direction. #### Is Terra Classic “compliant”? Terra Classic is a public, permissionless blockchain; compliance usually sits at the application, issuer, exchange, custody, and institutional-integration layer. Any regulated use case should be reviewed with qualified legal and compliance professionals before launch. ### Security, reliability, and risk #### How secure is Terra Classic? Terra Classic is secured by delegated proof-of-stake validators, staking incentives, governance-controlled upgrades, and slashing rules for validator misbehavior. Like every public blockchain, it also depends on responsible validators, secure infrastructure, audited apps, careful key management, and honest risk disclosure. #### What are the biggest risks users should understand? Key risks include market volatility, smart-contract bugs, validator slashing, bridge risk, governance changes, phishing, fake websites, poor wallet hygiene, and low-liquidity markets. Always verify links, contracts, proposals, and wallet prompts before signing. #### How are upgrades handled? Terra Classic uses governance and coordinated validator execution to update protocol software and modules. Upgrade quality depends not only on code, but also on testing, validator readiness, communication, and post-upgrade monitoring. #### Where do I report a bug or security issue? For documentation issues, open a GitHub issue or submit a pull request. For code, infrastructure, or security-sensitive issues, use the relevant project repository or maintainer channel and avoid posting exploitable details publicly before maintainers can respond. ### Practical reminders #### Is this website financial advice? No. This website is for education, onboarding, and ecosystem navigation only. It does not provide financial, investment, legal, tax, or compliance advice. #### What’s the best way to stay up to date? Follow Terra Classic governance, validator communications, developer repositories, ecosystem channels, documentation updates, and trusted analytics dashboards. The most reliable signal is not hype—it is shipped work, verifiable data, and transparent execution. ### About terra-classic.money #### Is terra-classic.money the official Terra Classic website? No. Terra-classic.money is an independent community project. If the Terra Classic community and governance later choose to adopt it, that decision can be proposed through governance. #### Who controls this website? The website is designed to be maintained through public contribution workflows, transparent correction rules, and independent community maintenance rather than validator control. #### Can validators contribute? Yes. Validators can suggest corrections, open issues, contribute content, and submit pull requests like any other community participant. Validator status should not create special editorial control. #### Do donations buy influence? No. Donations do not buy editorial control, ecosystem placement, validator preference, listing approval, roadmap inclusion, governance status, or official recognition. #### Are paid L2 listings endorsements? No. Paid L2 listings are promotional entries in a separated discovery surface. They are not endorsements, audits, recommendations, guarantees, or official Terra Classic status. ## Terra Classic Open Work Agent Context Terra-classic.money is an independent, community-maintained information website for Terra Classic. It is not the official Terra Classic website, not a governance authority, and not financial advice. Listings and links are informational only and do not imply endorsement, audit, custody safety, investment merit, or official status. ### Post-Quantum Roadmap implementation strategy Status: OPEN FOR PROPOSALS Category: Long-term protocol security Detail: https://terra-classic.money/open-work-detail.html?work=post-quantum-roadmap-implementation-strategy Prepare an RFC-aligned implementation strategy for Terra Classic's post-quantum roadmap: from RFC freeze support and CometBFT feasibility work to consensus-path prototyping, wallet/tx hybrid planning, IBC counterparty coordination, audit gates, and production migration decision packages. #### Deliverables - RFC-to-implementation mapping that separates Phase Omega, consensus path, wallet/tx path, client ecosystem, audit gates, and governance decision points. - Feasibility and architecture plan for a PQ-enabled consensus path, including CometBFT, Cosmos SDK, wasmd, validator key binding, deterministic cutover logic, and no-go criteria. - IBC and migration risk package covering counterparty-chain readiness, relayer requirements, fallback operating modes, route-impact communication, and external dependency tracking. - Milestone-based implementation, testnet, audit, documentation, and governance proposal plan that can be quoted, reviewed, and executed without implying immediate mainnet migration. #### Acceptance Criteria - The work explicitly follows the Post-Quantum Roadmap RFC and does not claim Terra Classic is already post-quantum, quantum resistant, or production-ready for PQ migration. - The plan clearly distinguishes RFC freeze, feasibility study, prototype work, migration-component work, audit gates, and production Go/No-Go decisions. - Consensus-path scope treats ML-DSA, validator key binding, safety/liveness, deterministic upgrade behavior, and larger-signature resource impact as security-critical review areas. - No mainnet cutover, wallet/tx activation, or client rollout is proposed without prior governance authorization, testnet evidence, independent review, and explicit residual-risk disclosure. #### Quote Requirements - A discovery phase that validates the RFC assumptions, identifies missing technical evidence, and defines which phase or work package the quote covers first. - A milestone plan with separate pricing for research, architecture, prototype, testnet operation, audit coordination, documentation, and governance-support work. - Relevant experience with Cosmos SDK, CometBFT, IBC, validator infrastructure, wallet signing flows, cryptographic migrations, or post-quantum signature schemes. - A risk register covering IBC counterparty dependency, relayer concentration, validator participation, key management, performance costs, audit blockers, and stop conditions. ### Forex Protocol implementation Status: OPEN FOR PROPOSALS Category: Stablecoins Detail: https://terra-classic.money/open-work-detail.html?work=forex-protocol-implementation Build the production-ready implementation plan and first deployable version of Terra Classic's Forex Protocol: a collateral-backed stable-asset system designed to bring transparent, on-chain fiat-pegged currencies to Terra Classic, starting with EUTC. #### Deliverables - Technical architecture for the Forex Protocol MVP, including minting, redemption, vault accounting, oracle pricing, fee handling, and DEX liquidity interaction. - Implementation plan for EUTC as the first supported fiat-pegged asset, including collateral handling for approved stablecoin inputs. - Smart contract or module-level implementation proposal with clear deployment path, testnet plan, and governance dependencies. - Public developer documentation explaining system logic, user flows, contract/module interfaces, risk assumptions, and operational controls. #### Acceptance Criteria - The system design clearly separates collateral, user balances, protocol fees, reserves, and any LUNC buyback or vault logic. - All minting, redemption, fee, oracle, and DEX-routing assumptions are documented with source-backed parameters and testable scenarios. - The MVP includes circuit breakers, rate limits, emergency procedures, and governance-controlled configuration where required. - No mainnet deployment is proposed without testnet validation, security review, reproducible deployment instructions, and public technical documentation. #### Quote Requirements - A discovery phase that validates the existing proposal, identifies technical gaps, and defines the safest MVP scope. - A milestone-based delivery plan covering architecture, implementation, testing, documentation, review, and deployment support. - Relevant DeFi, Cosmos SDK, CosmWasm, oracle, or stablecoin-system experience. - A clear statement on whether the team is quoting only development work, or also audit coordination, testnet operations, and post-launch maintenance. ### Ledger and Ledger Live integration Status: OPEN FOR PROPOSALS Category: Wallet infrastructure Detail: https://terra-classic.money/open-work-detail.html?work=ledger-ledger-live-integration Create a complete Ledger integration path for Terra Classic: from current hardware-wallet compatibility review to improved signing flows, user documentation, and a realistic submission package for deeper Ledger Wallet / Ledger Live support. #### Deliverables - Audit of the current Terra Classic Ledger experience, including supported wallets, derivation paths, transaction types, known limitations, and user-risk points. - Implementation plan for a complete Ledger-safe Terra Classic flow covering send, receive, staking, delegation, redelegation, reward claiming, and governance signing where technically feasible. - Ledger Wallet / Ledger Live readiness package, including technical requirements, required repositories, node/indexer needs, transaction serialization, signing test vectors, and support documentation. - User-facing onboarding guide for Ledger users that avoids seed phrase, private key, custody, or investment-advice ambiguity. #### Acceptance Criteria - Users are never asked to expose private keys, seed phrases, or recovery words in any Terra Classic Ledger flow. - All supported transaction types are tested on hardware and documented with expected device prompts and failure cases. - The work includes clear compatibility notes for desktop, browser extension, and wallet-interface environments. - The final package is suitable for review by Ledger, wallet maintainers, Terra Classic validators, and security-conscious users. #### Quote Requirements - A current-state audit of existing Ledger support before implementation begins. - A proposed integration path: short-term compatibility improvements, medium-term wallet UX improvements, and long-term Ledger Wallet / Ledger Live submission path. - Examples of previous Ledger, Cosmos, wallet, signing, or hardware-device integration work. - A maintenance plan for future Terra Classic upgrades that may affect transaction signing or wallet compatibility. ### Trezor integration feasibility and implementation path Status: OPEN FOR PROPOSALS Category: Hardware wallet R&D Detail: https://terra-classic.money/open-work-detail.html?work=trezor-integration-feasibility Determine the most realistic path for Terra Classic to become usable with Trezor hardware wallets, then prepare the technical plan, issue package, and implementation requirements needed to move from unsupported asset to credible integration candidate. #### Deliverables - Feasibility report covering native Trezor Suite support, Trezor firmware requirements, Trezor Connect support, and third-party wallet integration options. - Technical gap analysis for Terra Classic transaction signing, address derivation, chain metadata, protobuf handling, staking messages, governance messages, and wallet UX. - Public issue / proposal package prepared for the relevant Trezor repositories or support channels, including technical rationale and implementation scope. - If feasible, a staged implementation plan for proof-of-concept signing, third-party wallet support, testing, documentation, and upstream submission. #### Acceptance Criteria - The first milestone must clearly state whether Terra Classic support is technically feasible under current Trezor constraints. - The deliverable must distinguish between native Trezor Suite support, firmware-level support, and support through a third-party wallet interface. - No public claim of "Trezor support" may be made unless signing, address display, transaction confirmation, and recovery-safety assumptions are verified. - All user-facing guidance must clearly explain risks, limitations, unsupported flows, and the difference between hardware signing and wallet-interface support. #### Quote Requirements - A dedicated feasibility phase before any build commitment. - Experience with Trezor firmware, Trezor Connect, protobuf definitions, hardware signing, or comparable wallet integrations. - A clear explanation of which Terra Classic transaction types will be tested first. - A decision tree showing what happens if native Trezor Suite support is not currently realistic. ### Babylon integration feasibility study Status: OPEN FOR PROPOSALS Category: Interchain security R&D Detail: https://terra-classic.money/open-work-detail.html?work=babylon-integration-feasibility Research and define a practical integration path between Terra Classic and Babylon's Bitcoin-secured ecosystem, with a focus on feasibility, security assumptions, IBC connectivity, finality-provider models, and long-term value for Terra Classic users and validators. #### Deliverables - Feasibility report explaining how Babylon's Bitcoin staking, Finality Provider, BSN, IBC, and Cosmos SDK architecture may or may not apply to Terra Classic. - Technical integration map covering required chain upgrades, IBC routes, light-client assumptions, validator/finality-provider requirements, and operational dependencies. - Risk assessment covering slashing, governance, validator economics, custody assumptions, integration complexity, and user-facing communication. - Recommended next-step package: no-go rationale, proof-of-concept plan, or governance-ready work package for deeper integration. #### Acceptance Criteria - The report must clearly separate proven Babylon capabilities from assumptions that require direct Babylon team confirmation. - The work must not imply that Terra Classic receives Bitcoin security, BTC yield, or Babylon integration until the mechanism is technically validated. - The feasibility study must define what Terra Classic would need to change, deploy, or maintain to participate safely. - The final deliverable must be understandable for validators, developers, governance voters, and non-technical ecosystem participants. #### Quote Requirements - Research methodology and list of primary sources to be reviewed, including Babylon documentation, IBC requirements, Terra Classic chain constraints, and validator operational needs. - Relevant experience with Cosmos SDK, IBC, shared security, Bitcoin staking, validator infrastructure, or protocol research. - A phased plan: feasibility research, technical alignment, stakeholder outreach, proof of concept, governance preparation. - Explicit assumptions, dependencies, and stop conditions where the work should not continue without new evidence or partner confirmation.