FiatExDocs

Protocol mechanics

Permanent liquidity

The factory keeps the launch position. Neither the creator nor FiatEx has a withdrawal route for it.

What is locked

FiatEx creates v4 positions directly through PoolManager. The factory owns them, and the hook rejects liquidity removal. The contracts expose no function to transfer the position or upgrade the factory.

There is no transferable LP NFT issued to the creator. Permanent liquidity describes the withdrawal restriction more accurately than saying that a Uniswap LP NFT was minted and burned.

For a currency pool, the deposit and matching fx supply fund a full-range position. For a launched token, the initial supply funds a one-sided position. Swaps change the assets represented by each position.

This lock does not cover the external USDC/cirBTC, USDC/EURC, or USDC/MARCO bridge. Those positions belong to other liquidity providers, who keep their withdrawal rights.

A lock does not preserve a price

Trading can leave a position with far more of one asset and far less of the other. A permanent position can therefore have little usable quote liquidity. Large trades can move its price sharply or fail.

The lock does not validate a token’s creator, image, claims, or business. It does not remove contract bugs, USDC transfer restrictions, network risk, or the risk of buying into a manipulated market.

Creator tax and the platform fee are swap payments separate from the locked principal. Sending those fees to their configured destinations is not an LP withdrawal.

Verify the actual deployment

Once contracts are deployed, compare the official addresses, verified bytecode, pool key, hook address, and recorded liquidity with the release reference. A similarly named token or pool can have different rules.

The contract suite still requires an independent audit and real Arc integration verification. Local tests cannot certify that a public deployment has the same code or wiring.

Read the deployment reference