Skip to main content
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).

Arbitrum One

Arbitrum One, chain id 42161. Explorer: arbiscan.io.

Contracts

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. TOKEN and eTOKEN explains the wrapper and how note units relate to decimals. Running a relayer explains how relayerMinFee, ethPrice and usdPrice become fee quotes, and Fees and referrals 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).

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.