Update ethereum docs, about automation script

docs/ethereum.md

@@ -25,7 +25,6 @@ cd go-ethereum
 make all
 ```
 
-
 As `ethkey` is required, we compile all components for convenience. The compiled results can be found in the `build/bin` directory. It's recommended to add this directory to your 'PATH' environment variable for ease of use.
 
 ## Address
@@ -44,31 +43,59 @@ Here, the account's address and private key file are displayed. If you didn't ta
 
 In Ethereum, the `Address` is a 20-byte fixed-length array. When used in programs (geth and ckb-auth-cli), it will handle the leading `0x`.
 
+If you require automation testing, you can utilize the `passwordfile` and `keystore` parameters to manage password and key storage.
+
+```shell
+eth_password_file=`pwd`/password.txt
+echo $RANDOM > $eth_password_file
+eth_account_dir=`pwd`/account
+rm -rf $eth_account_dir
+mkdir -p $eth_account_dir
+geth account new --password $eth_password_file --keystore $eth_account_dir > /dev/null 2>&1
+
+eth_account_info=`geth account list --keystore $eth_account_dir 2>/dev/null`
+eth_address=`echo $eth_account_info | grep -oE -m 1 '\{[a-f0-9]+\}' | sed 's/{\(.*\)}/\1/'`
+eth_privkey_file=`echo $eth_account_info | grep -oE 'keystore://[^ ]+' | awk -F 'keystore:' '{print $2}'`
+
+echo Address: $eth_address
+echo PrivateKeyFile: $eth_privkey_file
+```
+
+After executing the above code. The value `eth_address` is ethereum address, `eth_privkey_file` is private key file path. In subsequent operations, these two variables can be used directly.
+
 ## Signature
 
 Ethereum's message is calculated using sha3: `Ethereum Signed Message:\n` + 'message' hash. While ckb-auth's message is a fixed length of 32 bytes, so here, `ethkey` supports the input of messages in both textual form and through a file (by using the `--msgfile` parameter). In this context, Ethereum's message is directly utilized as a data parameter hash, necessitating the use of the `--msgfile` to input a file.
 
 You can use the command provided by `ckb-auth-cli ethereum generate` to convert the message to file:
 ```shell
 message=0011223344556677889900112233445500112233445566778899001122334455
-message_file=
+message_file=`pwd`/message_file.bin
 ckb-auth-cli ethereum generate -m $message --msgfile $message_file
 ```
 (You need to set the path of `message_file` here)
 
 After generating the message file, you can use `ethkey` to sign:
 ```shell
-my_key_file=
-ethkey signmessage --msgfile $message_file $my_key_file
+ethkey signmessage --msgfile $message_file --passwordfile $eth_password_file $eth_privkey_file
 ```
 output:
 ```
 Signature: 5a62aa66a32a41fb44a58e7284ca964952da485dc0fcec24dadb7402d65274d8733f9a2c34274c573d09743d04f25fdfb00ffee8d821a1422c7d3f4e97ce97e100
 ```
 
+If it is an automated test, you can also get the signature through a script.
+```shell
+eth_sign_info=`ethkey signmessage --msgfile $message_file --passwordfile $eth_password_file $eth_privkey_file`
+eth_signature=`echo $eth_sign_info | awk -F 'Signature: ' '{print $2}'`
+echo Signature: $eth_signature
+```
+
+Now, the value in `eth_signature` is signature.
+
 After signing, you can verify it using geth to prevent any basic errors:
 ```shell
-ethkey verifymessage --msgfile $message_file 0x027a5b3c90216149a42ceaa0431ac7179d0e663b 5a62aa66a32a41fb44a58e7284ca964952da485dc0fcec24dadb7402d65274d8733f9a2c34274c573d09743d04f25fdfb00ffee8d821a1422c7d3f4e97ce97e100
+ethkey verifymessage --msgfile $message_file $eth_address $eth_signature
 ```
 
 * Here need to pay attention to the order of command parameters.
@@ -78,6 +105,5 @@ ethkey verifymessage --msgfile $message_file 0x027a5b3c90216149a42ceaa0431ac7179
 This can now be verified in ckb-auth:
 
 ```shell
-ckb-auth-cli ethereum verify -a 027a5b3c90216149a42ceaa0431ac7179d0e663b -s 5a62aa66a32a41fb44a58e7284ca964952da485dc0fcec24dadb7402d65274d8733f9a2c34274c573d09743d04f25fdfb00ffee8d821a1422c7d3f4e97ce97e100 -m 0011223344556677889900112233445500112233445566778899001122334455
+ckb-auth-cli ethereum verify -a $eth_address -s $eth_signature -m $message
 ```
-