Open work for Terra Classic
A public board of ecosystem work packages that independent builders, software houses, and contributors can prepare proposals or quotes for.
Open work packages
Current ecosystem requests that can be quoted by independent builders, software houses, and contributors.
Post-Quantum Roadmap implementation strategyTurn the Post-Quantum Roadmap RFC into governance-ready implementation work packages for Terra Classic, including consensus feasibility, wallet/tx migration planning, IBC risk handling, and audit-gated delivery stages.Forex Protocol implementationBuild the first production version of Terra Classic's collateral-backed Forex Protocol, starting with EUTC minting, redemption, collateral vaults, oracle inputs, DEX liquidity flows, and safety controls.Ledger and Ledger Live integrationUpgrade Terra Classic hardware-wallet access from partial Ledger support into a safer, clearer, and more complete user experience, with a practical path toward Ledger Wallet / Ledger Live readiness.Trezor integration feasibility and implementation pathResearch and define the most realistic path for Terra Classic support in the Trezor ecosystem, including firmware, Trezor Connect, third-party wallet options, and Trezor Suite constraints.Babylon integration feasibility studyExplore how Terra Classic could connect with Babylon's Bitcoin-secured ecosystem, including BTC-backed security, IBC pathways, finality-provider models, and practical integration constraints.
Closed work packages
Completed ecosystem work that shows Terra Classic maintenance continuing in public.
Cooperation terms
Work should be scoped, quoted, delivered, and paid in a way the Terra Classic community can review in public.
Pay per delivered work
Payment is made only after successful completion of the whole accepted work package, or after successful delivery of an accepted milestone when the quote is split into stages.
Payment asset and wallet
Payment is made in LUNC or USTC to the wallet address described in the accepted quote or proposal. The requested asset, wallet, amount, and stage structure must be public before voting.
Proposal and quote process
The website can list work packages, but acceptance happens through public community discussion and Terra Classic governance.
Open Terra Classic Agora
Choose an open work package
Review the detail page, acceptance criteria, expected deliverables, and quote requirements before preparing the proposal.
Publish the quote on Agora
Post the official quote or proposal on the Terra Classic Agora forum so the scope, cost, delivery model, wallet, and risks are visible to the community.
Discuss with community and validators
Answer questions, refine the scope if needed, and make trade-offs explicit before the work asks for on-chain approval.
Go through governance
Submit the proposal to Terra Classic governance. A successful governance vote means the quote is accepted and the contractor can start the approved work.
Build your own app on Terra Classic:
Founder stories are being collected from Terra Classic builders and L2 teams. The section will feature real project clips as the community submits and reviews them.
Check Terra Classic documentation
Founder’s stories:
Founder stories in preparation
Recorded stories from Terra Classic builders and L2 teams will be added here as submissions are reviewed.
L2 project stories wanted
Teams building on Terra Classic can prepare a 1 min vertical video about what they are building and why it matters.
Community collection opening soon
This section will feature real voices from the ecosystem instead of placeholder profiles.
Join Terra Classic community:
Track upgrades, evaluate opportunities, and shape what ships next—collaborating with builders, validators, investors, and institutions across governance, code, and real-time discussion.
Frequently asked questions:
Getting started
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.
No single company, foundation, or individual controls Terra Classic. It is governed through on-chain proposals, validator voting, delegator participation, and community-led development.
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.
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.
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
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.
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.
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.
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
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.
When you undelegate staked LUNC, it enters an unbonding period of 21 days and does not earn rewards during that time.
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.
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.
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
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.
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.
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.
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
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.
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.
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
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.
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.
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
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.
Yes. Terra Classic supports WebAssembly smart contracts powered by CosmWasm, including contract upload, instantiation, execution, querying, and migration patterns.
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.
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.
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
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.
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.
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.
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
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.
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.
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.
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
No. This website is for education, onboarding, and ecosystem navigation only. It does not provide financial, investment, legal, tax, or compliance advice.
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.
Help serious builders find the work.
Share the open work board with teams that can deliver scoped, source-aware, governance-ready work for Terra Classic.