# Integration Plan & Rollout

{% hint style="info" %}
Operator and jurisdiction: BASIS is operated by BASIS DIGITAL INFRASTRUCTURE LTD, a Seychelles IBC (LEI: [254900IX2F2KCWNSSS64](https://lei.bloomberg.com/leis/view/254900IX2F2KCWNSSS64)).
{% endhint %}

PAXG integration is deployed through a phased rollout with explicit operational gates.

A research-led platform does not activate complex modules in a single step. Each phase is validated through deterministic execution checks, state machine controls, venue health monitoring, and reconciliation requirements.

## Phase 0: Research and feasibility

### Deliverables

* Venue coverage analysis across spot and derivatives markets
* Liquidity depth study by venue and time window
* On-chain cost study including gas behavior and execution precision conditions
* Issuer risk surface mapping, including disclosures, controls, and redemption constraints

### Output

* Eligibility rules draft
* Risk addendum draft
* Monitoring dashboard requirements

{% hint style="warning" %}
PAXG support is active on BASIS. This phase defines research, control logic, and parameterization before broader strategy activation.
{% endhint %}

## Phase 1: Spot support and monitoring

### Enable

* PAXG deposits and withdrawals in the Funding Wallet
* PAXG to stPAXG same-token 1:1 swap
* Monitoring surfaces for price, depth, deviation, and venue health

### Do not enable yet

* DEX to CEX structural alpha capture modules
* Collateral optimization modules

### Goal

* Verify operational stability
* Validate reporting and accounting
* Confirm wallet, swap, and custody state transitions

{% tabs %}
{% tab title="User flow" %}

1. Connect a supported Web3 wallet
2. Deposit PAXG into the Funding Wallet
3. Swap PAXG to stPAXG at 1:1
4. Stake stPAXG in the Staking Wallet
5. Monitor rewards accumulating in real time as stPAXG
   {% endtab %}

{% tab title="Operational checks" %}

* Deposit confirmation integrity
* Funding Wallet and Staking Wallet balance reconciliation
* Swap parity validation at 1:1
* Withdrawal processing latency validation
* Venue and oracle deviation monitoring
  {% endtab %}
  {% endtabs %}

## Phase 2: Golden BASIS module

### Enable

* Spot-perpetual delta-neutral structural alpha capture
* Access only on whitelisted venues with strong liquidity
* Strict liquidation guards and exposure caps

### Goal

* Validate hedge mechanics
* Validate funding stability under stress
* Confirm deterministic execution quality across routing paths

{% hint style="info" %}
Execution standards are enforced through math-based constraints, deterministic routing logic, and risk controls designed to preserve capital under adverse conditions.
{% endhint %}

## Phase 3: DEX-CEX and collateral optimization

### Enable

* DEX-CEX module only when on-chain conditions satisfy execution precision thresholds
* Collateral optimization only on a strict protocol whitelist with conservative parameters

### Goal

* Expand the opportunity surface without compromising capital preservation
* Maintain reconciliation quality and operational predictability

### Control requirements

| Control area       | Requirement                                                    |
| ------------------ | -------------------------------------------------------------- |
| On-chain execution | Gas and execution precision must remain within approved bounds |
| Protocol access    | Whitelist only                                                 |
| Position sizing    | Conservative caps                                              |
| Failure handling   | Automatic pause and state transition controls                  |
| Monitoring         | Real-time venue, chain, and collateral health checks           |

## Phase 4: Full integration and public reporting

### Publish

* Module performance breakdowns by realized yield contribution
* Incident and pause statistics
* Parameter change logs
* Reconciliation summaries where applicable

A trust-first platform proves performance through evidence, reconciliations, and repeatable control behavior.

***

## Live PAXG support on BASIS

PAXG is fully active on BASIS.

### Supported wallet and asset behavior

| Item                      | PAXG                   |
| ------------------------- | ---------------------- |
| Deposit method            | Web3 wallet connection |
| Wallet type               | Funding Wallet         |
| Swap supported            | PAXG → stPAXG only     |
| Swap ratio                | 1:1                    |
| Withdrawable asset        | PAXG                   |
| Reward asset              | stPAXG                 |
| Estimated withdrawal time | 1–6 minutes            |

{% hint style="success" %}
PAXG follows the standard BASIS asset model:

* Funding Wallet: native token custody, deposit, withdrawal
* Staking Wallet: stToken balance, staking, reward accrual
* Rewards: accumulate in real time as stPAXG
* Unstake: full position only
* Claimable amount: automatically credited to the Staking Wallet as stPAXG after the 7-day unstaking buffer is complete.
  {% endhint %}

## Platform controls relevant to rollout

BASIS infrastructure applies the same control philosophy across active assets, including PAXG:

* Deterministic execution
* Math-constrained position logic
* State machine risk controls
* Proprietary routing infrastructure
* BHLE architecture with sub-50μs latency and 100K+ OPS capability
* Research support from Base58 Labs

A phased rollout is not delay for its own sake. It is how production systems preserve capital, maintain accounting integrity, and scale safely.


---

# Agent Instructions: 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:

```
GET https://docs.basis.pro/paxg-integration/integration-plan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.