Frequently Asked Questions

No. Seed phrases and private keys should remain under your control and should never be sent to anyone.

A seed phrase can restore a group of accounts, while a private key directly controls a specific account. Both are sensitive.

Verify the receiving address, network and asset type, and confirm the sender is using the same network.

Review the destination, network, asset, amount and gas, and make sure copied data was not altered.

Gas depends on network demand and transaction complexity, so fees vary across time and networks.

It can be used on the appropriate block explorer to review status, confirmations and failure information.

No. Connection, message signing, transaction signing and token approvals are separate permissions.

No. A message signature may prove identity or permission, while a transaction signature authorizes an on-chain action.

Check the approval contract, spender and allowance size, and consider revoking permissions you no longer need.

They often share address and contract models, but network IDs, gas assets, contracts and state remain separate.

Layer 2 can use mainnet for security or settlement, while cross-layer transfers may involve bridges and waiting periods.

Check the domain, source and request details, and do not submit secrets because of an ad, message or supposed support link.

Public networks increase exposure to fake hotspots and device risk, so sensitive actions deserve extra caution.

No. Rewards, network state, exit queues, validator performance and asset prices can all change.

Validators can face penalties for downtime or rule violations, along with operational and technical risks.

Not necessarily. Exit and withdrawal can depend on queues and protocol rules, so waiting periods may apply.

No. Contracts can have technical flaws, permission risks or third-party dependencies.

There is no fixed interval, but review permissions when you stop using a DApp or notice an unexpected approval.