ETH → NEAR

ETH -> NEAR: what makes this pair specific

ETH and NEAR live on completely separate chains. Ethereum is account-based with EIP-1559 fee markets; NEAR is sharded, uses human-readable account IDs (yourname.near), and settles in roughly 1-2 seconds with sub-cent fees. There is no native bridge step inside an aggregated swap - the service handles the cross-chain leg internally, so you send ERC-20-compatible ETH from any wallet and receive native NEAR at a NEAR account, not a wrapped representation on Aurora unless you specifically request it.

Liquidity for this pair is decent but thinner than ETH -> SOL or ETH -> BNB. Expect rate spreads to widen on amounts above ~20 ETH; for larger sizes, splitting across two providers from the comparison table often beats a single quote.

Choosing a route and sizing the trade

• Confirm the destination is a real NEAR implicit or named account - sending to an Aurora (0x...) address by mistake routes funds to the EVM shard and may require manual recovery.
• Check whether the quoted rate is floating or fixed. Fixed rates lock for 5-15 minutes but cost 0.5-1.5% more; floating rates settle at execution time and can drift if ETH confirmations are slow.
• Mind the minimum - NEAR's low unit price means some providers set ETH minimums around 0.01-0.02 to avoid dust on the output side.
• Refund address: always set an ETH refund address you control. If the quote expires mid-transit, funds return there, not to the sending wallet by default on every service.

Practical timing: Ethereum base fees swing widely. Submitting during low-gas windows (typically weekends, UTC late evening) saves 30-60% on the inbound leg. NEAR-side delivery is near-instant once the swap engine sees enough ETH confirmations - usually 12-25 blocks depending on the provider's risk policy.

For security, verify the NEAR account exists before sending. Unregistered named accounts can cause delivery to fall back to an implicit address you may not control.