Wallet Security Guidelines

Web3 Wallet Private Keys Are Crucial

Once a private key falls into the wrong hands, your assets can be completely drained. However, executing batch operations often requires using the private key, as it is impossible to sign multiple wallets simultaneously without it.

To address such needs, there are two widely used types of tools in the market:

1. Telegram Bots (TG BOT): TG BOTs inherently require access to private keys to sign transactions, making them a common choice for batch operations.

2. Web-based Tools (e.g., DogTools): These tools can execute transactions on the backend after obtaining private keys. However, this method comes with significant risks.

   • Trust: The platform must be highly trustworthy.

   • Security: The platform must have robust measures to protect private keys (e.g., the dexx server hack is a typical risk example).

But Some web tools, like DogTools, support executing transactions entirely on the frontend without accessing the user’s private key. DogTools ensures that private keys are used only for local signing. It never stores or uploads private keys and offers secure private key management options.

---

How to Ensure Private Keys Are Only Used for Local Signing

Any frontend tool that wants to access a private key must make an HTTPS request to send the key to a backend server. To verify this, you can inspect the tool's network activity:

1. Open Chrome Browser.

2. Right-click and select Inspect.

3. Navigate to Network -> Fetch/XHR.

4. Check if any requests send your private key to the backend (excluding third-party RPC interfaces like Helius for on-chain data).

---

How to Operate Private Keys Safely and Conveniently

DogTools offers three methods for managing private keys:

1. Manual Input

This method requires you to manage your private keys yourself and paste them into an input field. DogTools will use your private key for local signing.

• Security Precautions ⚠️:

  • Prevent malicious clipboard plugins on your computer from stealing your private key.

  • Ensure your private key isn’t stored in plain text on your device. Secure your device to prevent theft.

2. Import Private Key File

DogTools supports importing private keys in Excel, CSV, JSON, or TXT formats. Compared to manual input, this method improves efficiency.

• Instructions:

  • [For existing wallets]: download the [template file] from the top left, paste your private keys into it, and import.

  • [For new wallets]: use the Multi Sender feature to create new wallets, perform batch transfers, and export them in one go. Then, import the exported file.
• Security Precautions ⚠️:

  • Prevent malicious clipboard plugins from stealing your private key.

  • Ensure your private key isn’t stored in plain text on your device. Secure your device to prevent theft.

3. Local Encrypted Storage (Recommended 👍)

DogTools offers a local encrypted storage feature that uses AES encryption. Your private key is encrypted with a password you set (known only to you) and stored locally.

• Storage Location: Chrome Browser -> Right-click -> Inspect -> Application.

  
• Advantages:

  • Compared to manual input or file upload, private keys are not stored in plain text on your device.

  • It allows for easy wallet balance viewing and streamlined batch operations.

• Important Note:

  • Remember your encryption password. If lost, DogTools cannot recover your data. You’ll need to delete local data and start over.

Instructions:

• [For existing wallets]: After enabling wallet management, click [Import Bulk Wallets] in the top left and import your private keys. You can then select them directly for batch operations.

• [For new wallets]: After creating new wallets, import them into local wallet management with one click.

  
• Security Precautions ⚠️:

  • Be cautious of malicious clipboard plugins when importing private keys into local management.

  • Ensure the security of your local device and encryption password.