Skip to content

Latest commit

 

History

History
164 lines (108 loc) · 3.29 KB

File metadata and controls

164 lines (108 loc) · 3.29 KB

Base Wallet Security

Base wallet security covers the protection of wallet credentials, transaction signing, ERC-20 token approvals and smart contract interactions on Base.

This guide provides practical security information for Base wallet users and developers.

Protect Your Private Key

A private key controls access to a blockchain account.

Never share it with:

  • Websites
  • Developers
  • Support agents
  • Telegram users
  • Discord users
  • Unknown applications
  • Public repositories

Never publish private keys in GitHub.


Protect Your Seed Phrase

A seed phrase may control one or more blockchain accounts.

Never store a seed phrase in:

  • GitHub
  • Public documents
  • Screenshots
  • Chat messages
  • Public websites
  • Source code
  • Application logs

Anyone who obtains the seed phrase may be able to control the associated wallets.


Base Wallet Security Checklist

Before interacting with a Base application:

  • Verify the website domain
  • Verify the contract address
  • Verify the network
  • Review transaction details
  • Review token approvals
  • Avoid unknown contracts
  • Use separate wallets for higher-risk applications
  • Keep significant assets appropriately protected

ERC-20 Token Approvals

ERC-20 tokens commonly use allowance mechanisms.

An approval can allow a spender to transfer tokens on behalf of a wallet.

Users should understand:

  • Token contract
  • Spender address
  • Approved amount
  • Approval transaction
  • Application associated with the spender

ERC-20 Allowance

An allowance represents the amount of a token that a spender can transfer on behalf of an owner.

Simplified model:

Wallet
   ↓
ERC-20 Contract
   ↓
Approved Spender
   ↓
Allowance

Allowance information can be inspected using public blockchain data.


How to Check Base Token Approvals

A public blockchain inspection workflow can examine:

  • Wallet address
  • Token contract
  • Spender address
  • Allowance
  • Approval transaction
  • Approval events

Always verify the contract and spender before changing an allowance.


How to Revoke ERC-20 Approval

When an unwanted token approval is identified, users may interact with the relevant token contract to reduce or remove the allowance where supported.

Typical workflow:

  1. Identify the token contract.
  2. Identify the spender.
  3. Check the current allowance.
  4. Verify the contract.
  5. Submit the desired allowance update.
  6. Confirm the transaction.

A network fee is required to modify on-chain state.


Suspicious Base Transactions

When investigating an unfamiliar transaction, inspect:

  • Transaction hash
  • From address
  • To address
  • Token contract
  • Function call
  • Token amount
  • Approval events
  • Contract interaction

Do not interact with an unknown contract simply to investigate it.


Base Wallet Security Tools

Bitools provides blockchain inspection and wallet management tools.

https://bitools.pro/base/


Security Warning

A public balance checker or transaction inspection tool should not require your private key or seed phrase.

If a website asks for sensitive wallet credentials to inspect public blockchain information, do not provide them.


Related Guides