Kujira's history passes through three distinct technical settings. Its own retrospective places the original ORCA product on Terra and connects that work to the ideal of opening financial opportunities to ordinary participants. The later decision to move toward THORChain is presented as continuing that mission. This is the team's account of its purpose, not evidence that the systems it built always delivered equal access or protected users from loss. Continuity of a mission and continuity of a blockchain are different things.

The independent Kujira network was identified as kaiyo-1, with its own Cosmos SDK software, validator configuration and KUJI staking denomination. Rujira's history documentation instead describes an alliance combining Kujira-related teams, Levana and THORChain into an application layer on THORChain. Moving products there did not convert every old Kujira block into a THORChain block. The distinction is essential when reading an old wallet balance, an application announcement or a market page that still uses the KUJI ticker.

Kujira's migration guide records a snapshot on May 13, 2022 after the UST collapse, with separate treatment for KUJI and staked KUJI held on Terra. It offered eligible holders a route to native assets on the new network. That was a specific recovery process for defined balances, not a promise that all losses from Terra were reimbursed. A token migration should be read through its eligibility, conversion rules and destination chain rather than described loosely as everyone being made whole.

The published kaiyo-1 genesis file specifies July 1, 2022 at noon UTC. A genesis configuration is concrete evidence of the network's intended starting state; by itself it is not a measurement of when all validators began serving users. The surviving configuration is useful for distinguishing this chain from Kujira's earlier Terra contracts and later THORChain applications. Historical network identity remains important after services close, because the same project name can otherwise conceal several incompatible addresses, assets and transaction histories.

Kujira's product directory grouped BLUE, FIN, BOW, GHOST and ORCA into a common financial toolkit. BLUE handled account and governance functions; FIN supplied trading; BOW contributed market-making liquidity; GHOST added lending; ORCA handled liquidation markets. This integration explains the project's attraction better than calling it merely another token. It also explains why trouble in a lending or collateral market could matter beyond one screen. The products were intended to be used together, so users had to understand their connections as well as each individual interface.

FIN's documentation describes an on-chain order book, where orders provide explicit trading prices rather than requiring every trade to use a conventional liquidity pool. BOW's separate documentation explains how its inventory-based algorithm placed and replaced orders on FIN. Therefore, the presence of an order book did not eliminate automated liquidity provision or its inventory risks. BOW providers could receive trading fees and additional incentives, but those mechanisms did not ensure profitable execution or enough counterparties whenever someone wanted to exit.

ORCA turned purchases of liquidated collateral into a visible bidding process. Its documentation distinguished markets for USK collateral, isolated margin and GHOST positions, showing users the collateral, bid asset, available depth and discounts. Making such opportunities accessible was central to Kujira's public identity. A discount, however, is only a relation to a reference price. It does not guarantee that acquired collateral can be sold profitably, especially when prices are falling or there are few other buyers.

GHOST supplied the lending side of this arrangement. Its documentation describes deposits earning interest, collateral supporting borrowing and governance admitting additional assets. It also explicitly promotes leverage and connections to the wider product suite. That is a financial design with borrowers, lenders and collateral exposure, not a savings account whose advertised yield is assured. The distinction becomes especially important when an ecosystem's own token is used to support borrowing that is meant to increase activity inside the same ecosystem.

USK was designed as a crypto-collateralized stablecoin with a soft dollar peg. The technical documentation describes borrowing against locked collateral, interest and minting fees, and liquidation through ORCA when positions become too risky. It describes incentives intended to draw the market price back toward a dollar. These mechanisms are different from an issuer promising direct dollar redemption. The original numerical parameters are historical documentation, and should not be reused as current instructions for a retired system.

A 2026 notice reproduced in the project's official subreddit reported a mismatch between the lending contract's accounting and the amount actually available, alongside weak demand for users trying to sell USK. It proposed migrating xUSK receipts and arranging purchases on Rujira. This account attributes that report and proposal to the published notice; it does not treat the plan as proof of completed repayments. A migration route, an accounting repair and a buyer willing to absorb claims are separate pieces of a recovery.

The token documentation identifies KUJI as the network's native asset for fees and participation in its economic system. It records a governance-approved reduction of the original supply and completion of the release schedule in November 2023. Much of the appeal was that staking rewards came from activity rather than an endless stream of newly issued tokens. That design still required people to use the products. Avoiding dilution does not by itself create fee income, liquid markets or an appreciating asset.

The token-factory documentation explains another distinctive feature: applications could create native Cosmos denominations instead of handling their assets solely as contract tokens. The design allowed such denominations to be used in fee and revenue flows. This helps explain why a staker might receive a collection of different small balances. It also shows why the label native must be used carefully. An application denomination recognized by one chain's bank module is not automatically the original asset of another chain or a universally accepted fee currency.

Kujira described itself as semi-permissioned because launching a contract required governance approval. The stated purpose was to curate a coherent collection of applications rather than permit any deployment without review. Its developer documentation also described an on-chain scheduler and oracle integration. These were concrete design choices, not guarantees that approved applications were safe. Permission to deploy, software review and ongoing risk management should not be collapsed into a single claim that community selection prevents failures.

The Senate was a separate grant-oversight experiment, now explicitly marked retired in the documentation. Up to nine elected representatives considered community funding using group and multisignature contracts; its remit did not replace protocol governance. Daniel Lux's October 2023 financial report described grant review, treasury conversion and liquidity activities, while warning that parts of the report's forward-looking language were already outdated. This record is more useful than an undated claim that Kujira still has an active elected Senate managing its future.

In its August 1, 2024 statement, the team acknowledged using part of its operating funds in leveraged positions to stimulate liquidity and activity. It described stressed positions and proposed transferring treasury and protocol responsibilities into a new operational structure. The statement is retained through a readable archival mirror because the original social page was inaccessible during this review. Its explanations about other actors should be treated as the team's account, not a proven finding of coordinated misconduct by outsiders.

A subsequent August 3 recovery statement proposed PILOT sales to repay operational debts, including participation using certain lending receipts, and an rKUJI instrument redeemable under specified arrangements. It also proposed reducing borrowing against KUJI and moving treasury decisions outside the founding team. These were proposed remedies in a crisis. Their publication did not mean every creditor had been repaid or that the promised control changes had already happened. The distinction preserves accountability instead of letting the announcement of a recovery substitute for its execution.

The March 2022 ORCA queue audit examined a particular code revision before the independent Kujira chain existed. It reported two low-risk issues as acknowledged and an informational issue as remediated. It also excluded the liquidity-stability curve and directly financial attacks from scope. Those boundaries are central to interpreting the report. It cannot be used as a blanket audit of later GHOST markets, USK configurations, treasury leverage or all software that eventually operated on kaiyo-1.

Operational visibility also narrowed during the migration. A July 2025 project recap announced that Finder would stop indexing historical Kujira data and FIN price charts would lose their historical service. At that time the notice explicitly distinguished ending those services from stopping the chain. This is a useful example of why an unavailable explorer is not sufficient evidence of a blockchain halt. It also explains why later investigators may find the original user's transaction history harder to reconstruct from the team's familiar interfaces.

Rujira's current token documentation says the legacy merger window ended on April 5, 2026 and that further conversion is no longer possible through that process. It describes different schedules for participating assets, declining conversion rates and incentives for leaving converted RUJI in the merger contract. The documented switch flow moved external assets into a THORChain-native arrangement before or alongside the merger. This was not an automatic renaming of every KUJI balance, and KUJI, RUJI and RUNE should not be treated as interchangeable tickers.

The January 2026 Rujira roadmap described a planned BTC-backed stablecoin as a successor to USK and placed other financial products on a development schedule. A successor proposal does not establish that holders of the earlier stablecoin receive an equivalent claim or that the new product has launched. Rujira's future can be discussed as the continuation of a team and product tradition, while the fate of particular old liabilities remains a distinct historical and contractual question.

Early supporters did not all make unconditional promises. In August 2022, Wilder54321 liked the fee-funded staking model but tied its prospects to attracting users. By March 2024, patiboy72 was considering increasing a position while EffectiveConcern questioned the usefulness of receiving many tiny rewards. Other participants defended the product suite or complained about liquidity. These records show identifiable disagreements, not a scientific survey. A community's visual identity and loyal vocabulary should not erase ordinary users asking how the economics actually work.

El Dorado's September 2024 essay offered a much more aggressive recovery thesis: combining Kujira's applications with THORChain's liquidity could rescue their promise. It explicitly promoted buying, making it evidence of advocacy rather than an independent valuation. A different, practical problem appears in 712Jefferson's December 2023 thread about two KUJI forms in one wallet. The author later reported resolving the issue through a bridge. Together these accounts show both the grand investment story and the asset-routing confusion that everyday participants faced.

THORChain's August 6, 2026 podcast recap attributes Kujira's shutdown to a small exploit that accelerated planned retirement. Pragmatic Monkey reported unauthorized USK minting and roughly $6,000 extracted. This is a published participant account, not an independently reconstructed forensic report or an exact last-block timestamp. Continuing builders and applications refer to Rujira, rather than continued operation of Kujira's old ledger.

The Cosmos registry still labeled Kujira live when reviewed, despite that later shutdown account. Registry status is maintained metadata and can lag operational reality. This history therefore treats the chain as retired according to the later participant report, while preserving the discrepancy for readers checking old tools. It does not infer that every stranded balance can still be recovered. Historical asset claims require the precise chain, migration eligibility and surviving recovery mechanism, not a ticker on a market listing.