FAQ

On-chain assets are recorded by the relevant blockchain network. A wallet primarily manages keys, signatures and an interface for interacting with that network.

A seed phrase can restore a set of keys, while a private key directly controls a specific account. Both are highly sensitive and should remain private and offline.

No. Legitimate support should never ask for a seed phrase, private key or verification code.

Some networks use similar address formats, but the networks remain separate. A matching address does not mean assets exist on the same chain.

Review the destination address, network, amount and gas, and make sure the request matches what you intended to do.

No. Gas reflects resources consumed by network execution, and the resulting fee can vary with network conditions and transaction complexity.

A transaction hash is an identifier used to look up an on-chain transaction in the relevant block explorer and review status, addresses, value and fees.

Check the transaction hash and network conditions before resubmitting. Repeating an action without understanding the original state can create additional transactions.

A connection alone is generally different from a transfer, but later signatures, approvals or transactions can affect assets. Review each request separately.

No. A message signature may prove account control or support authentication, while a transaction signature authorizes an on-chain state change.

A token approval lets a specified contract spend up to an allowed amount under the token rules. Review the target and allowance, and consider revoking permissions you no longer use.

EVM is a smart-contract execution model used by multiple networks. Similarity of the model does not merge their assets, gas or on-chain state.

Layer 2 systems relate to a base chain for settlement or security, but transaction paths and asset movements can differ and may involve bridges or waiting periods.

Verify domains and entry points, avoid unsolicited links and remote-control requests, never share keys, and inspect every signature and approval.

No. Rewards can change, exits can involve waiting, validators can face penalties, and contract, third-party service and market risks remain.

In a Proof-of-Stake network, a validator performs protocol-defined duties that help the network reach consensus. Responsibilities and risks depend on the protocol.