Frequently Asked Questions

No. Do not send a seed phrase, private key or verification code to anyone, and do not enter them into an untrusted website.

Review the recipient address, target network, asset type, amount and expected network fee.

Gas is the fee mechanism used when a blockchain executes transactions or smart-contract operations. Cost depends on the network and current conditions.

A transaction hash identifies an on-chain transaction and can be used to check broadcast, inclusion and confirmation status in the relevant explorer.

No. A connection is separate from later signatures, transactions and token approvals. Review each request independently.

A token approval gives a contract permission to use a token within a defined allowance. Check both the target and scope.

Layer 2 systems relate to mainnet but use different execution or settlement arrangements. Cross-layer transfers can involve bridges and waiting periods.

No. Rewards can change, exits may require waiting, validators can face penalties, and smart contracts and asset prices carry risk.

Both relate to wallet control. A seed phrase is commonly used to recover a set of wallet keys, while a private key directly controls a specific account. Neither should be shared.

A token name or symbol can be reused while contract addresses, networks and transfer paths differ. Review both the network and contract information.

Use the transaction hash and the relevant block explorer to see whether it was broadcast, is pending or failed before deciding what to do next.

Different signatures can have different consequences. Do not judge safety from the label alone; review the request origin, content and DApp purpose.

It usually means the allowance is extremely high or not limited to a typical transaction amount. It can be convenient but expands the contract’s permission scope.

No. EVM-compatible networks can share address formats while network IDs, fee assets, token contracts and transaction histories remain separate.

PoS validators are expected to participate correctly in consensus. Downtime, incorrect behavior or protocol-defined violations can reduce rewards or trigger penalties.

Use caution. Public networks can increase exposure to fake hotspots, interception attempts or device risks. Important actions are better performed on trusted devices and networks.