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

# Roadmap

Redact roadmap consists of 5 phases:

1. Phase 0 - Testnet Deployment (current stage)
2. Phase 1 - Mainnet Launch
3. Phase 2 - Core Components Polish
4. Phase 3 - Ecosystem Expansion
5. Phase 4 - UX Optimization

<figure><img src="https://3289548442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBtZLqCP6brcfNsL0LJh%2Fuploads%2Fip5elgBnCrq6EQosDrfY%2FRedact%20Roadmap.png?alt=media&amp;token=27fa52b0-8407-439e-af14-f3d5c08cb2d6" alt=""><figcaption><p>Redact Roadmap Illustration</p></figcaption></figure>

## Phase 0 → Testnet Deployment

**Goal:** Launch Redact on the testnet to introduce confidential DeFi for initial use

* **Encrypt**

  Encrypt ERC20 token balances into fhERC20 confidential token balances.
* **Decrypt**\
  Decrypt fhERC20 token balances back into ERC20 public token balances.
* **Confidential Transactions**\
  Privately send confidential tokens between wallets, the amount sent is encrypted and private (confidentiality), but the sender and receiver are public (non-anonymous).

## Phase 1 → Mainnet Launch

**Goal**: Deploy Redact on mainnet

* **Mainnet launch**\
  Deploy contracts, update frontend network configs, run pre-launch smoke tests.
* **Performance & load testing**\
  Validate end-to-end flows at scale (wrapping, minting, transfers).
* **Monitoring & alerts**\
  Stand up on-chain telemetry and on-call dashboard for quick incident response.

## Phase 2 → Core Components Polish

**Goal:** Round out foundational UX & privacy flows&#x20;

* **Multi-wallet connect**\
  Ensure users can connect multiple wallets.
* **Smart wallet integration**\
  Finalize Alchemy Smart Wallet SDK flows: creation, import, signing.
* **Wallet optimization**\
  Triage and fix performance/UI glitches in the in-dApp wallet.

## Phase 3 → Ecosystem Expansion

**Goal:** Grow reach via incentives and new chains

* **Deployment on additional EVM-chains**\
  Roll out Redact contracts & UI to one or two testnet/mainnet EVM forks (e.g. Polygon, BSC).
* **Rewards mechanism release**\
  Launch the opt-in yield-rewards module on mainnet.

## Phase 4 → UX Optimization

**Goal:** Drive adoption with polished experiences

* **Mobile version optimization**\
  Refactor responsive layouts, performance budgets, touch-flow refinements.
* **Ongoing wallet optimization**\
  Iterate on UX (batch txs, gas-fee hints, balance sync), reduce latency further.
* **Confidential tx hardening**\
  Add final checks (fraud-proofs, replay protection) and audit fixes for confidential transfers.
* **Shared permits integration**\
  Wire up fhERC-20 permit issuance on login for confidential-data decryption.<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.redact.money/roadmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
