The migration instructions draw a precise boundary: the original chain continued as columbus-5, while a new chain used phoenix-1. Existing balances on the original ledger remained there, with LUNA renamed LUNC and UST renamed USTC. This was not an automatic conversion of every old balance into a new network asset. An exchange can present both histories beside similar logos, so a reader must check the network, denomination and withdrawal route before treating two displayed prices as the same instrument.

The current denomination guide makes another distinction that trading shorthand often hides. uluna is the micro-denomination of LUNC, while uusd identifies USTC. A historical dollar reference in a token name does not supply a dollar redemption right. Oracle quotations also do not guarantee market liquidity or a peg. With the old market conversion messages disabled, acquiring or disposing of these assets depends on actual markets and their available counterparties, rather than the former algorithmic mint-and-burn promise.

The May 2019 stress analysis by Nicholas Platias and Marco Di Maggio examined whether a payment currency and its reserve asset could withstand demand shocks. Its simulations rested on assumptions about demand, mining incentives and intervention mechanisms. Significantly, the paper discussed a reflexive danger: issuing more reserve tokens during stress could weaken their price and require still more issuance. The existence of a mathematical model therefore documented a proposed defense and its assumptions; it did not independently establish that the system could survive every market run.

Platias's separate staking-rewards paper supplied an influential investor story: payment activity would generate fees that rewarded the asset securing the network. It contrasted this claimed external value capture with rewards funded by dilution. Yet its revenue and adoption paths were projections, and it explicitly warned that outcomes could differ. Reading it today is useful for understanding why the proposal appealed to holders. It is not a current reward schedule, evidence that the projected commerce occurred, or a valuation model that survived the collapse unchanged.

On April 5, 2024, the SEC announced the jury's fraud verdict against Terraform Labs and Do Kwon. The regulator identified misleading claims about UST's stability and about Chai's use of the blockchain. That finding changes how the original adoption story should be read: promotional claims cannot be recycled as verified network usage. The judgment concerns the defendants and the conduct tried. It does not establish that every subsequent validator, developer or holder participated in that conduct, nor that current community proposals are automatically fraudulent.

The criminal case reached a further concrete milestone on December 11, 2025, when the United States Justice Department reported Kwon's fifteen-year sentence following his guilty plea. Legal accountability and a holder's financial recovery are separate questions. A sentence does not replenish an exchange balance, restore USTC's peg or settle every bankruptcy claim. For this network's history, the important distinction is between documented adjudication and online recovery expectations that attach much broader promises to the same headline.

The July 2022 recovery paper by Edward Kim and collaborators describes a community-led emergency effort separate from Terraform Labs. Its subject was practical continuity: repairing operations, restoring usable governance and rebuilding confidence in a damaged network. The paper is evidence that named contributors organized around those tasks, rather than proof that every proposed intervention was completed. Keeping the ledger available and designing a credible monetary recovery are different engineering and economic problems; success at the first does not establish success at the second.

The public classic-terra/core repository provides a more inspectable record than an anonymous declaration that the chain is saved. It exposes code, release discussions and the terrad application used by operators. Its historical README also contains inherited terminology and links, which must be checked against newer releases. A repository demonstrates available software and development work. It cannot by itself show how many independent operators installed a version, whether a public endpoint is synchronized, or whether a particular exchange supports deposits at this moment.

Terra Classic's maintained protocol guide describes stake-weighted consensus and delegation, with LUNC participating in network security and governance. Unbonding introduces a waiting period, and validator misconduct or operational failures can expose delegated stake to penalties under the applicable rules. Those functions distinguish LUNC from an ordinary application token. They also explain why advertised staking rewards should be read alongside validator performance and liquidity constraints.

A protocol description is not a promise of an unchanged reward percentage or an assurance that every operator follows good security practice.

The validator guide treats uptime, oracle operation, key security and governance as ongoing responsibilities. Its recommended separation of signing infrastructure from exposed services illustrates a basic control boundary: a public RPC endpoint and a consensus signing key should not be treated as interchangeable tools. Delegators depend on an operator's execution of these duties while retaining certain governance choices.

The existence of a validator set does not erase concentration or maintenance risks, particularly when an upgrade requires many independently managed machines to move together.

The governance guide emphasizes the messages attached to a proposal. A vote can authorize a parameter change, fund a recipient or signal sentiment, depending on what the proposal actually contains. These are not equivalent outcomes. Bonded voting power and delegation affect participation, while delegators can override a validator's vote. For a controversial proposal, the useful audit trail includes its message type, deposit and voting status, final execution, and the state changed afterward. A persuasive discussion thread alone supplies none of those execution receipts.

The community pool is another area where historical vocabulary can mislead. The maintained treasury guide distinguishes the distribution module's communal funds from the former monetary-policy treasury. A displayed token balance is neither a dollar guarantee nor a commitment to pay a particular developer. Funding and spending messages have specific amounts, denominations and recipients. Evaluating a grant therefore means following the enacted transfer and deliverables, rather than assuming that the existence of a pool makes an entire roadmap financially secure.

Edward Kim's September 2022 proposal for a 1.2 percent transfer tax carefully separated on-chain enforcement from exchange trading. The chain could not simply impose the same rule on an exchange's internal order book. Its own analysis raised wallet compatibility, liquidity migration and application costs. That historical proposal helps explain the appeal of supply reduction and its tradeoffs. The percentage in its title is not presented here as today's parameter, and a reduction in token supply does not establish an offsetting increase in economic demand.

A 2026 reserve-ceilings discussion shows how far the debate extends beyond burning. The proposer distinguished an initial policy vote from later spending decisions and software changes. Participants challenged whether LUNC and USTC should share the same funding strategy and whether rigid reserves would crowd out development. This makes the implementation sequence essential: endorsement of a design, allocation of money and activation of code are separate events. A future mechanism should not be described as operating merely because its advocates can point to an earlier favorable vote.

An August 2026 funding request from Juris Protocol described IBC relaying work involving Bumeo Capital and LuncGoblins. It identified server expenses and maintenance responsibilities for connections including Osmosis, Noble and Axelar. The proposal is useful evidence that connectivity requires people, machines and funding rather than only compatible protocol code. It remains a request unless an approval and payment are verified. A functioning relay also does not make a destination asset risk-free or guarantee that every route has enough liquidity for a user's intended transaction.

The proposal separated financial and infrastructure support from technical operation, making responsibility more concrete than a generic interoperability slogan. It also explained that earlier activity had depended on private funding after a prior mandate expired. This matters to readers assessing sustainability: open access to software does not mean recurring costs disappear. For such a service, the meaningful follow-up is an observable relay, a disclosed operator and a funded operating period, rather than the mere number of chains listed in an ecosystem directory.

The January 2026 community-owned exchange discussion proposed routing trading fees toward burns and ecosystem funding. Replies asked harder questions about audits, liquidity fragmentation, operating costs and whether a simpler spot exchange should come first. Those questions expose a circular risk in revival plans: projected trading fees are sometimes used to justify a product whose trading demand has not yet been shown. The thread records competing design preferences, not an independently measured business case or evidence that a public treasury approved all of its ambitions.

The governance documentation supplies a practical way to examine such plans without accepting either enthusiasm or cynicism as proof. A reader can distinguish a discussion, a text proposal and a transaction carrying spending instructions. They can then compare the approved recipient and amount with the deliverable being advertised. This does not determine whether a product will succeed commercially. It does keep a development story tied to the powers that were actually exercised, which is particularly valuable when several loosely associated community groups use the same network name.

The v4.0.0 release published on March 29, 2026 documents a substantial software update, including the Cosmos SDK 0.53 migration. A release is a dated artifact, not automatic proof that the entire network activated it at publication time. Its significance is that the codebase has a maintenance history beyond the emergency period. Readers comparing versions should look at upgrade handlers, dependency changes and operator coordination, rather than interpreting a higher version number as a blanket improvement in every security or application property.

The accompanying v14_1 proposal document discussed testnet work, fork testing and the intended mainnet upgrade path. Testing a state transition before asking validators to execute it is materially different from publishing an untested feature wish list. Nevertheless, a test result and an activation receipt answer different questions. The document supports the preparation process described there; it should not be stretched into proof that every validator, wallet or contract handled the eventual transition without an issue.

The September 14, 2026 v4.0.1-patch.3 release identified a mandatory security update involving wasmd and wasmvm and prescribed a coordinated consensus-changing upgrade. Its notice supplied an estimated activation date and a target height. Those instructions show why operator coordination matters, but an estimate is not a verified block-time receipt. This account does not assert that an exploitation occurred or that all validators installed the patch. Both claims would require evidence beyond a release notice describing a vulnerability and its remediation.

The September 28 v4.0.2 release then described a compatible rolling update, with security dependencies and operational fixes. The distinction between a coordinated fork and a rolling release is useful: they impose different timing requirements on operators even when both deserve attention. As of this review, these publications establish continued maintenance and explicit security work. They do not establish USTC recovery, uniform exchange support, current validator independence or the success of proposed economic reforms.

Those remain questions for live network evidence and subsequent governance receipts.