Consensus duties
Consensus duties is a distinct part of understanding PoS & Validators. First identify the network, account and action involved, then compare what the wallet displays with what you actually intend to do. Familiarity with a workflow is not a reason to skip verification for transfers, contract calls or approvals.
Use a repeatable review sequence for consensus duties: network and address first, then asset or contract, then request details, value and fees, and finally the on-chain result after submission. Cancel requests with unclear fields, unfamiliar contracts, unexpectedly broad allowances or pressure to act quickly.
After connecting to a DApp, inspect every signature, transaction and token approval independently; disconnecting does not necessarily revoke an on-chain allowance. For important actions, keep a public address or transaction hash and verify the on-chain result with a block explorer. Stop when interface data conflicts with chain data.
Practical checks
- Confirm the active network and account for consensus duties
- Verify the destination, contract or requested action
- Never share a seed phrase, private key or verification code
- Use a transaction hash to verify the result on-chain
Online performance
Online performance is a distinct part of understanding PoS & Validators. First identify the network, account and action involved, then compare what the wallet displays with what you actually intend to do. Familiarity with a workflow is not a reason to skip verification for transfers, contract calls or approvals.
Use a repeatable review sequence for online performance: network and address first, then asset or contract, then request details, value and fees, and finally the on-chain result after submission. Cancel requests with unclear fields, unfamiliar contracts, unexpectedly broad allowances or pressure to act quickly.
Security is a continuing routine: offline backups, trusted devices, fewer unnecessary approvals, caution on public networks and skepticism toward unexpected requests. Similar address formats do not make networks interoperable. Before transferring, re-check the network, amount, gas and destination.
Practical checks
- Confirm the active network and account for online performance
- Verify the destination, contract or requested action
- Never share a seed phrase, private key or verification code
- Use a transaction hash to verify the result on-chain
Slashing
Slashing is a distinct part of understanding PoS & Validators. First identify the network, account and action involved, then compare what the wallet displays with what you actually intend to do. Familiarity with a workflow is not a reason to skip verification for transfers, contract calls or approvals.
Use a repeatable review sequence for slashing: network and address first, then asset or contract, then request details, value and fees, and finally the on-chain result after submission. Cancel requests with unclear fields, unfamiliar contracts, unexpectedly broad allowances or pressure to act quickly.
Review the active network, account and target together rather than relying on a page label or icon. After connecting to a DApp, inspect every signature, transaction and token approval independently; disconnecting does not necessarily revoke an on-chain allowance.
Practical checks
- Confirm the active network and account for slashing
- Verify the destination, contract or requested action
- Never share a seed phrase, private key or verification code
- Use a transaction hash to verify the result on-chain
Exit and liquidity
Exit and liquidity is a distinct part of understanding PoS & Validators. First identify the network, account and action involved, then compare what the wallet displays with what you actually intend to do. Familiarity with a workflow is not a reason to skip verification for transfers, contract calls or approvals.
Use a repeatable review sequence for exit and liquidity: network and address first, then asset or contract, then request details, value and fees, and finally the on-chain result after submission. Cancel requests with unclear fields, unfamiliar contracts, unexpectedly broad allowances or pressure to act quickly.
Seed phrases and private keys are account-control secrets and should never be sent through web forms, chats, email or remote-support sessions. Security is a continuing routine: offline backups, trusted devices, fewer unnecessary approvals, caution on public networks and skepticism toward unexpected requests.
Practical checks
- Confirm the active network and account for exit and liquidity
- Verify the destination, contract or requested action
- Never share a seed phrase, private key or verification code
- Use a transaction hash to verify the result on-chain