> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluton.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployments

> Where Fluton Pool is deployed, with every contract and token address of the Arbitrum One deployment.

Fluton Pool runs on Arbitrum One. The wallet publishes the deployment record as
`deployment.json`: the addresses below together with `deployBlock` and `logChunk`, so a client scans
events from the deployment block in RPC-sized pages instead of asking a public node for the whole
chain. A relayer you run yourself reads the same file ([Running a relayer](https://docs.fluton.io/operators/relayer.md)).

## Arbitrum One

Arbitrum One, chain id `42161`. Explorer: [arbiscan.io](https://arbiscan.io).

| Field | Value |
| - | - |
| `network` | `arbitrum` |
| `chainId` | `42161` |
| `explorer` | `https://arbiscan.io` |
| `levels` | `20`, the tree parameter the pool was deployed with; [notes and proofs](https://docs.fluton.io/concepts/notes-and-proofs.md) explains the tree |
| `deployBlock` | `525081844`, the block the client scans events from |
| `logChunk` | `10000`, the block range of one page of that scan |
| `rpcUrl` | `https://arb1.arbitrum.io/rpc`, Arbitrum's public endpoint. Point your own client or relayer at an RPC endpoint of your own |
| `ensRpcUrl` | `https://ethereum-rpc.publicnode.com`, the Ethereum RPC the wallet resolves ENS names through |
| `relayerUrl` | `https://relayer.fluton.io` |
| `indexerUrl` | `https://indexer.fluton.io` |
| `apiUrl` | `https://api.fluton.io` |
| `screeningSigner` | [`0xBDBaEE164C8d8B5311A25F42c48BcBb6963073AB`](https://arbiscan.io/address/0xBDBaEE164C8d8B5311A25F42c48BcBb6963073AB), the address whose screenings the pool was deployed to take ([Deposit screening](https://docs.fluton.io/concepts/deposit-screening.md)) |

### Contracts

| Key | Address | What it is |
| - | - | - |
| `pool` | [`0x4242D651Ac54BF8e96a782Aa4218a3c1308Ee659`](https://arbiscan.io/address/0x4242D651Ac54BF8e96a782Aa4218a3c1308Ee659) | The address every client talks to: a `TransparentUpgradeableProxy` (OpenZeppelin 5.6), whose constructor called `initialize` in the same transaction |
| `poolImplementation` | [`0xD9a47cf770358299FA63E02423c9Cb009e1Df1D8`](https://arbiscan.io/address/0xD9a47cf770358299FA63E02423c9Cb009e1Df1D8) | The `PrivacyPool` code the proxy runs. Its own constructor disables its initializers, so it stays ownerless and inert |
| `proxyAdmin` | [`0x565341F00f44C7E0937Cad264CED2Ba0642515Eb`](https://arbiscan.io/address/0x565341F00f44C7E0937Cad264CED2Ba0642515Eb) | The `ProxyAdmin` the proxy deployed; its owner alone can call `upgradeAndCall(pool, newImplementation, data)` |
| `verifier` | [`0xc284F199ED4376B1A19AD5A052469bbBb87C38eB`](https://arbiscan.io/address/0xc284F199ED4376B1A19AD5A052469bbBb87C38eB) | Verifier for the 2-input join-split; see [circuits](https://docs.fluton.io/reference/circuits.md) |
| `verifier16` | [`0x057F3abC5E4892214b8d7Cb33C4Cb40039221540`](https://arbiscan.io/address/0x057F3abC5E4892214b8d7Cb33C4Cb40039221540) | Verifier for the 16-input join-split; see [circuits](https://docs.fluton.io/reference/circuits.md) |
| `hasher` | [`0xeC1C4Cd754ae4eF74F1c80B3b7E1Ef301A06eF10`](https://arbiscan.io/address/0xeC1C4Cd754ae4eF74F1c80B3b7E1Ef301A06eF10) | The Poseidon hasher; [notes and proofs](https://docs.fluton.io/concepts/notes-and-proofs.md) covers what it hashes |
| `confidentialLib` | [`0x2497fF8B26d9326D3a683258E57b7847FD49292D`](https://arbiscan.io/address/0x2497fF8B26d9326D3a683258E57b7847FD49292D) | The confidential-token library of this deployment; [TOKEN and eTOKEN](https://docs.fluton.io/concepts/token-formats.md) covers the eTOKEN wrappers |

`pool` is the proxy, so it is the address an upgrade keeps. All state lives in the proxy, including the CoFHE ACL grants, which name the
proxy's address, so an upgrade keeps notes, receipts, obligations and encrypted liabilities
usable. The pool's owner and the upgrader are separate roles: transferring one does not transfer
the other.

### Listed assets

Two assets are listed, each with an `id` in listing order, a plain ERC-20 (TOKEN) and its
confidential wrapper (eTOKEN). The TOKENs are the tokens' own contracts on Arbitrum One: native
USDC and the chain's wrapped ether.

| id | Symbol | Name | Decimals | `underlying` | `wrapper` |
| - | - | - | - | - | - |
| 1 | USDC | USD Coin | 6 | [`0xaf88d065e77c8cC2239327C5EDb3A432268e5831`](https://arbiscan.io/address/0xaf88d065e77c8cC2239327C5EDb3A432268e5831) | [`0xC7C9099D893Fbf113b063686cddFfEc307893956`](https://arbiscan.io/address/0xC7C9099D893Fbf113b063686cddFfEc307893956) |
| 2 | WETH | Wrapped Ether | 18 | [`0x82aF49447D8a07e3bd95BD0d56f35241523fBab1`](https://arbiscan.io/address/0x82aF49447D8a07e3bd95BD0d56f35241523fBab1) | [`0x3AAac62dC12E74Ba228a607045CF3FBfaE3bf15E`](https://arbiscan.io/address/0x3AAac62dC12E74Ba228a607045CF3FBfaE3bf15E) |

[TOKEN and eTOKEN](https://docs.fluton.io/concepts/token-formats.md) explains the wrapper and how note units relate to
`decimals`.

| id | Symbol | `mintable` | `relayerMinFee` | Price | `wrapsEther` |
| - | - | - | - | - | - |
| 1 | USDC | `false` | `"0.25"` | `usdPrice` `1` | not set |
| 2 | WETH | `false` | `"0.0002"` | `ethPrice` `"1"` | `true` |

[Running a relayer](https://docs.fluton.io/operators/relayer.md) explains how `relayerMinFee`, `ethPrice` and `usdPrice`
become fee quotes, and [Fees and referrals](https://docs.fluton.io/concepts/fees.md) why the fee is paid as a note.
`wrapsEther` marks the token as wrapped ether: the wallet shows it as ETH and wraps ETH into it on
the way in ([Using the wallet](https://docs.fluton.io/wallet/using-the-wallet.md#shield-a-token)).

### What the record does not tell you

Treat the record as what was deployed rather than as the live configuration: the owner of the pool
can name another screening signer, schedule another fee rate and list more tokens afterwards, and
the owner of `proxyAdmin` can replace the pool's code entirely. Read the live values from the pool.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.