# Network & deployment status

The website is available at [rearctor.io](https://rearctor.io), with indexed reads at [api.rearctor.io](https://api.rearctor.io/api/health). These online services are separate from a blockchain deployment.

## Current application status

As verified on **17 September 2026**, Arc Testnet is connected to Rearctor contracts, with a separate confirmed index. Mainnet is preparing for launch and displays only REARC Coming soon. Trading remains disabled. The official Rearc token is still upcoming; the deployed factory alone does not create it.

| Component | Arc Testnet | Mainnet |
| --- | --- | --- |
| Factory, hook and treasury | Connected; test USDC only | Not connected |
| Token catalogue | Confirmed on-chain launches | REARC Coming soon |
| Official Rearctor token and pool | Upcoming; not yet launched | Upcoming |
| Wallet transactions | Available with test USDC | Disabled |

### Rearctor deployment on Arc Testnet

| Contract | Address |
| --- | --- |
| Launchpad factory | [0xf3a9F17C7DeF3f0f9cb5686270df7E2110BDF64B](https://explorer.testnet.arc.io/address/0xf3a9F17C7DeF3f0f9cb5686270df7E2110BDF64B) |
| Protocol treasury | [0x9a324aB42C2d0C363F93498484DDedC4D661793c](https://explorer.testnet.arc.io/address/0x9a324aB42C2d0C363F93498484DDedC4D661793c) |
| V4 hook | [0xCBc67AFCc4b6500795DB853156817a05C3d0A880](https://explorer.testnet.arc.io/address/0xCBc67AFCc4b6500795DB853156817a05C3d0A880) |
| Pool implementation | [0xBae6C591D292A8ac5c2b84ce50dA787c7E3EFE1C](https://explorer.testnet.arc.io/address/0xBae6C591D292A8ac5c2b84ce50dA787c7E3EFE1C) |

The current factory was deployed at block **62,563,288**. Its minimum initial liquidity starts at **1 USDC**, and the factory owner can update it for future launches. This revision retains the optimized block-opening price guard, owner-authorized eligible manual graduation and the fixed dead-wallet remainder destination. Public ABI downloads match the current implementation. These are Testnet addresses, not Mainnet deployment addresses.

## Configured network target

| Setting | Repository default |
| --- | --- |
| Chain ID | 5042 |
| Public RPC | `https://rpc.mainnet.arc.io` |
| Quote token | `0x3600000000000000000000000000000000000000` |
| Quote token decimals | 6 |
| Native gas accounting | USDC, 18 decimals |

The USDC interface and its relationship to native gas are described in [Arc's official documentation](https://docs.arc.io/arc/concepts/stablecoin-native-model). A network setting is not evidence that Rearctor contracts have been deployed there. Verify the chain ID and current deployment configuration before connecting a signing wallet.

## From Preview to live

Activating a live deployment requires verified factory, hook, pool implementations and treasury bindings; matching frontend/indexer configuration; and the factory deployment block for historical indexing. The UI rejects an API configured for another chain, factory, treasury or mode.

Once launched, the official token identity requires reciprocal treasury/factory bindings, a canonical pool and the factory's first launch matching the bound token/pool/vault. The contract can bind a canonical pool once; the first-launch requirement is an additional application identity check. A name or ticker match is insufficient.

## Authoritative checks

Read [Mainnet API health](https://api.rearctor.io/api/health), [Arc Testnet API health](https://api.rearctor.io/api/testnet/health) for mode and snapshot state, and [official identity](https://api.rearctor.io/api/official) for the currently verified token identity. These are status endpoints, not signing services. Use [Smart contracts](/docs/smart-contracts/) for verification relationships and [Permissions and liquidity](/docs/security/) for contract roles.

## Arc Testnet profile

The header selector now supports **Arc Mainnet (5042)** and **Arc Testnet (5042002)**. The testnet profile uses a separate RPC, index API, factory/treasury configuration and persistent database. Arc Testnet uses the deployment listed above. A profile without configured contracts displays Preview and disables transactions.

| Setting | Arc Testnet |
| --- | --- |
| Chain ID | 5042002 |
| Upstream RPC / wallet network RPC | `https://rpc.drpc.testnet.arc.io` |
| Browser reads and simulations | `https://rearctor.io/api/testnet/rpc` |
| Explorer | `https://explorer.testnet.arc.io` |
| USDC ERC-20 | `0x3600000000000000000000000000000000000000` |
| V4 PoolManager | `0x8366a39cc670b4001a1121b8f6a443a643e40951` |
| V4 Quoter | `0x8dc178efb8111bb0973dd9d722ebeff267c98f94` |
| Read API | `https://api.rearctor.io/api/testnet` |

Network settings come from [Arc’s RPC reference](https://docs.arc.io/arc/references/rpc-endpoints) and [contract-address reference](https://docs.arc.io/arc/references/contract-addresses). Read-only checks on 17 September 2026 confirmed chain ID, USDC precision, compatible V4 runtime bytecode and Quoter-to-manager binding on testnet. The Uniswap official deployment registry did not list this testnet; these are verified compatible testnet deployments, not a claim of registry endorsement. The primary Arc testnet RPC was unavailable from our verification environment, so the profile uses a documented alternative.

These infrastructure addresses are separate from Rearctor’s factory, treasury and token deployments. See [Admin & networks](/docs/admin/) for switching and graduation behavior.

The website sends fresh contract reads through its own domain, so browser privacy filters do not need to permit direct requests to a third-party RPC host. The relay verifies the network and supports reads and simulations only. Transaction approval, signing and submission remain with the connected wallet and its network provider.

## Optimized and previous Testnet deployments

The latest deployment adds the owner-adjustable minimum seed, initially 1 USDC, and retains the optimized block-opening execution guard. Old token contracts remain immutable and accessible through **Arc Testnet · previous**. New launches use **Arc Testnet**.

| Component | Arc Testnet | Arc Testnet · previous |
| --- | --- | --- |
| Factory | `0xf3a9F17C7DeF3f0f9cb5686270df7E2110BDF64B` | `0x3092fa4d6aF193e305F143b53a8Be55d5F07F9A7` |
| Protocol treasury | `0x9a324aB42C2d0C363F93498484DDedC4D661793c` | `0x5296dBf00226ad334E91b399bde9664818416782` |
| Hook | `0xCBc67AFCc4b6500795DB853156817a05C3d0A880` | `0xe7f0e6A18A711B257C021726df05e03887A16880` |
| Pool implementation | `0xBae6C591D292A8ac5c2b84ce50dA787c7E3EFE1C` | `0xc4DB45055B71b257560247E4B95D7658eA09E7Ec` |

The optimized factory was deployed at block **62442245**. Its pool runtime is **20,851 bytes**, below the 24,576-byte limit. Deployment verification compares compiled runtime byte-for-byte and checks constructor bindings; it does not imply that every possible economic risk has been eliminated. Source publication on Sourcify is not enabled.