Nomad Review: Is Its Bridge Safe to Use?

Nomad was built as a cross-chain messaging protocol, not a standalone blockchain. Its smart contracts connect chains, while an off-chain component supports message monitoring. For regular users, the project advertised an ERC-20 token bridge; for developers, its messaging channels were intended to carry arbitrary data and enable cross-chain contract calls.

The project describes its security model as optimistic: messages can be challenged by off-chain watchers using fraud proofs, rather than relying on custodians or a validator set. The stated network list includes Ethereum, Moonbeam, Milkomeda and Evmos. Treat that as a description of Nomad’s deployments, not confirmation that every route is currently operating or safe. The homepage still presents a bridge launch option, but a visible interface alone does not establish that contracts are maintained or that transfers will complete. If you are considering Nomad, first verify the exact route and current contract status through reliable, up-to-date project communications.

Nomad does not publish a clear current fee schedule in its project information. The protocol has described itself as reducing gas costs compared with traditional header-relay systems, but that claim is not a substitute for a live quote or a guarantee of what a transfer will cost you now.

A bridge transaction can involve more than one cost: the bridge may charge a fee, and you generally need gas for transactions on the source chain and potentially the destination chain. Network congestion can affect gas costs. Before confirming any transfer, inspect the full transaction details in your wallet and check whether the interface shows a bridge fee, exchange rate, minimum amount or amount the recipient will receive. If those details are missing or unclear, do not approve the transaction. Given Nomad’s security history, even a low quoted fee would not make an unverified route a sensible choice.

The central issue is Nomad’s August 2022 exploit, when roughly $190 million in crypto assets was taken. This history materially changes the risk assessment: cross-chain bridges hold or control assets in contracts, and a flaw in message verification can put funds at risk across connected networks. Nomad’s optimistic design and its claim that one honest actor can keep the system safe do not eliminate that possibility.

No audits are listed in the project information, and the present security status of its contracts is not established. That does not prove that no audit ever occurred, but you should not assume an old review covers current deployments or later changes. The site also displays a request for the return of ETH or ERC-20 tokens to a specified wallet. Verify any recovery or bounty instructions through trusted official channels before sending funds; a displayed address by itself is not proof that a transfer is safe. Do not deposit while the project’s current security and operating status remain unclear.

Nomad’s advertised flow is to connect a wallet, choose an ERC-20 token and source and destination chains, then review and confirm the transfer. The listed networks are Ethereum, Moonbeam, Milkomeda and Evmos. The project also describes an SDK and messaging channels for developers building applications that communicate across chains.

That describes the intended product, not a confirmation of current service quality. Nomad does not clearly publish current route availability, transfer times, withdrawal limits or a support commitment. A cross-chain transfer may also require separate transactions and gas on the relevant networks. If you are a developer, inspect the specific contracts and documentation you plan to integrate rather than relying on general protocol descriptions. If you are a token holder, do not connect a wallet or approve a token allowance until you have verified that the exact route is live and that the contracts are appropriate for your transaction.

Nomad’s largest shortcoming is not a missing convenience feature; it is the combination of a major past exploit and unclear current security and operational details. The advertised list of chains does not tell you which routes still work, whether contracts have changed, or whether any recovery process is active. Fees, current transfer times and route limits are also not clearly published.

There is no project token listed, so there is no token to buy as part of using the bridge. But that does not reduce the risk of sending assets through its contracts. If you need to move funds, compare alternatives based on current contract audits, incident history, transparent fees and reliable route status. Do not choose Nomad solely because its interface appears available, or because the protocol describes its design as secure and low-cost. Until current operations and security are independently verifiable, a different bridge is the more prudent option for transfers.