Hyperliquid Sets 1 USDC Minimum for Bridge Transfers

Operators moving USDC into HyperCore margin accounts must send at least 1 USDC, as smaller transfers go uncredited.

Updated on Nov. 7, 2026 in Business Strategy

Bold flat-color editorial illustration of a small steel coin falling through a narrow gate into a dark navy wall, evoking a transfer threshold.
Hyperliquid set a 1 USDC minimum on USDC transfers from HyperEVM to HyperCore, meaning smaller amounts go uncredited and are lost. AI Illustration. Upload story photo >

Hyperliquid has set a 1 USDC minimum for USDC transfers moving from HyperEVM to HyperCore. Transfers below that threshold are not credited on HyperCore margin accounts, so sub-minimum amounts are lost.

Why it matters

For operators and developers using the platform's bridge, the change means small USDC transfers can disappear without any visible credit on the trading side. The threshold is enforced at the precompile gateway that moves assets between the two environments, so it applies to every transfer regardless of origin.

The minimum is set at 1 USDC for every transfer from HyperEVM to HyperCore, while HyperCore is described as capable of sustaining up to 200,000 transactions per second. Example test transfers of $0.05 and $0.50 would both fall below the threshold and go uncredited, and the extraction does not report how many transfers have been affected.

The players

Hyperliquid

Hyperliquid operates a decentralized trading platform combining a native orderbook with an EVM-compatible execution environment.

The details

The minimum is enforced at the precompile gateway, the system component that moves assets between HyperEVM, an Ethereum Virtual Machine-compatible environment, and HyperCore, the native orderbook layer. Transfers below 1 USDC leave the HyperEVM wallet but never reach the HyperCore balance, so the funds are effectively lost to the precompile. The stated purpose is to limit ledger spam and fractional state bloat, and to block bot-driven micro-dust attacks on bridge precompiles.

Timeline

  1. The effective date of the 1 USDC minimum is not specified in the source.

Market Landscape

The rule sits inside a design where HyperCore executes sub-second state transitions and HyperEVM runs alongside it, with assets passing between the two through system precompiles. A minimum transfer size is a common way for execution layers to block dust and spam, and this change applies that approach at the bridge boundary.

Users sending USDC from HyperEVM to HyperCore should confirm each transfer meets the 1 USDC minimum before sending, since smaller amounts are not credited. Operators who batch or automate bridge transfers should build a minimum-size check into their process.

The takeaway

Treat the 1 USDC minimum as a hard floor on any automated bridge flow, and add a pre-send check to avoid stranded funds. Confirm the rule's effective date and any treatment of pending transfers with the platform before relying on it operationally.

Further reading

For broader context on how platforms design operating rules to manage costs and network load, see Business Strategy.

Source note: This article includes information reported by BTC Wires.