4 posts tagged with "wallet"

Overview​

This guide explains how to use the sub-wallet features of TronLink / MetaMask to manage multiple merchant accounts with 4 mnemonic groups (3 multisig admin groups + 1 treasurer group), each corresponding to 4 master wallets, and complete the following tasks:

• Create sub-wallets for each merchant's multisig admins and treasurer address
• Register a new merchant and configure the multisig admin and treasurer wallets
• Obtain the API Key for integration by the development team

In the blockchain field, ERC-4337 (Account Abstraction) has been very popular in recent years. It proposes a new account system that allows wallets to move beyond traditional Externally Owned Accounts (EOA) and be completely defined by smart contracts.

It sounds ideal:

• User operations are submitted through UserOperation (UserOps) instead of regular transactions.
• Bundlers collect users' UserOps, bundle them into a single transaction, and submit to the blockchain.
• Account logic (signature methods, multi-factor authentication, limits, recovery mechanisms) is completely controlled by contracts, providing more flexible wallet experiences.

However, after in-depth research, we found: The real-world effectiveness of ERC-4337 in payment business is not as perfect as imagined.

Blockchain wallets are the "keychains" of the blockchain world, determining how you access and manage assets while impacting security and functionality. Wallet differences can be categorized by usage patterns or underlying protocol models. This article provides a comprehensive understanding of both classification methods, including security recommendations and a comparison table of common wallets.

When you make on-chain payments, wallets like TP (TokenPocket) and imToken may display a warning: "The address you entered is a contract address. Please verify before transferring." This warning often causes concern. Below is a detailed explanation.