Investigate Unexpected Native Value in a Wallet Request
A wallet’s native-value field deserves its own check. It is not interchangeable with an ERC-20 amount, an estimated token output or a network fee. If the value surprises you, pause the request and identify its purpose.
Read the fields with their units
Ethereum transaction documentation defines value as the native ETH amount transferred, expressed in wei. Contract input data is a different field. A token quantity may be encoded in that input rather than in value. Gas-related fields describe another part of the request. Do not add these numbers together as though they use the same units or infer the destination’s purpose from a token logo.
Compare the request with the task
Write down the intended chain, recipient or contract, asset and amount before interpreting the wallet prompt. Ask what would justify any native value for that specific operation. Different protocols can have different requirements, so a generic rule such as every contract call must carry zero is insufficient. Use the protocol’s official documentation for the exact operation; if the explanation is missing, leave the request unsigned.
Use a hypothetical mismatch to guide review
Suppose you intended to inspect a quote, but a wallet prompt asks to transfer native currency. That is a change of task requiring investigation, not a routine quote display. RunixCoin’s public quote form does not execute swaps, so its estimate cannot justify an unexpected execution prompt. Canceling a prompt you cannot explain is preferable to relying on a familiar website label to identify the underlying action.
Verify any existing submission separately
If you already confirmed a request, record its hash, network and actual destination, then inspect the receipt and relevant asset movements. The wallet prompt and the chain result are different observations. Keep the transaction value separate from the gas charge when interpreting a balance change. Do not send a compensating transaction to test your interpretation. This page provides a review method, supplies no transaction parameters to sign and cannot establish that an unknown destination or request is legitimate.
References and verification
Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.