[Private Node] Are we up to the scratch?

[multicryptobank]

Hi.

New to this project.
Successfully deployed a private SR & Full node locally. Both tested ok.
Trying wallet-cli for the very first time.

config.conf

net {
type = testnet
}
fullnode = {
ip.list = [
"127.0.0.1:51051"
]
}
gasfree = {
mainnet = {
apiKey = ""
apiSecret = ""
}
testnet = {
apiKey = ""
apiSecret = ""
}
}
grpc = {
mainnet = {
apiKey = ""
}
}

Thanks in advance.

[lxcmyf]

@multicryptobank
How is your address generated? It can be seen from the figure that your address format is invalid. Please use the correct address format. This link can easily verify your address format: here

[warku123]

@multicryptobank
If getAddress can't return any value, maybe U need to check your config to ensure that U exactly connect to a peer. And also U need to run wallet-cli.jar in the initial repo.
I found wallet-cli.jar can't run out the repo, if I copy this jar to another folder, will get the phenomenon same as yours.

[lxcmyf]

@warku123
That's not true. GetAddress can get results without connecting to the correct node. You don't see it in the figure because the wallet address you logged in to doesn't conform to the official tron address format.

[warku123]

@lxcmyf
Actually, I copy the wallet-cli.jar out of the repo directory, and run getAccount to the same address.
In the repo directory(the right of the screenshot), it can return the correct result.
But out of the repo directory(the left of the screenshot), it can't return the correct result and return the address format error.

At the beginning, I consider that the wallet-cli.jar I just packed may use some resource in the repo. So I just running this program in the repo. But as you say, maybe this is a bug here, about the wallet-cli.jar can't identify the correct address format out of the repo folder?

BTW, I use arm and jdk17, maybe it also relate to the problem here?

[lxcmyf]

@warku123
What files or directories are there in the same directory as wallet-cli.jar outside and inside the repo you mentioned?

[warku123]

@lxcmyf
In both condition, the folder include the wallet config and log folder, like the screenshot below.

In the right condition, I just run ./gradlew build to build the jar package and run the java -jar wallet-cli.jar in the ~/tron/wallet-cli/build/libs.

In the left condition, I copy the wallet-cli.jar, wallet-1.0-SNAPSHOT.jar, log folder and wallet folder out to another folder ~/tron/local-wallet and run the java -jar wallet-cli.jar in ~/tron/local-wallet.

[lxcmyf]

@warku123
Have you configured config.conf in the wallet-cli.jar peer directory? If not, it will default to the configuration in the code. What network are you connected to? MAIN or NILE or private chain network? Or is it convenient to show your config.conf?

How is your address generated? Why is the address displayed by tronscan invalid?

[warku123]

@lxcmyf
I also run a private blockchain.

I noticed I used to configure a config.conf in ~/tron/local-wallet, but not in ~/tron/wallet-cli/build/libs. I delete the config.conf and the peer can work normally.

That difference maybe the reason of the different phenomenon.

Sorry of that I just provided an incorrect information.

I think @multicryptobank maybe use an incorrect config like me.

BTW, my address is TW64yhbXK6WaGqEUKfv13PWaAxveHMzjxC, your input is wrong. I can convert the address normally.

My incorrect config:

net {
 type = local
}

fullnode = {
  ip.list = [
    "localhost:50051"
  ]
}

# soliditynode = {
#  // the IPs in this list can only be totally set to solidity.
#  ip.list = [
#    "127.0.0.1:50051" // default solidity
#  ]
#  // NOTE: solidity node is optional
# }

# open ledger debug
# ledger_debug = true

# To use the lock and unlock function of the login account, it is necessary to configure
# lockAccount = true in the config.conf. The current login account is locked, which means that
# signatures and transactions are not allowed. After the current login account is locked, it can be
# unlocked. By default, it will be unlocked again after 300 seconds. Unlocking can specify
# parameters in seconds.

# lockAccount = true

# To use the gasfree feature, please first apply for an apikey and apiSecret.
# For details, please refer to
# https://docs.google.com/forms/d/e/1FAIpQLSc5EB1X8JN7LA4SAVAG99VziXEY6Kv6JxmlBry9rUBlwI-GaQ/viewform
gasfree = {
  mainnet = {
     apiKey = ""
     apiSecret = ""
  }
  testnet = {
     apiKey = ""
     apiSecret = ""
  }
}

# If gRPC requests on the main network are limited in speed, you can apply for a apiKey of trongrid to improve the user experience
grpc = {
  mainnet = {
    apiKey = ""
  }
}
# Set the maximum number of transactions and backup records that can be retained
maxRecords = 1000

Maybe can you help me fix the config?

[lxcmyf]

@warku123
Change your net.type to as shown in the figure. Don't worry. It doesn't mean that you will no longer connect to your private network.

[warku123]

@lxcmyf
Now it's OK to me, and also can access my private chain.

But back to the problem, the config file affect the peer's address judgement? Why?

[multicryptobank]

I found wallet-cli.jar can't run out the repo, if I copy this jar to another folder, will get the phenomenon same as yours.

The sentence ut supra makes no sense at all!

Is wallet-cli project production ready? How much QA?

Anyway, can we know what's wrong with this allegedly invalid address and how to fix it?

Cheers.

[lxcmyf]

@multicryptobank
Can you show your config.conf? Please check whether the net.type you configured in config.conf is mainnet. In addition, the official address format of Tron is encoded in base58, and the obtained addresses start with T, such as TW64yhbXK6WaGqEUKfv13PWaAxveHMzjxC.

[lxcmyf]

@warku123
net.type will affect the address format, as shown in the following code:

[multicryptobank]

@lxcmyf Please, PAY MORE ATTENTION!

Can you show your config.conf?

Already provided/shown!

You haven't answered any of the questions in/from my previous post! STAY FOCUSED! If you don't understand the issue at hand, seek assistance from a colleague.

Thanks for your patience.

[lxcmyf]

@multicryptobank
Please check carefully. Do you correct net.type to mainnet? If you read my reply to another person（@warku123 ）, you will understand everything.