> For the complete documentation index, see [llms.txt](https://docs.redacted.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.redacted.money/our-story.md).

# Our Story

## From Terra to THORChain — Forged Through Adversity

Redacted's journey begins in early **2022** under our former name **TerraBay**, building on the Terra blockchain. In February 2022, we launched the **Ronin NFT** collection — 2,968 Ronin-inspired NFTs that sold out and raised 742,000 UST, funding the development of our privacy protocol.

Then came the storm. In **May 2022**, the Terra ecosystem collapsed — UST and LUNA imploded in one of crypto's most devastating events. But our vision and commitment never wavered. The protocol was largely completed before the crash, and the team pressed forward.

In **July 2022**, we seamlessly transitioned the Ronin NFTs and the project to **Terra V2**, where we successfully launched our first privacy-centric protocol — proving our adaptability under the most hostile conditions.

But we knew Terra V2 wasn't the long-term home for what we were building. We needed a foundation as decentralized and resilient as our mission demanded.

## Why THORChain and Rujira

We chose **THORChain** and its application layer **Rujira** for two reasons: **true decentralization** and **any asset, best liquidity**.

THORChain is one of the most decentralized cross-chain protocols in existence — no multisigs, no centralized bridges, no single points of failure. It settles native assets (real BTC, real ETH, real XRP) without wrapping or custodians. This is the kind of infrastructure that a privacy protocol must be built on — because privacy is only as strong as the base layer it runs on.

But decentralization alone wasn't enough. Our vision is **programmable privacy for any asset** — and THORChain is the only protocol that gives us native access to every major chain's assets with the deepest cross-chain liquidity in DeFi. No wrapped tokens, no bridging risk, no liquidity fragmentation. When you trade privately through Redacted, you're trading real assets with real depth.

**Why this matters for Redacted:**

* **Any asset** — Native BTC, ETH, XRP, BNB, AVAX, ATOM, and every chain THORChain supports. Programmable privacy isn't limited to one chain
* **Best liquidity** — THORChain's deep cross-chain liquidity means better execution, tighter spreads, and real volume for privacy-preserving trades
* **No trusted bridges** — Your BTC is real BTC, your ETH is real ETH. No wrapped tokens, no custodial risk
* **Validator-secured** — THORChain's economic security model ensures no single entity can censor transactions
* **Rujira's composability** — Full CosmWasm smart contract environment with access to THORChain's liquidity and settlement
* **Aligned values** — A community and infrastructure that believes decentralization isn't optional

The team's deep roots in the THORChain ecosystem — built through years of close collaboration — made this a natural homecoming. Redacted isn't just deployed on Rujira; it's woven into the fabric of the THORChain universe.

## An Independent Protocol with a Multichain Vision

Redacted is an **independent protocol** — it operates on top of Rujira with its own governance, its own token ($RED), and its own community. Rujira is our base, our home chain, the foundation everything is built on.

But we're not stopping there. The plan is to deploy **multiple outposts on other chains** — expanding Redacted's privacy layer across the crypto landscape. Every outpost, every integration, every expansion drives value back to where it belongs: **our base on Rujira**.

This is how you build a privacy network effect: one base, many outposts, all flowing home.

## From Self-Reliant to B2B — The Next Chapter

Up until now, Redacted has been fully self-reliant — building our own protocol, our own interface, our own community from the ground up. That independence is core to who we are and it's not going away.

Going forward, we're expanding into **B2B integrations** — embedding Redacted's privacy infrastructure into existing protocols, wallets, and DeFi platforms. Best-in-class privacy as a service, integrated where users already are. Every integration earns revenue that flows back to $RED stakers and Ronin NFT holders.

**Two paths, one mission:**

* **Redacted Interface** — Our own frontend for maximum privacy and full decentralization. No compromises, no middlemen. The purest privacy experience
* **B2B Integrations** — Redacted's privacy layer plugged into existing infrastructure. Partners get programmable privacy for their users; Redacted earns on every interaction

This dual approach means Redacted's privacy layer reaches users everywhere — through our own interface for those who want the full experience, and through partner integrations for those who want privacy built into tools they already use. All revenue flows home.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.redacted.money/our-story.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
