Bitcoin bridge dust minimums depend on more than BTC’s dust limit

There is no universal Bitcoin bridge dust minimum in 2026: Bitcoin nodes apply an output floor, while each bridge sets its own deposit rules and fees. Those limits answer different questions. Dust policy asks whether an output is economical enough to relay under a node’s settings; a bridge minimum asks whether its service will process a deposit. A payment can clear one limit and fail the other. Check the exact deposit instructions before sending.

Bitcoin Core’s default dust relay fee has been 3,000 satoshis per kilobyte, or 3 sat/vB, in its policy code. At that baseline, its familiar dust thresholds include 546 sats for a legacy P2PKH output and 294 sats for a native SegWit P2WPKH output. These figures come from Bitcoin Core’s output-and-spend-size calculation; they are not bridge minimums or transaction fees. If you are weighing historical RenBridge mechanics, this guide to questions about moving BTC through RenBridge covers that decision in more detail.

What does Bitcoin’s dust limit actually mean?

Bitcoin’s dust limit is a relay-policy threshold for an individual spendable output. Bitcoin Core estimates the size of the output and a typical future input that would spend it, then multiplies that size by the configured dust relay fee. An output below the result is usually rejected as non-standard by nodes using that policy. The threshold can vary with the output script and node configuration.

This is a policy rule, not a consensus rule. A below-threshold output is not inherently invalid under Bitcoin’s consensus rules, but ordinary wallet and node paths may refuse to relay the transaction. The practical distinction matters: a displayed “minimum send” in a wallet may reflect its own settings, its chosen address type, or its provider’s rules. It is not necessarily a network-wide minimum.

Dust also differs from the fee needed to get a transaction confirmed. The fee is paid for the transaction’s size and is affected by demand for block space. Dust is a limit on the value of a particular output under a relay policy. A transaction can have an output above the dust threshold and still pay too little to confirm promptly; a high fee does not automatically make an otherwise rejected dust output acceptable.

How much BTC should you send to a bridge?

Send at least the bridge’s stated minimum deposit, plus enough BTC to cover the Bitcoin transaction fee from your wallet. The bridge minimum is service-specific: it may account for processing costs, the amount of the asset issued on the destination chain, or the bridge’s settlement design. It can be much higher than a few hundred satoshis, and it can change independently of Bitcoin node policy.

Before sending, use this short check:

• Confirm the bridge supports BTC on the source network and the asset and network you intend to receive.
• Read the current minimum deposit and any maximum, confirmation, or refund conditions on the deposit screen.
• Check whether the stated minimum is before or after service fees, and whether the Bitcoin network fee is separate.
• Compare the amount you will send with both the service minimum and the amount you expect to receive after fees.

Bridge deposits can involve more than one transaction or a wait for confirmations before the destination asset is issued. That means the service’s quoted minimum may reflect its own processing path, not just the size of the Bitcoin output. A small test transfer can help verify an address and route, but it may be uneconomical if it falls below the service minimum or incurs fees disproportionate to the amount. Do not assume an under-minimum deposit will be automatically returned.

Why can the minimum differ between wallets and bridges?

Wallets and bridges control different steps. A wallet builds and broadcasts a Bitcoin transaction, selecting inputs, calculating a fee, and creating outputs. The bridge observes a deposit and applies its own rules before crediting or issuing anything on another chain. The wallet may permit a transfer that the bridge will not process, or the bridge may require more BTC than the wallet’s dust check would suggest.

Output type is another difference. At Bitcoin Core’s default 3 sat/vB dust-relay baseline, P2PKH and P2WPKH outputs have different thresholds because their estimated spending sizes differ. The same nominal amount can therefore be treated differently depending on the destination script. Those values describe node policy; they do not predict how much a bridge accepts or how much the transaction will cost to confirm.

RenBridge is a historical case rather than a current route to use: Ren’s team announced in December 2022 that Ren 1.0 was being sunset amid uncertainty over funding for its planned Ren 2.0 transition. Its past deposit parameters should not be treated as live instructions. For any bridge, the current service interface and status matter more than old minimums quoted in guides or forum posts.

What should you watch before sending BTC?

For most readers, the better rule is to treat the live bridge minimum as the controlling amount and Bitcoin’s dust threshold as a separate technical floor. Check the minimum at the time of transfer, since service rules can change; inspect whether the quoted amount includes fees; and confirm the receiving chain and asset match your plan. If the bridge does not clearly state how it handles under-minimum deposits, do not send an amount that depends on an exception.

The signals worth watching are the bridge’s published minimum, fee breakdown, confirmation requirements, and status notices, alongside the transaction fee shown by your wallet. Bitcoin Core’s dust relay setting and the output type help explain whether a transaction is likely to relay. They cannot guarantee that a bridge will credit it. The actionable minimum is the higher service requirement, with the network fee budgeted separately.