Fhenix Goes Live on Arbitrum: What Payments Still Reveal

Fhenix is live on Arbitrum, bringing fully homomorphic encryption (FHE) to applications that need to work with confidential data. For anyone considering private payroll or vendor payments, the launch raises a specific question: which parts of a payment remain visible?

The answer matters more than the privacy toggle. Amount confidentiality can protect sensitive financial information while leaving the connection between payer and recipient exposed. A business choosing a payment tool needs to evaluate both.

What went live

Arbitrum confirmed Fhenix mainnet on October 21 at 13:06 UTC, describing FHE-powered confidentiality and the ability to switch transactions between public and private modes. Fhenix subsequently introduced Genesis at 16:46 UTC as a place to explore applications, shield and unshield assets, and send confidential transactions. Both announcements were checked October 22.

These are infrastructure and application milestones. They do not establish that every token in an Arbitrum wallet now supports encrypted transfers.

Hidden amounts leave a visible payment graph

Fhenix’s dual-mode token explanation, published August 10 and modified September 4, describes one token contract maintaining public and confidential balances. FHE enables computation over encrypted values. The same explanation explicitly says sender, recipient and transaction timing remain visible, while existing DeFi compatibility is more limited on the confidential side. Checked October 22.

Consider a business paying a contractor from an address already linked to its treasury. Concealing the amount protects the size of the invoice. It does not, by itself, conceal that the two addresses transacted. Repeated payments could still suggest an ongoing commercial relationship. That is an inference from the disclosed metadata, rather than evidence that anyone has broken the encryption.

For a recipient whose main concern is salary disclosure, that may be useful protection. For a business trying to keep its supplier list confidential, the remaining visibility is a separate constraint.

Check whether the asset is dual-mode or wrapped

The Fhenix Pay manual, checked October 22, distinguishes three token types:

Token type	What the wallet documentation describes
DUAL	Public and encrypted balances inside one contract; examples include fUSD and FIX
FHERC20	A confidential wrapper around an underlying ERC-20; cUSDC is the example
ERC-20	An ordinary public token without confidential features

That distinction prevents a misleading reading of the launch. A native dual-mode design can avoid a separate wrapper, but the wallet ecosystem also documents wrapped assets. Users should inspect the particular contract and network before assuming their existing token has gained a private mode.

The manual also describes read access through permits. Sharing access with an accountant is therefore a separate decision from sending a payment. Review the scope of any disclosure request before signing it.

The exit deserves as much attention as the send

Fhenix Pay’s privacy policy, updated October 14 and checked October 22, says public balances and unshield claim amounts are visible. It also discloses that service providers receive connection information, including IP addresses and request data. Encrypting a transfer amount does not eliminate those other sources of information.

The practical consequence is to examine the full payment journey: entry, confidential transfer, disclosure and eventual exit. A private intermediate balance is only one part of that journey.

There is an availability consideration too. The wallet’s terms, also updated October 14 and checked October 22, warn that CoFHE downtime can prevent the app from displaying confidential balances, sending confidential transfers or completing unshield claims. They also explain that revoking a disclosure permit cannot undo information already seen.

Before using this for a payment, confirm the token type, what the recipient will receive, what remains public, and how the funds become spendable again. Fhenix’s launch makes amount confidentiality more accessible on Arbitrum. Whether that meets a particular payment’s privacy needs depends on the information the sender and recipient actually need to protect.