FAQ

Digital assets are recorded on the relevant blockchain. A wallet manages keys used to view accounts and sign requests, then presents network data in a usable interface.

A private key generally controls a specific account, while a seed phrase can recover a set of deterministically derived accounts. Both are highly sensitive.

No. A seed phrase, private key or verification code should never be sent as routine support information or entered into an unfamiliar web page.

Assets with the same name can exist on different networks, and address formats can look similar. A network mismatch can prevent the recipient from seeing funds where expected.

Gas is the fee mechanism used to pay for network processing or smart-contract execution. Fees vary by network conditions and transaction complexity.

A transaction hash identifies a specific on-chain operation and can be used to check status, block inclusion, addresses and other public details.

Check the transaction hash on the correct network and distinguish a delayed interface from actual on-chain status. Congestion and fee settings can affect confirmation time.

Not necessarily. A failed transaction may already have consumed network resources, so some gas can still be charged depending on the network and failure point.

No. Connection normally exposes limited account information. Signatures, transactions and token approvals are separate requests that need their own review.

A message signature can be used for login, proof of account control or protocol authorization. It may not transfer assets directly, but it can still have important permission implications.

A token approval records permission for a spender contract to use tokens within a defined amount. Check the spender and limit before signing.

Usually not. Disconnecting ends a site session, while an on-chain approval must be changed or revoked through a new transaction on the relevant network.

Many EVM-compatible networks use similar address formats, but each network maintains independent state, gas rules and contract deployments.

Layer 2 systems process activity outside the base layer and connect back through different settlement or security mechanisms. Moving assets across layers normally uses a bridge.

Do not rely on the image or name alone. Check the network, contract and source, and avoid unfamiliar links or signature requests tied to unknown rewards.

No. Rewards can change with protocol rules, network conditions and validator performance. They are not a fixed annual return or guaranteed yield.

PoS protocols use penalties to enforce validator duties. Downtime, missed duties or serious rule violations can reduce rewards or trigger stronger penalties.

Not always. Exit and withdrawal timing can depend on protocol queues, network conditions and any third-party service process.