关于eth_sendTransaction的data选项及发送ERC20代币的参数咨询

Hey there! Let's break this down clearly since you're just getting started with sending ERC20 tokens using JSON-RPC's eth_sendTransaction method.

The value Parameter #

For ERC20 token transfers, you should always set value to "0x0" (which equals 0 wei). Here's why:

• The value field is exclusively for sending native blockchain currency (like Ethereum's ETH). ERC20 tokens are smart contract-based assets, so their transfer logic lives entirely within the token's contract—you don't send them via the native value field.
• Setting value to anything else would send native ETH to the ERC20 contract, which is almost never what you want (unless the contract explicitly expects it, which standard ERC20s don't).

The data Parameter (The Heart of ERC20 Transfers) #

The data field is where you encode the specific action you want the ERC20 contract to perform. For standard transfers, this means calling the contract's transfer method. Let's break down how it works:

Basic Structure of ERC20 Transfer data #

The data string is ABI-encoded and has two key parts:

1. Method Signature Hash: The first 4 bytes of the Keccak-256 hash of the method's signature. For the standard transfer(address to, uint256 amount) method, this is 0xa9059cbb.
2. Encoded Parameters: The to address and amount (in the token's smallest unit, e.g., wei for ETH, or 1e6 per USDT token) encoded as 32-byte hex strings, padded with leading zeros.

Example data for a Transfer #

Suppose you want to send 100 tokens (in their smallest unit) to 0x1234567890abcdef1234567890abcdef12345678:

• The encoded to address becomes 0x0000000000000000000000001234567890abcdef1234567890abcdef12345678
• The encoded amount (100) becomes 0x0000000000000000000000000000000000000000000000000000000000000064
• Combining these with the method signature gives:

  0xa9059cbb0000000000000000000000001234567890abcdef1234567890abcdef123456780000000000000000000000000000000000000000000000000000000000000064
  

Other Common ERC20 Methods for data #

Beyond transfer, you might need to use other ERC20 methods—each has its own signature hash:

• approve(address spender, uint256 amount): Lets you authorize another address to spend your tokens. Signature hash: 0x095ea7b3
• transferFrom(address from, address to, uint256 amount): Used by authorized addresses to transfer tokens from someone else's account. Signature hash: 0x23b872dd

Pro Tip: Don't Encode Manually! #

You don't have to build the data string by hand. Tools like Ethers.js or Web3.js have functions (e.g., encodeFunctionData in Ethers.js) that handle the encoding for you based on the contract ABI. This avoids typos and mistakes with padding.

Full Example eth_sendTransaction Request #

Here's what a complete request might look like for an ERC20 transfer:

{
  "jsonrpc": "2.0",
  "method": "eth_sendTransaction",
  "params": [
    {
      "from": "0xYourWalletAddress",
      "to": "0xERC20ContractAddress", // Important: This is the token's contract address, not the recipient's address!
      "value": "0x0",
      "data": "0xa9059cbb0000000000000000000000001234567890abcdef1234567890abcdef123456780000000000000000000000000000000000000000000000000000000000000064"
    }
  ],
  "id": 1
}

Critical Note: The to field must be the ERC20 token's contract address, not the recipient's wallet address. The recipient's address is encoded in the data field instead.

内容的提问来源于stack exchange，提问作者Haren Sarma