# Technical Infrastructure

### 1) Network & Deployment

0Fx is deployed on **Arbitrum One**, an Ethereum Layer 2 network designed for high throughput and lower transaction costs while inheriting Ethereum security guarantees.

* **Network:** Arbitrum One
* **Chain ID:** 42161
* **Gas token:** ETH
* **Explorer:** Arbiscan

***

### 2) Token Contract

The 0Fx token is implemented as a standard ERC-20 contract deployed using the **DODO token launcher** template (based on widely used ERC-20 launch templates).

* **Standard:** ERC-20
* **Max supply:** 500,000 0Fx
* **Token contract:** [`0x73e2226dA3e8bd78155f70FDc5d13A85585Cd899`](https://arbiscan.io/token/0x73e2226dA3e8bd78155f70FDc5d13A85585Cd899)
* **DODO launcher:** [`https://dodoex.io/`](https://dodoex.io/en) *(official reference)*

> Contract verification and source code are publicly accessible through the explorer.

***

### 3) Liquidity Infrastructure

0Fx liquidity is primarily organized around a **Uniswap V3 pool**.

* **DEX:** Uniswap V3
* **Pool:** 0Fx / wstETH
* **Pool address:** [`0xAf1AdDBfeb890839D38020061A109B9346ffbEC9`](https://arbiscan.io/address/0xaf1addbfeb890839d38020061a109b9346ffbec9)

#### Base asset: wstETH

wstETH (Wrapped staked ETH) is used as the base asset to maintain structural alignment with ETH while benefiting from Ethereum staking yield mechanics.

* **wstETH contract:** [`0x5979D7b546E38E414F7E9822514be443A4800529`](https://arbiscan.io/token/0x5979D7b546E38E414F7E9822514be443A4800529)
* **Lido:** [`https://lido.fi/`](https://lido.fi/) *(official reference)*

***

### 4) Protocol-managed Liquidity Model

A significant portion of the maximum supply is allocated to support liquidity in the primary pool.\
This creates strong market accessibility and reduces early-stage fragmentation.

This liquidity is managed through controlled operational wallets (multisigs) and is designed to be:

* **transparent** (on-chain verifiable),
* **adjustable through governance** (as governance matures),
* **progressively decentralized** over time via increasing external LP participation.

***

### 5) Multisig Wallets & Operational Security

0Fx uses multisig wallets to separate responsibilities and reduce operational risk.

#### Protocol / DAO Operations Multisig

* **Address:** [`0x6e52dd64b0daa77e94ca68f93fb6fa879a19ad5d`](https://arbiscan.io/address/0x6e52dd64b0daa77e94ca68f93fb6fa879a19ad5d)\
  Used for protocol-level operational actions, ecosystem maintenance, and infrastructure coordination.

#### Founder Strategic Reserve Multisig

* **Address:** [`0x5a151e6ed9e1df0deb19a5eda1fa16415e45102d`](https://arbiscan.io/address/0x5a151e6ed9e1df0deb19a5eda1fa16415e45102d)\
  Holds the founder strategic reserve allocation, intended to support long-term development and alignment.

> At the current stage, multisigs are managed by the core contributor(s). Governance mechanisms are expected to mature progressively as the ecosystem decentralizes.

#### Vesting / Large Holders Multisig

* **Address:** [`0x6e52dd64b0daa77e94ca68f93fb6fa879a19ad5d`](https://arbiscan.io/address/0x6e52dd64b0daa77e94ca68f93fb6fa879a19ad5d)\
  Used for structured vesting custody and long-term allocation management.

***

### 6) Off-chain Agents (Data & Execution)

To support ecosystem operations and the 0Fx Capital product layer, the infrastructure includes dedicated off-chain agents.

#### Market Data Indexing Agents (x4)

Used to fetch and index price data for assets used in 0Fx Capital index products, enabling:

* product NAV calculation,
* real-time pricing display,
* analytics and monitoring.

#### Market Activity / Liquidity Monitoring Agent (x1)

Used to monitor liquidity conditions and market activity, and execute predefined operational actions when necessary to support ecosystem functionality (such as price index freshness and market accessibility).

> These agents provide operational tooling but do not override on-chain execution rules.


---

# 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://0fx-protocol-1.gitbook.io/0fx-protocol-docs/protocol/technical-infrastructure.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.