diff --git a/docs/tron.md b/docs/tron.md
index 368371e..80accff 100644
--- a/docs/tron.md
+++ b/docs/tron.md
@@ -1 +1,70 @@
-# [Tron](../README.md)
\ No newline at end of file
+# [Tron](../README.md)
+
+Tron's wallets or tools do not support standalone signature operations. Therefore, the officially provided SDK and `ckb-auth` are used here for comparative testing.
+[Official website](https://tronweb.network/)
+
+Tron's signature mechanism relies on secp256k1, which is also used by [Ethereum](./ethereum.md).
+
+
+## TronWeb
+`TronWeb` is an official SDK provided by Tron, Source code on [GitHub](https://github.com/tronprotocol/tronweb). Inside the [`tools/tron`](../tools/tron/) directory, there is a simple signature demo. This demo generates a set of keys, sign a message with the private key from this set, and verifies the signature.
+
+The message is a 32-byte binary data, corresponding to the ckb signature message.
+
+The demo require `nodejs` and `tronweb` module.
+- **Node.js**: The [Official website](https://nodejs.org/en). Download the appropriate binary package, extract it, and add the directory to your `PATH`.
+- To install 'tronweb' navigate to the directory [`tools/tron`](../tools/tron/) and run the command: `npm install tronweb`. (Note that for this command, This command may require proxy configuration. It will place the dependencies in the `node_modules` directory in the current location.)
+
+
+Run demo, after installing the dependencies.
+```bash
+node main.js
+```
+
+Output
+```text
+key: {
+  privateKey: '13B9751EDFC5F25ABCB6AE0A8DF387C0B473CF52D8A71125358EBC735F157ABA',
+  publicKey: '046B0EE21A47F54AD838D6F7C97A01067CC4F0BFA94C96F96A90516A24EC1E686F73EEEC973CAC5977563072035D6FEC23B22627F0EDF428F141F33300BDBE7BFF',
+  address: {
+    base58: 'TNzoqJ2ZCVZAzTsR5sKA6N5zardVodSi5x',
+    hex: '418EE7208C79F1FB62C124875C22CA082CCF6C89F6'
+  }
+}
+msg data: 01122334445566778899aabbccddeeff01122334445566778899aabbccddeeff
+msg hash: 0x98ebdce9b9c574540113cef6e187404fd804bc0aff17d1ea4b977ff7cbaefe2b
+sign: 0xdec4f45b74a3b19926a5d17b1a28d9c18f0e2982d764b0477269815827954ca43b27e004802d11d07311fb856ef53a7554c8301dae087d3ebbf14de4fea1eb9f1b
+verify ret pubkey address: TNzoqJ2ZCVZAzTsR5sKA6N5zardVodSi5x
+
+
+Success
+```
+
+Here's an explanation of the output content:
+- `key-privateKey`: This is the plaintext private key, stored as a hexadecimal string.
+- `key-publicKey`: The plaintext public key, also in hexadecimal string format.
+- `key-address-base58`: The address encoded in base58. Tron typically uses this format.
+- `key-address-hex`: The hexadecimal form of the address. It's not commonly used.
+- `msg data`: The data to be signed is a fixed length of 32 bytes, which is necessary for verification in ckb-auth-cli.
+- `msg hash`: The actual data used for signing, derived from multiple hashes of the msg data. This result is displayed for reference or debugging purposes.
+- `sign`: The result of the signature, in hexadecimal string format. In this case, it's 65 bytes long.
+- `verify ret pubkey address`: The result of the signature, in hexadecimal string format. In this case, it's 65 bytes long.
+
+## Address
+In Tron, the address is encoded by default in base58 format, and after decoding, it consists of 42 bytes. 
+
+The first byte is a fixed value of 0x41, and the subsequent data structure is the same as in `Ethereum`. [Refer to](https://developers.tron.network/docs/account).
+
+In the `ckb-auth-cli tron verify` command, the tool also checks the integrity of the Tron address to ensure it matches this format.
+
+## Sign
+The Tron signature process is indeed very similar to Ethereum, with a minor difference in how the message is hashed. Before hashing the message in Tron, a fixed prefix, `TRON Signed Message`, is added to it. This prefix is used as part of the hashing process for Tron signatures.
+
+### Verify
+
+The Tron verification process is similar to Ethereum, and the ckb-auth-cli tron verify command is used for verification purposes. This command is designed to verify Tron signatures, similar to how Ethereum signatures are verified.
+
+```
+./ckb-auth-cli tron verify -a TNzoqJ2ZCVZAzTsR5sKA6N5zardVodSi5x -s 0xdec4f45b74a3b19926a5d17b1a28d9c18f0e2982d764b0477269815827954ca43b27e004802d11d07311fb856ef53a7554c8301dae087d3ebbf14de4fea1eb9f1b -m 00112233445566778899aabbccddeeff00112233445566778899aabbccddeeff
+```
+The output "Success" indicates a successful verification.
diff --git a/tools/tron/main.js b/tools/tron/main.js
index 851f2df..a88afce 100644
--- a/tools/tron/main.js
+++ b/tools/tron/main.js
@@ -9,6 +9,7 @@ console.log("key: %o", account_key);
 let message_data = [0x00, 0x11, 0x22, 0x33, 0x444, 0x55, 0x66, 0x77, 0x88, 0x99, 0xaa, 0xbb, 0xcc, 0xdd, 0xee, 0xff, 0x00, 0x11, 0x22, 0x33, 0x444, 0x55, 0x66, 0x77, 0x88, 0x99, 0xaa, 0xbb, 0xcc, 0xdd, 0xee, 0xff,]
 
 let msg_hash = TronWeb.utils.message.hashMessage(message_data);
+console.log("msg data: %s", message_data.map(item => item.toString(16)).join(''));
 console.log("msg hash: %s", msg_hash);
 
 let sign_data = TronWeb.utils.message.signMessage(message_data, account_key.privateKey);