This glossary is designed for mixed audiences (community, investors, builders, validators, press). Definitions are plain-English first, with just enough technical precision to read the report without getting lost. Terms are alphabetical for scanning.

A

Active address / active wallet

A wallet address that performed at least one on-chain action in a defined time window (e.g., 30 days).

Why it matters: It’s a rough proxy for “real usage,” but can be inflated by bots or a few power users.

Airdrop

A distribution of tokens to users (often as a marketing or bootstrapping tactic).

Why it matters: Can create short-term attention without sustainable demand.

AML / KYC

Anti–Money Laundering / Know Your Customer policies used by exchanges and regulated intermediaries.

Why it matters: Access to trading and fiat rails depends on it, regardless of what the chain does on-chain.

APR (staking APR)

Annual Percentage Rate: an annualized estimate of staking yield (usually from inflation + fees), before compounding assumptions.

Why it matters: Low APR can weaken validator economics; high APR can imply high inflation or unsustainable subsidies.

Authority gap

A governance reality where many people act “as if official,” but there is no legally recognized or clearly mandated operator accountable for outcomes.

Why it matters: Partners and exchanges need clear accountability surfaces; ambiguity increases risk.

B

Bad debt (USTC “legacy debt”)

A large outstanding supply that represents a historical obligation narrative (e.g., “repeg”), without a credible mechanism or backing.

Why it matters: It acts like an overhang that distorts incentives and narratives.

Benchmark / peer set

A selected set of comparable blockchains used for relative evaluation (not to “win a ranking,” but to contextualize).

Why it matters: Helps separate “normal for crypto” from “unique Terra Classic weakness.”

Block

A batch of transactions packaged and finalized by validators.

Why it matters: All throughput, fees, and state changes are expressed through blocks.

Block time

Average time between blocks.

Why it matters: Affects user experience, finality feel, and validator load.

Bridge

A mechanism to move assets across chains (not necessarily IBC-based).

Why it matters: Bridges expand connectivity, but add trust and security risk.

Bug bounty

A program paying external researchers to report vulnerabilities responsibly.

Why it matters: It’s a measurable security maturity signal.

Bus factor

“How many people can disappear before the project stalls.” A low bus factor means key-person risk.

Why it matters: Predicts continuity risk for the codebase and operations.

C

Canonical (information) source

The “official-looking” or primary reference surface (website, docs, explorer links).

Why it matters: Canonical links are a control plane for user routing and trust.

Cap table

A record of ownership (equity holders, token allocations, vesting) in a company-like structure.

Why it matters: In L1 diligence, unclear ownership and liabilities can be dealbreakers.

CEX (Centralized Exchange)

A custodial trading venue (e.g., users trade via the exchange’s internal ledger).

Why it matters: Terra Classic’s market demand can exist off-chain even when on-chain utility is weak.

Chain halt

A period when block production stops (planned or unplanned).

Why it matters: It is a top-tier reliability event affecting builders, exchanges, and trust.

Claim label (Measured / Documented / Reported / Inferred / Speculative)

A required tag describing how strong the evidence is for a statement.

• Measured: derived from reproducible data (on-chain/telemetry/repo analytics)

• Documented: based on official records (governance, audits, signed comms)

• Reported: stakeholder testimony (surveys, chats, interviews)

• Inferred: reasoned conclusion from multiple signals (assumptions stated)

• Speculative: forward-looking hypothesis (explicitly separated)

  Why it matters: It prevents “narrative facts” from sneaking into decision-grade analysis.

Client (software client)

The node software validators run to participate in consensus.

Why it matters: Client upgrades are existential; outdated clients increase security and compatibility risk.

Client update (IBC client update)

A governance-approved update that keeps cross-chain trust relationships current (for IBC).

Why it matters: Without updates, IBC connectivity degrades or breaks.

Community Pool

A protocol-level treasury funded by on-chain mechanisms (fees/inflation modules, depending on chain parameters).

Why it matters: It’s the only native “budget-like” lever for funding work—if governance can execute.

Concentration (stake / voting power / liquidity)

A condition where a small number of actors control a large share (stake, votes, liquidity, endpoints, etc.).

Why it matters: Concentration creates capture risk and single-point-of-failure risk.

Control plane

The set of operational assets that influence how users access and trust the ecosystem (domains, docs, endpoints, explorers, key repos, “official” lists).

Why it matters: Control-plane capture can occur even if stake is decentralized.

Counterparty risk

Risk that another party (exchange, bridge, relayer operator, endpoint operator) fails or misbehaves.

Why it matters: Many “on-chain experiences” depend on off-chain operators.

D

DAO

A governance structure coordinated by tokenholders, often without traditional corporate structure.

Why it matters: “DAO-like” doesn’t automatically shield participants from liability; counterparties still want accountability.

Data pipeline (ETL)

Extract–Transform–Load: process of collecting data, cleaning/normalizing it, and storing it for analysis.

Why it matters: Without a pipeline, metrics become cherry-picked screenshots.

Dealbreaker

A red-flag class condition strong enough to justify a “no-go” decision in diligence.

Why it matters: Prevents “optimism bias” from overriding structural risk.

Decentralization

Distribution of control across many independent actors (stake, infrastructure, code authority, information routing).

Why it matters: Real decentralization reduces capture and key-person risk—but must be measured, not asserted.

Delegator

A token holder who stakes by delegating tokens to a validator (instead of running a validator).

Why it matters: Delegators are the security budget; their behavior affects validator incentives and governance outcomes.

Delisting

Removal of a token from an exchange (or restrictions that effectively reduce access).

Why it matters: Market access is a fragile “life-support” surface for many ecosystems.

Dependency risk

Risk introduced by relying on upstream libraries or external components (e.g., SDK upgrades, cryptography libs).

Why it matters: Security and reliability are partly inherited from dependencies.

DEX (Decentralized Exchange)

On-chain trading using smart contracts and liquidity pools (non-custodial).

Why it matters: DEX volume/TVL are “utility layer” signals, but can be micro-scale even when CEX trading is large.

DoS (Denial of Service)

An attack that overwhelms a network/service to degrade availability.

Why it matters: Reliability threats are not only “hacks”; availability failures kill adoption too.

E

Ecosystem theater

Legitimacy signals (claims, announcements, dashboards) that are not matched by verifiable counterpart evidence or measurable outcomes.

Why it matters: It inflates narrative while degrading partner trust.

Effective outage

A situation where the chain may be producing blocks, but users can’t access it due to endpoints/indexers/explorers being down or degraded.

Why it matters: “Visibility is part of uptime” for real users.

Endpoint (public RPC / API)

A server that lets wallets, explorers, and apps query the chain and submit transactions.

Why it matters: Endpoint concentration creates de facto centralization and availability fragility.

Evidence hierarchy

Preferred order of evidence strength: on-chain measurements → telemetry/logs → governance/repos → audits/advisories → surveys/chats → media/social.

Why it matters: It defines what counts as “proof” in this report.

Explorer

A website that shows blocks, transactions, validators, governance, and accounts.

Why it matters: Explorers are public “truth surfaces” and a UX dependency.

F

Fee (transaction fee)

Amount paid to get a transaction processed (usually gas × gas price + extras).

Why it matters: Fees are one of the few measurable “economic throughput” signals.

Finality

The point at which a transaction is considered irreversible (practically “settled”).

Why it matters: Finality quality affects exchange operations, UX, and risk models.

Fork

A divergence of the chain history or codebase (can be intentional or contentious).

Why it matters: Forks reshape compatibility, legitimacy narratives, and tooling support.

G

Gas

A unit measuring computational work for executing a transaction.

Why it matters: It’s the basis for fee calculation and spam resistance.

Governance

On-chain decision-making process (proposals + voting + execution rules).

Why it matters: Governance is Terra Classic’s “operating system” for change—if execution is real.

Governance capture

When a small set of actors can reliably control outcomes (through stake concentration, low participation, or operator clustering).

Why it matters: Capture risk undermines credibility and can block institutional partnerships.

Grant

Treasury funding allocated to a team/project to deliver defined work.

Why it matters: Grants without accountability artifacts become “spend without proof.”

H

Halt-class vulnerability

A vulnerability that can stop block production or make the chain unsafe without being “a theft hack.”

Why it matters: Availability is a first-order security dimension.

I

IC (Investment Committee) brief

A structured memo used to decide “invest / acquire / partner / don’t.”

Why it matters: The report aims to be decision-grade in this format.

IBC (Inter-Blockchain Communication)

A Cosmos protocol for trust-minimized messaging and asset transfers between chains.

Why it matters: IBC connectivity is a practical proxy for “interchain relevance.”

IBC channel

A specific connection path between two chains (like a “route” with identifiers).

Why it matters: Channels can exist but be inactive; inventory alone is not adoption.

IBC relayer

An off-chain service that relays IBC packets between chains.

Why it matters: Relayers are part of liveness for cross-chain functionality.

Indexing / indexer

A system that reads raw blockchain data and makes it queryable fast (for explorers, dashboards, analytics).

Why it matters: Without indexers, the chain is “alive but illegible.”

Inflation (token inflation)

Increase in token supply over time (protocol issuance).

Why it matters: It affects staking yields, security budget, and long-term holder dilution.

Integrity control

A rule/process preventing metric drift, cherry-picking, or narrative manipulation (e.g., defined windows, reproducible formulas).

Why it matters: It’s the difference between “blog post” and “report.”

J

Jailed validator

A validator temporarily removed from active set due to downtime or misbehavior; can be unjailed by following rules.

Why it matters: Large “validator graveyards” imply lifecycle hygiene problems.

K

KPI (Key Performance Indicator)

A metric tied to a decision lever (not a vanity metric).

Why it matters: KPIs force arguments to be measurable and falsifiable.

L

L1 (Layer 1)

The base blockchain itself (consensus + security + data availability for its own state).

Why it matters: If L1 is weak (security/reliability), the ecosystem can’t safely build on top.

L2 (Layer 2)

A system built on top of an L1 to add scalability or specialized execution (definition varies by ecosystem).

Why it matters: L2 success can fail to translate into L1 recovery if incentives don’t align.

Liveness

The network’s ability to keep producing blocks and processing transactions over time.

Why it matters: Liveness failures (halts, persistent downtime) destroy partner trust.

Liquidity

How easily an asset can be traded without moving price too much.

Why it matters: Liquidity is a market-access health signal and affects investor risk.

Liquidity concentration

A situation where most trading depth exists on a small number of venues.

Why it matters: It increases fragility: one venue change can reprice the ecosystem.

M

MAW (Monthly Active Wallets)

Count of unique wallets active in a month (definition depends on methodology).

Why it matters: A core adoption proxy, but must be guarded against spam and multi-wallet behavior.

Market cap

Price × circulating supply.

Why it matters: It’s a perception metric; it does not prove on-chain utility.

Market microstructure

The “how trading works” layer: spreads, depth, venue fragmentation, liquidations, open interest.

Why it matters: It explains why price can move without corresponding on-chain fundamentals.

Metric dictionary

A reference specifying KPI name, definition, formula, source, frequency, biases, how it can be gamed, and “what good looks like.”

Why it matters: Prevents meaning drift and metric manipulation.

N

Narrative volatility

Large swings in attention or belief that aren’t matched by fundamental changes in usage/security/execution.

Why it matters: It’s a reputational and partner-risk variable.

Node

A machine running the blockchain software and maintaining a copy of the chain state.

Why it matters: Nodes are the infrastructure substrate; decentralization requires many independent nodes.

O

Off-chain vs on-chain

• On-chain: activity recorded and enforceable by the blockchain

• Off-chain: activity happening outside the chain (CEX trading, social, websites, relayers, endpoints)

  Why it matters: Terra Classic can have off-chain demand while on-chain utility remains weak.

Oracle

A system that provides external data (e.g., prices) to the chain.

Why it matters: Oracle health affects DeFi safety and sometimes consensus-adjacent mechanisms.

P

Partner readiness

How safe a chain is to integrate from a counterparty’s view: stability, clarity, compliance posture, reliable endpoints, credible governance execution, and reputational risk.

Why it matters: Partner rejection is often an execution and trust issue, not a technology issue.

Patch latency

Time between a vulnerability being known and being fixed/deployed.

Why it matters: A measurable security maturity indicator.

PoS (Proof of Stake)

Consensus where validators stake tokens to propose/validate blocks; misbehavior can be punished (slashing).

Why it matters: Security depends on stake distribution, validator incentives, and governance behavior.

Proposal (governance proposal)

A formal governance item put to vote (text-only or execution-critical like upgrades/spends).

Why it matters: Proposal volume can be high while execution-quality remains low.

Pruning

Deleting older blockchain state to reduce disk usage, sometimes at the cost of historical query ability.

Why it matters: It affects reproducibility, analytics, and the ability to verify history.

Q

Quantum risk / post-quantum (PQ) readiness

Risk that future quantum computers could break today’s public-key cryptography, requiring migration to PQ-safe schemes.

Why it matters: It’s long-horizon, but ecosystems with no plan signal weak security governance.

Quorum

Minimum participation required for a governance vote to be valid (exact rules chain-specific).

Why it matters: Low participation plus low quorum can amplify capture risk.

R

Red flag

A condition that materially increases probability of catastrophic failure, stagnation, or partner rejection, supported by strong evidence and framed with likelihood/impact/disconfirmation.

Why it matters: Red flags are “risk gates,” not opinions.

Relayer

See IBC relayer.

Repo (repository)

A code repository (often GitHub) containing source code, issues, and pull requests.

Why it matters: Repo activity is a measurable developer and governance artifact surface.

Retention (proxy)

A measure of how many users return after first engaging (e.g., week-1, week-4).

Why it matters: It distinguishes “attention” from “habit.”

S

Security posture

The overall security state of the chain: audits, responsible disclosure, patch cadence, dependency hygiene, operational security, incident response.

Why it matters: “We haven’t been hacked” is not proof of security.

Service Level Agreement (SLA)

A formal uptime/performance contract.

Why it matters: Most public endpoints have no SLA; this is a structural reliability constraint.

Slashing

A penalty that destroys (slashes) a validator’s staked tokens for certain misbehavior or downtime (rules vary).

Why it matters: It’s a core economic security mechanism in PoS.

Snapshot (data snapshot)

A fixed capture of metrics at a point in time or defined window.

Why it matters: Without explicit snapshots, charts become non-reproducible.

Stake / staking

Locking tokens to support network security and earn rewards.

Why it matters: Staking aligns incentives—but also concentrates governance power.

Stake concentration

When a small number of validators control a large share of staked tokens/voting power.

Why it matters: It increases capture risk and reduces resilience.

Supply (circulating vs total)

• Total supply: all tokens that exist

• Circulating supply: tokens considered available to the market (definition depends on methodology)

  Why it matters: Supply definitions affect market narratives and valuation framing.

Sybil-like clustering

Multiple validators that appear independent but are controlled by the same operator group (or tightly coordinated).

Why it matters: It creates an illusion of decentralization.

T

Tax2Gas (reverse-charge tax behavior)

A mechanism where a tax that would have been additionally charged is effectively routed/absorbed into gas/fees in a way that changes who bears the cost (implementation-specific).

Why it matters: It changes the real-world impact of “burn tax” narratives.

Tax exemption registry (“zones”)

A list of transactions/contracts/actors exempted from the burn tax or certain parameters (implementation-specific).

Why it matters: Exemptions define the true economic regime, not the headline rate.

Telemetry

Operational data from nodes/services (latency, errors, uptime), not just on-chain state.

Why it matters: Telemetry can reveal reliability problems that chain data alone hides.

Throughput

How much the chain can process (transactions per second, or other volume measures).

Why it matters: Throughput capacity matters, but real demand matters more.

TVL (Total Value Locked)

Total value deposited in DeFi protocols (usually across lending/DEX/derivatives).

Why it matters: TVL is a rough DeFi footprint proxy—often near-zero even when token trading is active off-chain.

U

Upgrade (chain upgrade / software upgrade)

A coordinated change to the chain software, often requiring validator action and governance approval.

Why it matters: Upgrades are recurring stress tests for operational maturity.

USTC

Terra Classic’s legacy stablecoin token, currently not functioning as a stablecoin in practice.

Why it matters: USTC narratives create reputational and regulatory overhang.

V

Validator

An operator running infrastructure that participates in consensus, produces/validates blocks, and votes in governance (directly or via delegation power).

Why it matters: Validators are both a security layer and a governance class—so competence and incentives matter.

Validator set (active set)

The set of validators currently participating in consensus (often top-N by voting power).

Why it matters: Security and liveness depend on the active set’s quality and distribution.

Vesting

A schedule that releases tokens over time (often for team/investors).

Why it matters: Vesting cliffs can impact sell pressure and governance power.

Voting power

A validator’s governance and consensus weight, generally proportional to delegated stake (with chain-specific details).

Why it matters: It’s the core control surface in PoS.

W

Wallet UX

The user experience of managing keys, signing transactions, viewing balances, participating in governance, and accessing dApps.

Why it matters: UX debt is adoption debt—especially for retail-heavy ecosystems.

Whale

A holder with a very large position relative to typical users.

Why it matters: Whales can dominate governance outcomes and market microstructure.

X–Z

x/tax module

A chain module responsible for burn taxation (implementation details chain-specific).

Why it matters: It defines the real mechanics behind “burn tax” narratives.

Zero-sum dynamics

A situation where gains by one group come largely at the expense of another (rather than growing the overall pie).

Why it matters: Governance and treasury decisions can become redistributive instead of growth-oriented.