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

# Technical Roadmap

<figure><img src="/files/jOfeosuP64I60oCupUy2" alt=""><figcaption></figcaption></figure>

### Q4 2024: Alpha Testing

{% hint style="info" %}
For more details on how the PHT system forked MakerDAO's Multi Collateral DAI, please see see the audit section:\
[Smart Contract Audits](/technical-references/smart-contract-audits.md)
{% endhint %}

The alpha testing stage includes the following activities;

1. Initial fork and deployment of MakerDAO's Multi Collateral DAI
2. In-house UI development
3. Initial QA, testing and liquidity provision by team
4. First audit by SlowMist

### Q1-Q2 2025: Beta Testing

{% hint style="info" %}
Initial beta testing rollout implements custodial collateral types based on MakerDAO's RWA vaults. This ensures that collateral is 100% safe from on chain security incidents, while the PHT system is in its' early stages.&#x20;
{% endhint %}

{% hint style="info" %}
During this stage, custodial collateral types are transparently listed in wallets, so that all users, LPs or PHT holders may verify the collateral backing PHT. \
\
See [Transparency](/transparency.md) page for more information.&#x20;
{% endhint %}

The beta testing stage includes the following activities;

1. PHT Minting and Redemption
2. Custodial Collateral Types
3. LayerZero integration for PHT cross chain bridging

<table><thead><tr><th width="214">Collateral Type</th><th>Description</th><th>Rationale</th></tr></thead><tbody><tr><td>apcxUSDT</td><td>`apcxUSDT` represening custodial collateral reflects USDT backing of PHT in reserves</td><td>Initial beta testing rollout implements off chain collateral types forked from MakerDAO's RWA vaults. This ensures that collateral is 100% safe from on chain security incidents, while the PHT system is in its' early stages. </td></tr><tr><td>apcXUSDT</td><td>`apcxUSDC` represening custodial collateral reflects USDT backing of PHT in reserves</td><td>Initial beta testing rollout implements off chain collateral types forked from MakerDAO's RWA vaults. This ensures that collateral is 100% safe from on chain security incidents, while the PHT system is in its' early stages. </td></tr></tbody></table>

### Q2-Q3 2025: Preparation and Full Version 1 System Launch

{% hint style="info" %}
Version 1 System Launch entails all aspects of the PHT Multi Collateral System are live, including the permissionless stability mechanism and full on chain collateral with USDC and USDT.&#x20;
{% endhint %}

This stage includes the following activities;

1. Fully permissionless USDC and USDT collateral types
2. Solidified operational security
   1. Established security council
   2. multiple audits
   3. Multiple collateral custodians for any custodial reserves
3. Fully active stability mechanism to keep PHT price peg even if more volatile collateral types are used


---

# 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.apacx.io/technical-roadmap.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.