DEV Community: Kendra Koepp

Blackhole swap costs in 2026: estimate your first trade

Kendra Koepp — Wed, 30 Sep 2026 16:16:03 +0000

A token swap costs more than its pool fee. To estimate the full cost, check the trade price, the fee built into it, and the separate network charge.

The pool fee is part of the exchange rate; gas is a separate network charge.
Price impact depends on your trade size and the pool’s available tokens.
Slippage is a limit on price movement, not an extra fee.

What makes up the cost of an Avalanche swap?

A swap usually has three cost parts: the pool fee, price impact, and gas. A liquidity pool is a shared supply of tokens that traders swap against. Its fee is taken from each trade, often as a percentage of the amount swapped.

For an example, imagine a pool fee of 0.3% on a $1,000 trade. That equals $3, usually reflected in how many tokens the pool returns. This is an illustration, not a current rate for every pool; the fee depends on the pool you use.

Price impact is the change your trade causes in the pool’s price. A small trade in a deep pool may have little impact. The same trade in a shallow pool may return fewer tokens, even before the network charge.

Gas is the fee paid to the Avalanche network to process your transaction. It varies with network activity and the work the transaction requires. Your wallet normally shows an estimate before you approve the trade.

How do you estimate the amount you will receive?

Start with the quoted output: the number of tokens the swap says you should receive. Compare it with the market price, then account for the pool fee and price impact. The quote usually reflects both, so do not subtract them again if they are already included.

If you plan to trade through Blackhole swap, the Blackhole swap fees article can help you consider the fee side. Check the quote for your specific token pair and trade size, since pool depth affects the result.

Slippage tolerance sets how much the price may move before the swap is rejected. It is not a charge. A very low setting can make a trade fail if the price shifts; a very high setting can allow a worse price than you intended.

For instance, if a quote shows 50 tokens, a 1% slippage limit means you accept a minimum of 49.5. That figure is an example. Use the quote and limit shown for your own trade, and check the token pair carefully before approving.

What should you check before approving?

Before confirming, check the network, the token names, the estimated output, and the gas estimate. Avalanche uses different networks for different purposes; a wallet must be connected to the network where the tokens and pool exist. WalletConnect is a way to connect some wallets to apps by scanning or approving a connection request.

A common first-trade mistake is judging cost only by the quoted output. Fix that by noting the output and gas estimate before approval, then comparing them with your wallet balance afterward. A failed transaction can still use gas if it reached the network.

For a first trade, use a small amount and a clear quote. Blackhole swap is one way to make an Avalanche pool trade, but the pool’s depth and your chosen tokens determine the result. Check those details before you confirm.

How to Test a ZeroFi XMR Deposit on Sepolia

Kendra Koepp — Wed, 30 Sep 2026 11:38:40 +0000

Testing a ZeroFi XMR deposit on Sepolia means sending a small amount of real Monero and checking that the bridge issues testnet zXMR to your EVM wallet. The key condition is that Sepolia is a test network: its zXMR demonstrates the transfer flow, but it is not mainnet zXMR or spendable value.

What does Sepolia change?

Sepolia is an Ethereum test network, so transactions there use test ETH for gas and do not settle on Ethereum mainnet. The bridge’s current interface lists Monero XMR as the source, Sepolia as the destination, and a chain ID of 11155111; chain ID is the number wallets use to identify a network.

That means a test can still involve real XMR leaving your Monero wallet. The zXMR you receive on Sepolia is a test-network token, so don’t count it as money you can sell or use in mainnet DeFi. Treat the XMR you send as funds at risk, even when the destination is only a testnet.

What should I prepare before sending XMR?

Prepare a Monero wallet with a small amount of XMR and an EVM-compatible wallet set to Sepolia. Your EVM wallet needs Sepolia ETH if the flow asks you to approve or submit an on-chain transaction; test ETH pays gas on Sepolia and has no mainnet value. Keep your wallet recovery phrases and private keys private throughout.

Check the bridge’s displayed minimum before you start. Its current interface shows a minimum deposit of 0.01 XMR, so an amount below that may not be processed; the displayed minimum can change. Use the smallest amount the interface accepts, and make sure you can afford the Monero network fee as well as the deposit.

Before confirming, check that the receiving EVM address is yours and that the destination says Sepolia. Monero transactions are private, so a public explorer may not show the sender and amount as plainly as an Ethereum explorer does. Save the transaction ID from your wallet so you can track the deposit in the bridge explorer.

How do I follow the deposit from XMR to zXMR?

Start the deposit in the bridge interface and follow its prompts to get the XMR deposit details. Send the amount from your Monero wallet to the displayed deposit address, then save the Monero transaction ID. A transaction ID is the unique string that identifies your payment; it lets you check whether the transaction has been included in a Monero block.

The bridge currently requires 10 source-chain confirmations for deposits. A confirmation is one block added after the block containing your transaction; Monero blocks arrive roughly every two minutes, so ten confirmations can take around 20 minutes, with actual timing varying. The bridge also lists 10 sweep confirmations: a sweep is the bridge’s later movement of deposited funds, which has its own confirmation wait.

After those steps, check the receiving wallet while it is connected to Sepolia. If zXMR does not appear automatically, the wallet may need the token added using the contract address shown by the bridge. Verify that address against the bridge’s current published details before adding it; a token with the same name at another address may be unrelated.

What if the deposit is still pending?

A pending status can mean the Monero transaction has not yet reached the required confirmations or the bridge is still processing its sweep. Search the saved transaction ID in the bridge explorer and compare its status with the confirmation requirements; avoid sending a second deposit just because the first one is taking time. If the transaction never appears, check the address and amount you used before contacting the project through its official support channel.

Once you’ve checked the amount, network, and transaction status, you’ll know whether you’ve completed a test transfer or need to wait for processing. The ZeroFi Monero bridge is where you can check the current deposit requirements before starting; remember that a Sepolia result is a test of the flow, not proof of mainnet redemption or value.

How to Move Staking Rewards to a Higher-Yield Chain

Kendra Koepp — Tue, 29 Sep 2026 22:19:22 +0000

Move only rewards you can withdraw freely when the destination’s expected return still beats the full cost and added risk. Your original stake can usually stay where it is; moving rewards is a separate job that may involve claiming, swapping and bridging tokens.

A staking reward is what you earn for helping secure a proof-of-stake network, often by delegating tokens to a validator. It may arrive as a spendable balance, or stay inside a staking account until you claim or withdraw it. Check which applies before planning a move.

Rango Bridge can help find a cross-chain route when your reward token and the token you need on the destination chain differ. Routes may combine a swap with a bridge, so the asset that arrives can be different from the one you send. rangobridge.com is the service that can route this kind of cross-chain swap.

Separate claimable rewards from your staked principal

Only move rewards that are available to spend; your principal may have a separate withdrawal process. On Cosmos Hub, for example, claiming delegation rewards makes them spendable while the delegated ATOM remains staked. On some networks or staking services, rewards may be added to a position or require an unbonding period before withdrawal.

That distinction changes the task. If rewards are already liquid, you can plan a transfer while leaving the original stake alone. If they are locked or auto-restaked, first check the provider’s rules and waiting period; a cross-chain route cannot release funds that are still locked.

Compare the return after costs and risk

A higher advertised yield does not automatically mean you will earn more. Compare the destination’s expected annual return with the source return, then account for transaction costs, token price changes, and the risks of the destination staking or lending protocol.

For example, imagine you have $20 in claimable rewards. In Case A, keeping them in the source token earns a hypothetical 4% a year. In Case B, swapping them into a destination token with a hypothetical 7% staking return adds $1.40 per year before costs, compared with $0.80 at 4%. That extra $0.60 is only an illustration: the rates can change, and a fall in the destination token’s price could outweigh the difference.

Check whether the quoted rate is APR, which usually excludes compounding, or APY, which includes it. Also check the minimum amount needed for the destination position: small rewards can be consumed by source-chain gas, route fees, swap spread, and the cost of a later transaction on the destination chain.

Use this sequence to move the rewards

Confirm the reward is spendable. Open your wallet or staking provider and identify the reward balance separately from your delegated or staked principal. If it is not available to transfer, find out whether claiming, withdrawing, or waiting through an unbonding period is required.
Choose the destination asset and activity. Decide whether you want to stake a token, lend it, or use another yield strategy. These are different activities with different risks; a lending rate is not directly comparable to a staking rate.
Check that the route matches your goal. Note the reward token and source chain, then the token and chain you want to receive. Rango Bridge is a cross-chain routing service for finding routes across networks; a route may swap the reward token, move value between chains, or do both. Read the quoted result carefully to confirm the destination asset is the one your chosen yield activity accepts.
Leave enough for the transactions. Keep some source-chain token for the claim or send transaction, and plan for destination-chain gas if you need to stake after arrival. The exact cost depends on the chains, route, congestion, and swaps involved; moving a very small reward may not be worthwhile.
Review and complete the transfer. Check the source amount, destination chain, receiving asset, and estimated amount after any swap before signing. A cross-chain route can involve source-chain confirmation and processing before funds appear on the destination, so wait for completion and verify the received token in your wallet.
Put the received funds to work. Use the destination network’s normal staking or lending process, and verify that the position shows the amount you expect. Keep a record of the route and your starting value so you can compare the actual return later.

Recheck the yield after the move

Once the rewards are earning on the destination chain, revisit the comparison when rates, token prices, or your plans change. A yield that looked attractive at the time of transfer may fall, and moving again will cost more and add another round of route risk.

Use one short safety check before signing: confirm the token, destination chain, and receiving address, and make sure you are using the intended service. Cross-chain transfers can be difficult or impossible to reverse if sent to the wrong network or address.

Before acting, ask yourself: after fees, price risk, and the destination protocol’s risk, is the expected extra return worth moving these rewards?

Bungee Bridge: 5 Checks for Team Transfers

Kendra Koepp — Tue, 29 Sep 2026 16:39:53 +0000

Bungee Bridge fits team transfers when a route meets your asset, net receipt, timing, approval and recordkeeping requirements. Bungee Bridge finds bridge and exchange routes for a specific transfer so your team can compare them before moving funds. Check the destination token contract and keep the transaction records for reconciliation.

What is Bungee Bridge?

It is a cross-chain bridge aggregator built by Socket that searches routes through bridges and decentralized exchanges (DEXs). A route may swap a token on the source chain, bridge it, then swap it again on the destination chain. The result depends on the particular route, not merely the names of the two networks.

bungeebridge.co is the official service for comparing these cross-chain transfers. For a useful comparison, your team needs the source and destination chains, the token on each chain, the amount and the receiving address. A token name alone is insufficient: two assets called USDC can have different contract addresses and acceptance rules.

Which Five Checks Decide the Route?

Check asset identity, net receipt, arrival time, execution requirements and the record your team will need afterward. These are the points that can change which route works for a treasury transfer or payout.

Asset identity: Will the recipient receive the intended token on the intended chain?
Net receipt: How much arrives after the route’s costs and swaps?
Arrival time: Does the route fit the payment deadline?
Execution requirements: What must the treasury signer approve and submit?
Records: Can the team prove and reconcile delivery?

Asset identity. Check chain IDs and token contract addresses on both ends; Ethereum is chain ID 1 and Base is 8453. A common mistake is to approve a transfer because the quote says “USDC,” then discover that the recipient expected a different USDC contract. Fix it by confirming the destination contract with the recipient before comparing routes. If the required asset has no available route, changing the bridge alone will not solve the payout.

Net receipt. Compare the amount expected at the destination after bridge charges, exchange price impact and any swap slippage, then account for source-chain gas. For an illustrative $10,000 transfer, one route might quote $9,970 received and another $9,945. If the first also costs $35 more in gas, the second leaves the team $10 ahead overall. Refresh quotes before signing because gas prices and exchange liquidity change.

Arrival time. Use the route’s time estimate against the actual payment cutoff, while allowing for source confirmation and destination settlement. A fast estimate is less useful if a delayed payout would miss payroll or an exchange deposit window. Bridge mechanisms can have very different settlement times, and an estimate is not a guarantee. For time-sensitive transfers, decide the latest acceptable arrival before choosing the cheaper quote.

Execution requirements. An ERC-20 transfer may need a token approval as well as the transfer transaction; some routes may involve further action after the source transaction. Check the approval amount, the contract receiving it, the minimum amount receivable and whether your treasury signer can perform every required action. For a controlled wallet, the route with the highest quoted output may be unusable if its contract interaction cannot pass your signing policy.

Records. Decide in advance what accounting needs: the input amount, quoted output, source transaction hash, destination transaction hash and final token balance. The receiving wallet may also need native gas on the destination chain to spend an ERC-20 token later. For recurring payouts, check each transfer against a fresh route; a route available last week need not quote the same output or timing today.

How Do Teams Execute and Reconcile a Transfer?

Choose from current quotes using the five checks, then verify the receiving address and minimum output before the treasury signer commits funds. The transfer begins on the source chain and is complete for business purposes when the intended asset reaches the intended address on the destination chain. Keep the quote alongside the two chain records so finance can match the payment instruction to what arrived.

If you bridge tokens with Bungee regularly, set an internal threshold for acceptable net receipt and arrival time rather than selecting the first route returned. A small trial transfer can confirm that a new recipient accepts the exact destination token. For later transfers, recheck the quote and contract address instead of treating that trial as permanent route approval.

Can I Track a Bungee Bridge Transaction?

Yes: track source confirmation and destination settlement as separate events. Save the source chain ID and transaction hash when funds leave, then check the route’s status and the destination chain for the receiving transaction. A confirmed source transaction proves the first leg happened; it does not by itself prove the payout arrived.

For automated workflows, transaction or request hashes can be used to query status through Bungee’s API. If delivery is still pending, compare that status with both chain records before sending again; a second transfer could create a duplicate payout. Close the ledger entry only after the destination amount, token contract and recipient match the instruction.

Confirm the destination chain, token contract and address.
Compare net receipt, timing and signer requirements.
Save the quote and source hash; verify the destination receipt.

How to Pay Contractors in USDT From Monero

Kendra Koepp — Tue, 29 Sep 2026 13:29:29 +0000

If you hold Monero and need to pay a contractor in USDT, convert XMR into the network the contractor can receive, then send the stablecoin to their matching wallet or exchange deposit. For repeat payments, agree on the chain and invoice amount first; that prevents an avoidable second conversion or a payment sent on the wrong network.

Why convert XMR to USDT before paying?

USDT gives both sides a dollar-denominated payment amount, while XMR’s market price can move between invoicing and settlement. If an invoice is for $1,000, agree whether that means 1,000 USDT before fees, or 1,000 USDT received by the contractor. Those are different targets when conversion and withdrawal costs apply.

An XMR bridge is useful when your funds are in Monero but the recipient expects USDT. The service handles the cross-chain conversion: you provide XMR, and USDT is sent on a destination network. That avoids first moving through a separate asset or exchange route, though each extra conversion or withdrawal can add cost and time.

How does the conversion reach your contractor?

The process has two transfers and a conversion between them. Your XMR transaction is broadcast on Monero and included in a block; Monero blocks average about two minutes. The conversion service waits for the deposit according to its settlement rules, exchanges the value for USDT, and sends the result on the selected network. The contractor then receives USDT at their wallet or exchange.

That means “XMR sent” is not the same as “contractor paid.” The swap may need time to confirm and process, and the contractor’s wallet may need further network confirmations before showing the deposit as available. For a deadline, allow for both stages and for the recipient’s exchange crediting time; don’t schedule payment to the last minute.

Which network keeps the payment fast and economical?

Choose the network the recipient can actually receive, then compare its total cost with the required arrival time. USDT on Ethereum can incur variable gas costs, especially when the network is busy. Polygon can offer lower transaction costs, but it only helps if the recipient’s wallet or exchange supports USDT deposits on Polygon.

Before each payment, confirm these details with the contractor:

The exact asset: USDT, not another dollar stablecoin.
The receiving network, such as Ethereum or Polygon.
The deposit address for that asset on that network.
Any required memo or tag, plus the exchange’s minimum deposit.

A common and costly mistake is choosing a network because the address looks compatible. Ethereum and Polygon addresses can look alike, but the deposit still arrives on a particular chain; an exchange may not credit it if you use the wrong one. Match the recipient’s stated network exactly, and send a small test payment first when the address or route is new and the amount justifies the extra transaction.

How do you keep recurring payments predictable?

Agree on the invoice currency, who covers conversion costs, and the USDT network once, then verify the address and network for every payment. Compare the amount the contractor will receive after the swap and onward transfer, not only the headline conversion rate. Service pricing, liquidity, network fees, and market movement can all affect the net amount.

For example, if the contractor must receive 1,000 USDT, use the live quote to estimate the XMR input and check whether the resulting payout covers the invoice after any onward withdrawal fee. If the quote can expire, prepare the payment only when you are ready to send; late XMR confirmation or a changed rate may affect the result, depending on the service’s terms. Keep the transaction IDs and agreed invoice amount with your payment record.

For the choice of conversion method behind this workflow, read how XMR bridge methods compare; then settle on a route that matches your recipient’s network and your payment cadence. The practical rule is simple: agree on the chain, calculate the net USDT, and leave time for both settlement stages.

What Do Dust Limits Mean for Tiny Balances?

Kendra Koepp — Wed, 09 Sep 2026 21:43:57 +0000

Dust limits mean that a bridge may reject, round down, or make uneconomic a transfer whose amount is too small for that route. The first attempt usually fails because the wallet shows one balance while the bridge checks three different limits: token precision, transfer cost, and destination setup.

The numbers that matter

1 USDC = 1,000,000 units. USDC uses six decimals. An amount such as 0.000001 USDC is representable; anything smaller is not.
8 decimals. The original Wormhole token bridge represents bridged amounts at no more than eight decimals. An 18-decimal token can therefore lose sub-unit precision during conversion. That remainder is dust and should be refunded rather than minted on the destination.
About 4.2 USDC or 0.3 USDC. Current automatic CCTP relay fees are roughly 4.2 USDC on Ethereum mainnet and 0.3 USDC on Base, Optimism, Arbitrum, and Avalanche. These are route fees, not universal minimums.
Zero protocol minimum in one case. Circle CCTP can transfer any representable USDC amount when the sender pays gas on both chains. An automatic relayer still needs enough value to cover its destination-side work.

Dust is three different problems

Precision dust is created by decimal conversion. A token balance may contain units that the bridge cannot encode on its messaging layer or destination token contract. The bridge sends the largest representable amount and handles the remainder according to its rules. That remainder is not a fee, and it is not necessarily recoverable from the destination wallet.

Economic dust is different. A transfer can be technically valid but irrational. A 0.50 USDC transfer that requires a 0.30 USDC relay fee leaves little value before source-chain gas is counted. On an expensive chain, the gas to approve and send the token can exceed the balance itself. A user interface may label this a minimum amount even when the smart contract could process less.

Destination dust comes from account creation. A recipient may need a token account, rent deposit, or native gas before the asset can be credited. This matters on Solana, where a CCTP redemption may need an associated token account. If a relayer creates that account, the required rent and transaction costs become part of the practical minimum.

This third category is the one most bridge explanations leave out. The amount you send is not the whole transaction. The destination has to be able to receive it, and a tiny transfer may not fund the machinery needed to make that happen.

Why the same amount works on one route

A dust limit belongs to a route, not to the word “bridge.” The route combines a source chain, destination chain, asset representation, messaging system, relayer, and settlement mode. Change one of those and the minimum can change.

Stargate Finance exposes this through its quote data. Its OFT interface returns a minimum and maximum amount in local token decimals, while the transfer quote reports the minimum amount expected after fees. Stargate V2 also separates Taxi transfers from Bus transfers. Bus batches activity to reduce costs but can delay delivery; Taxi is immediate and may cost more. A tiny balance that fits one mode may not fit the other.

Wormhole Protocol has a separate precision issue because its token-bridge format historically shifts amounts to a common decimal range. That can leave a remainder even when fees are negligible. If native USDC is available through Circle CCTP, the asset is burned on the source chain and minted on the destination instead of being represented as a wrapped token. That removes the wrapped-asset problem, but it does not remove gas or relay costs.

How to check before sending

Convert the balance into the token’s smallest units. Do not rely only on the rounded dollar value shown in the wallet.
Quote the exact amount on the exact source and destination route. Check the amount received after fees, the route minimum, and the slippage minimum.
Check the destination separately. Confirm that the recipient token account exists and that the destination has enough native gas or rent for redemption.
Keep enough source-chain gas for approval and submission. “Send maximum” can fail if the wallet needs native currency to authorize the transfer.
If the balance is below the route minimum, do not split it into several transfers. Fixed relay and transaction costs multiply. Aggregate it, use a cheaper route, or leave it until more funds arrive.

The practical rule is simple: treat the quoted received amount, not the wallet balance, as the spendable figure. A dust limit is a warning that some part of the route cannot be represented, paid for, or completed at that size.

For the broader job of selecting a bridge route across assets and chains, start with Universal Bridge.

How Governance Tokens Influence Protocol Decisions

Kendra Koepp — Wed, 09 Sep 2026 17:53:54 +0000

Governance tokens influence protocol decisions by giving holders voting power over proposals that can change a protocol’s parameters, treasury, or code.

The vote is often already live when most holders notice it: a proposal has a deadline, a quorum bar, and wallets deciding whether software should change. For the surrounding ZKsync context, start at syncswap.

What the token actually does

The token is usually an ERC-20 Token Standard asset. That standard provides balances, transfers, and allowances; a governance contract adds checkpoints, delegation, proposal thresholds, and vote counting. A holder’s balance at a snapshot becomes voting power—often one token, one vote, subject to quorum and approval rules.

The usual path is:

Read the proposal and inspect its executable payload.
Delegate to an informed voter if your balance or time is small.
Vote directly if you hold enough to matter or want control.
Check the timelock before treating approval as execution.

What changed in 2026

Governance is moving beyond raw token counts. Delegates interpret proposals, councils handle emergencies, and timelocks give users time to react. ZKsync’s 2026 votes on upgrades and development allocations show the distinction clearly: token holders can approve an action while a separate executor controls when it reaches production.

Matter Labs’ visible voting power also shows why delegation matters: a large, recognised stakeholder can shape outcomes without every holder surrendering ownership. Orbiter Finance is a useful adjacent reminder that builders, bridges, and protocol administrators are not automatically the same governance body.

For a small holder, delegation is usually the best budget-to-influence trade. For a large holder, direct voting buys control at the cost of attention and gas. My rule is simple: never buy a governance token merely to vote. Verify the snapshot, quorum, delegate incentives, payload, and timelock first.

Multisig Custody: The Rule That Moves Bridged Assets

Kendra Koepp — Tue, 08 Sep 2026 12:33:01 +0000

The rule that moves a bridged asset is the bridge contract's quorum check, and it is public. You can look at the lock contract on the origin chain, the mint contract on the destination chain, and the list of signer addresses that must agree before either one changes state. The custody is the contract; the multisig is the condition it requires.

How a multisig move runs

A move runs through three steps: lock, quorum signature, and mint. The bridge contract on the origin chain locks your tokens — say, USDC on the source network. A set of signers, commonly 5-of-8 or 3-of-5, signs a message that names the recipient, the amount, the destination chain, and a nonce. A relayer submits that bundle to the destination contract, which verifies the quorum and mints the bridged representation. The return trip reverses it: burn on the destination, and the source contract verifies the burn proof against its own quorum rule, then releases the original token. What you end up with is a representation of your asset on another network; the original stays locked until the return trip.

The common explanation gets the trust direction wrong

The common explanation says a multisig bridge is safe when enough signer keys are spread around and unsafe when they are not. That is true, but secondary. What decides it is what the contract enforces around the quorum. If the mint contract accepts a signature without checking that the message came from the bridge's own verifier, no number of signers saves you. If the lock contract releases funds without verifying the burn proof, the quorum is a formality. The signers authorize; the contract executes.

This is also the point where discussions about bridges split. One side says more signers means more security; the other says key distribution matters more. You can settle it with what is checkable: the quorum threshold, the signer list, and the bytecode guarding the mint and unlock functions. A 3-of-5 with signers in separate jurisdictions running isolated hardware will move funds more soundly than a 9-of-12 whose keys sit behind one API. Quorum size decides coordination cost; the contract's guard logic decides custody strength. You can read both for a given bridge: Paraswap.

Where multisig custody does not apply

Not every bridge uses a quorum. Light-client bridges verify execution headers on-chain and authorize movement by proof, with no signer set at all. Atomic swaps use hashed timelock contracts, where the asset moves only if a preimage is revealed before a deadline. Intent-based systems hand the movement to solvers who compete to fulfill it. In those cases there is no multisig to read, and the trust model is a different question: a proof to verify instead of a quorum to watch.

The custody mechanism is what you are actually choosing when you route a swap across chains. On the destination, the bridged asset becomes usable in the venues you already know — an order on 0x Protocol, a pool on Uniswap Protocol, a position on Optimism Network — but the movement that put it there was either a multisig-gated contract action or one of the alternatives above. That difference is the thing to check before you move funds.