From 2798d5df308e025a8a3d56b4134ed3bd24244012 Mon Sep 17 00:00:00 2001 From: Grodex Date: Wed, 17 Dec 2025 17:04:25 +0800 Subject: [PATCH 1/6] Update getting_started_with_javatron.md Correct some wording errors and grammar mistake. For the part that requires client to change, please leave it for now --- .../getting_started_with_javatron.md | 20 +++++++++---------- docs/mechanism-algorithm/multi-signatures.md | 17 ++++++++++++---- 2 files changed, 23 insertions(+), 14 deletions(-) diff --git a/docs/getting_started/getting_started_with_javatron.md b/docs/getting_started/getting_started_with_javatron.md index f66946c4..3800d5d2 100644 --- a/docs/getting_started/getting_started_with_javatron.md +++ b/docs/getting_started/getting_started_with_javatron.md @@ -33,7 +33,7 @@ There are two main types of accounts on the TRON network: To begin interacting with the TRON network, you first need to create an Externally Owned Account (hereafter referred to as an "account"). There are several ways to create a TRON account, including using Software Development Kits (SDKs) like [Trident-java](https://tronprotocol.github.io/trident/) and [TronWeb](https://tronweb.network/), or various wallet applications (such as the browser extension wallet, [TronLink](https://www.tronlink.org/)). -This guide will use the command-line tool `wallet-cli` to demonstrate the most fundamental account operations. +This guide use the command-line tool `wallet-cli` to demonstrate fundamental account operations. > **About `wallet-cli`** > @@ -83,14 +83,14 @@ currentNetwork: NILE **1. Register Account** -At the prompt, enter the `registerwallet` command and follow the instructions to set a secure password. This command generates a new TRON network account and registers it with `wallet-cli`, which means its encrypted private key is stored in the local keystore for future use in signing transactions. +At the prompt, enter the `registerwallet` command and follow the instructions to set a secure password. This command generates a new TRON network account and registers it with `wallet-cli`, storing the encrypted private key locally for future transaction signing. ``` wallet> registerwallet Please input password. password: -user defined config file doesn't exists, use default config file in jar +user defined config file doesn't exist, use default config file in jar WalletApi getRpcVsersion: 2 Please input password again. password: @@ -149,7 +149,7 @@ After completing all the above preparations, you now have a properly configured ## Skill 2: Start and Run a Java-tron Node -This module will guide you through launching a java-tron instance, turning your computer into a TRON FullNode. Running your own node provides you with the most stable, reliable, and rate-unlimited network access. The network used in this module is the TRON [Nile Testnet](https://nileex.io/). +This module guide you through launching a java-tron instance, turning your computer into a TRON FullNode. Running your own node provides you with the most stable, reliable, and rate-unlimited network access. The network used in this module is the TRON [Nile Testnet](https://nileex.io/). > Tips: > @@ -259,7 +259,7 @@ The result is as follows: "address": "TUoHaVjx7n5xz8LwPRDckgFrDWhMhuSuJM", "balance": 93643857919, "create_time": 1619681898000, - "latest_opration_time": 1655358327000, + "latest_operation_time": 1655358327000, "is_witness": true, "asset_issued_name": "TestTRC10T", "latest_consume_free_time": 1652948766000, @@ -325,8 +325,8 @@ This command returns a transaction pending confirmation. Please follow the steps Please confirm and input your permission id, if input y or Y means default 0, other non-numeric characters will cancel transaction. y Please choose your key for sign. -The 1th keystore file name is .DS_Store -The 2th keystore file name is UTC--2022-07-04T06-35-35.304000000Z--TQXjm2J8K2DKTV49MdfT2anjUehbU3WDJz.json +The 1st keystore file name is .DS_Store +The 2nd keystore file name is UTC--2022-07-04T06-35-35.304000000Z--TQXjm2J8K2DKTV49MdfT2anjUehbU3WDJz.json The 3th keystore file name is UTC--2022-06-21T09-51-26.367000000Z--TUoHaVjx7n5xz8LwPRDckgFrDWhMhuSuJM.json Please choose between 1 and 3 3 @@ -405,9 +405,9 @@ After you send a transaction, the `wallet-cli` terminal returns a unique transac ### Method Two: Using `cURL` (Direct HTTP API Call) -While `wallet-cli` provides user-friendly interactive commands, more advanced developers or those working in automated scripting scenarios may find it more flexible and efficient to interact with a java-tron node directly via its HTTP API. This section demonstrates how to use `cURL` (a command-line tool for sending HTTP requests) to call the java-tron node's HTTP API to perform core functions like querying account balances and sending transactions. +While `wallet-cli` provides user-friendly interactive commands, advanced developers or those working on automated scripts scenarios may find it more flexible and efficient to interact with a java-tron node directly via its HTTP API. This section demonstrates how to use `cURL` (a command-line tool for sending HTTP requests) to call the java-tron node's HTTP API to perform core functions like querying account balances and sending transactions. -Unlike `wallet-cli`, which automatically handles signing and broadcasting, sending a transaction by directly calling the API requires you to manually complete a standard three-step process: **Create -> Sign -> Broadcast**. This section will show you how to execute this process. +Unlike `wallet-cli`, which automatically handles signing and broadcasting, using the API requires you to manually complete a three-step process: **Create -> Sign -> Broadcast**. This section will show you how to execute this process. #### Prerequisite: Query Account Balance @@ -436,7 +436,7 @@ In the returned JSON data, the `balance` field represents the TRX balance of the Now, let's use a TRX transfer as an example to fully demonstrate the "Create-Sign-Broadcast" three-step process for sending a transaction to java-tron. -Srtep 1 - Create a Transaction +Step 1 - Create a Transaction Use the FullNode's `wallet/createtransaction` HTTP endpoint to create an unsigned TRX transfer transaction. In the request body, specify the sender (`owner_address`), recipient (`to_address`), and amount (`amount`). diff --git a/docs/mechanism-algorithm/multi-signatures.md b/docs/mechanism-algorithm/multi-signatures.md index b059d001..ade2aadb 100644 --- a/docs/mechanism-algorithm/multi-signatures.md +++ b/docs/mechanism-algorithm/multi-signatures.md @@ -171,10 +171,19 @@ The above fees can be adjusted through proposals. ### 1. Permission Modification Operation Process -1. Use `getaccount` to query the current account permission structure. -2. Construct the new permission configuration. -3. Call `AccountPermissionUpdateContract`. -4. Sign and broadcast the transaction. +1. Check Current Account Permissions +Use the getaccount command to query and review the current permission structure of the SR account. +2. Prepare the New Witness Account. +3. Stop the Current SR Node. +4.Update Witness Permission via Smart Contract. +Using the SR's owner account, initiate the AccountPermissionUpdateContract transaction (cost: 100 TRX). +5. Modify SR Node Configuration, update the local config file of your SR node.Replace the existing private key with the private key of the new witness account. +6. Restart the SR Node. + +Warning! +You must stop the currently producing SR node before broadcasting the AccountPermissionUpdateContract transaction. + +An SR node cannot package a transaction that modifies its own witness permission into a block. If a node attempts to produce a block containing such a transaction, the block will fail signature verification. As a penalty, the node will be disconnected from the network by other peers for 1 hour. #### Example Request: From 59e5242aba2bef10fcc5f2e1f72b1bf5b7e4a68a Mon Sep 17 00:00:00 2001 From: Grodex Date: Wed, 17 Dec 2025 17:46:56 +0800 Subject: [PATCH 2/6] Update multi-signatures.md --- docs/mechanism-algorithm/multi-signatures.md | 15 ++++----------- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git a/docs/mechanism-algorithm/multi-signatures.md b/docs/mechanism-algorithm/multi-signatures.md index ade2aadb..a2ab119c 100644 --- a/docs/mechanism-algorithm/multi-signatures.md +++ b/docs/mechanism-algorithm/multi-signatures.md @@ -171,17 +171,10 @@ The above fees can be adjusted through proposals. ### 1. Permission Modification Operation Process -1. Check Current Account Permissions -Use the getaccount command to query and review the current permission structure of the SR account. -2. Prepare the New Witness Account. -3. Stop the Current SR Node. -4.Update Witness Permission via Smart Contract. -Using the SR's owner account, initiate the AccountPermissionUpdateContract transaction (cost: 100 TRX). -5. Modify SR Node Configuration, update the local config file of your SR node.Replace the existing private key with the private key of the new witness account. -6. Restart the SR Node. - -Warning! -You must stop the currently producing SR node before broadcasting the AccountPermissionUpdateContract transaction. +1. Use `getaccount` to query the current account permission structure. +2. Construct the new permission configuration. +3. Call `AccountPermissionUpdateContract`. +4. Sign and broadcast the transaction. An SR node cannot package a transaction that modifies its own witness permission into a block. If a node attempts to produce a block containing such a transaction, the block will fail signature verification. As a penalty, the node will be disconnected from the network by other peers for 1 hour. From 8095119a35ab2c968f0325d3e037412de9d0697a Mon Sep 17 00:00:00 2001 From: Grodex Date: Wed, 17 Dec 2025 17:49:15 +0800 Subject: [PATCH 3/6] Update multi-signatures.md --- docs/mechanism-algorithm/multi-signatures.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/mechanism-algorithm/multi-signatures.md b/docs/mechanism-algorithm/multi-signatures.md index a2ab119c..e3b98ed0 100644 --- a/docs/mechanism-algorithm/multi-signatures.md +++ b/docs/mechanism-algorithm/multi-signatures.md @@ -176,7 +176,7 @@ The above fees can be adjusted through proposals. 3. Call `AccountPermissionUpdateContract`. 4. Sign and broadcast the transaction. -An SR node cannot package a transaction that modifies its own witness permission into a block. If a node attempts to produce a block containing such a transaction, the block will fail signature verification. As a penalty, the node will be disconnected from the network by other peers for 1 hour. + #### Example Request: From 6081a47e5ee36c89782f1306bd553c5f84fd13a7 Mon Sep 17 00:00:00 2001 From: Grodex Date: Wed, 17 Dec 2025 17:50:28 +0800 Subject: [PATCH 4/6] Update multi-signatures.md --- docs/mechanism-algorithm/multi-signatures.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/mechanism-algorithm/multi-signatures.md b/docs/mechanism-algorithm/multi-signatures.md index e3b98ed0..b059d001 100644 --- a/docs/mechanism-algorithm/multi-signatures.md +++ b/docs/mechanism-algorithm/multi-signatures.md @@ -176,8 +176,6 @@ The above fees can be adjusted through proposals. 3. Call `AccountPermissionUpdateContract`. 4. Sign and broadcast the transaction. - - #### Example Request: ``` From 8c945e6bc179b0587db0da669a1fd58d11139aff Mon Sep 17 00:00:00 2001 From: Grodex Date: Mon, 22 Dec 2025 17:47:55 +0800 Subject: [PATCH 5/6] update on get started Update the wallet cli client text part according to the newest version --- .../getting_started_with_javatron.md | 37 +++++++++++-------- 1 file changed, 21 insertions(+), 16 deletions(-) diff --git a/docs/getting_started/getting_started_with_javatron.md b/docs/getting_started/getting_started_with_javatron.md index 3800d5d2..0d7cd940 100644 --- a/docs/getting_started/getting_started_with_javatron.md +++ b/docs/getting_started/getting_started_with_javatron.md @@ -90,11 +90,16 @@ At the prompt, enter the `registerwallet` command and follow the instructions to wallet> registerwallet Please input password. password: -user defined config file doesn't exist, use default config file in jar -WalletApi getRpcVsersion: 2 Please input password again. -password: -Register a wallet successful, keystore file name is UTC--2022-07-04T06-35-35.304000000Z--TQXjm2J8K2DKTV49MdfT2anjUehbU3WDJz.json +Please enter the number of mnemonic words + Default: 12 mnemonic words, + Enter 24 to use 24 mnemonic words + Press Enter to use the default (12). + Valid inputs are "12" or "24" +mnemonic file : ./Mnemonic/(your wallet address).json +Please name your wallet: +, keystore file : ./Wallet/(your wallet address).json +(Note: If you delete an account, make sure to delete the wallet file and mnemonic file) wallet> ``` @@ -257,14 +262,13 @@ The result is as follows: ``` { "address": "TUoHaVjx7n5xz8LwPRDckgFrDWhMhuSuJM", - "balance": 93643857919, + "balance": 93643d857919, "create_time": 1619681898000, - "latest_operation_time": 1655358327000, - "is_witness": true, - "asset_issued_name": "TestTRC10T", - "latest_consume_free_time": 1652948766000, + "net_window_size": 28800000, + "net_window_optimized": true, "account_resource": { - "latest_consume_time_for_energy": 1655358327000 + "energy_window_size": 28800000 + "energy_window_optimized": true }, ...... @@ -312,7 +316,7 @@ wallet> sendcoin TUznHJfHe6gdYY7gvWmf6bNZHuPHDZtowf 1000000 "raw_data_hex":"0a02cbc322088581ae7e29258a5240a89aefbf9c305a67080112630a2d747970652e676f6f676c65617069732e636f6d2f70726f746f636f6c2e5472616e73666572436f6e747261637412320a1541ce8a0cf0c16d48bcf22825f6053248df653c89ca121541d0b69631440f0a494bb51f7eee68ff5c593c00f018c0843d7098cfebbf9c30" } before sign transaction hex string is 0a85010a02cbc322088581ae7e29258a5240a89aefbf9c305a67080112630a2d747970652e676f6f676c65617069732e636f6d2f70726f746f636f6c2e5472616e73666572436f6e747261637412320a1541ce8a0cf0c16d48bcf22825f6053248df653c89ca121541d0b69631440f0a494bb51f7eee68ff5c593c00f018c0843d7098cfebbf9c30 -Please confirm and input your permission id, if input y or Y means default 0, other non-numeric characters will cancel transaction. +Please confirm and input your permission id, if input y/Y means default 0, other non-numeric characters will cancel transaction. ``` This command returns a transaction pending confirmation. Please follow the steps below to complete the signing and broadcasting: @@ -322,13 +326,14 @@ This command returns a transaction pending confirmation. Please follow the steps 3. Authorize with Password: Enter the password for the selected account. `wallet-cli` will then sign the transaction and broadcast it to the java-tron node, completing the transaction. ``` -Please confirm and input your permission id, if input y or Y means default 0, other non-numeric characters will cancel transaction. +Please confirm and input your permission id, if input y/Y means default 0, other non-numeric characters will cancel transaction. y Please choose your key for sign. -The 1st keystore file name is .DS_Store -The 2nd keystore file name is UTC--2022-07-04T06-35-35.304000000Z--TQXjm2J8K2DKTV49MdfT2anjUehbU3WDJz.json -The 3th keystore file name is UTC--2022-06-21T09-51-26.367000000Z--TUoHaVjx7n5xz8LwPRDckgFrDWhMhuSuJM.json -Please choose between 1 and 3 + +No. Address Name +1 (you wallet address) +2 (you wallet address) +Please choose between 1 and 2, or enter search to search wallets 3 Please input your password. password: From d0aaed5f6a53645f29407ae0323abdb5e7079b6e Mon Sep 17 00:00:00 2001 From: Grodex Date: Mon, 22 Dec 2025 17:55:50 +0800 Subject: [PATCH 6/6] Update getting_started_with_javatron.md --- docs/getting_started/getting_started_with_javatron.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/getting_started/getting_started_with_javatron.md b/docs/getting_started/getting_started_with_javatron.md index 0d7cd940..2c71e195 100644 --- a/docs/getting_started/getting_started_with_javatron.md +++ b/docs/getting_started/getting_started_with_javatron.md @@ -262,8 +262,8 @@ The result is as follows: ``` { "address": "TUoHaVjx7n5xz8LwPRDckgFrDWhMhuSuJM", - "balance": 93643d857919, - "create_time": 1619681898000, + "balance": 5, + "create_time": 1663487574000, "net_window_size": 28800000, "net_window_optimized": true, "account_resource": {