How to get the mapping between number of network parameter and string name of it

[GrothenDI]

No description provided.

[ferdinand026]

@GrothenDI This doc provides the network id and the parameter name and value: https://developers.tron.network/reference/wallet-getchainparameters .

[King31T]

This doc provides the network id and the parameter name and value: https://developers.tron.network/reference/wallet-getchainparameters .

@ferdinand026 i have 2 questions

1. Why the number of parameters are not continuous?
2. We can see 70 parameters by using the api, but in tronscan there are only 65, the other 5 parameters don't have value, so how to assign values when these 5 parameters are used in main network?

[Sunny6889]

@King31T Which of these 5 parameters?

[King31T]

@Sunny6889 Actually, there are 15 keys don't have pairing values according to the return by api getchainparameters of mainnet, they are:
getAllowUpdateAccountName
getAllowAdaptiveEnergy
getTotalEnergyAverageUsage
getAllowAccountStateRoot
getAllowProtoFilterNum
getForbidTransferToContract
getAllowMarketTransaction
getMarketSellFee
getMarketCancelFee
getAllowPBFT
getAllowTransactionFeePool
getAllowNewResourceModel
getAllowTvmFreeze
getAllowTvmCompatibleEvm
getAllowAccountAssetOptimization

[laurenceja]

This doc provides the network id and the parameter name and value: https://developers.tron.network/reference/wallet-getchainparameters .

@ferdinand026 i have 2 questions

1. Why the number of parameters are not continuous?
2. We can see 70 parameters by using the api, but in tronscan there are only 65, the other 5 parameters don't have value, so how to assign values when these 5 parameters are used in main network?

@King31T 1. If multiple features are developed at the same time, each of which contains a parameter, but only one of them is released first, at this time it is possible that the IDs are not continuous.
2. Some parameters are deprecated, so they are not shown on tronscan.
3. If the value of the parameter is zero, getchainparameters will returns empty for that parameter.

[King31T]

This doc provides the network id and the parameter name and value: https://developers.tron.network/reference/wallet-getchainparameters .
@ferdinand026 i have 2 questions

1. Why the number of parameters are not continuous?
2. We can see 70 parameters by using the api, but in tronscan there are only 65, the other 5 parameters don't have value, so how to assign values when these 5 parameters are used in main network?

@King31T 1. If multiple features are developed at the same time, each of which contains a parameter, but only one of them is released first, at this time it is possible that the IDs are not continuous. 2. Some parameters are deprecated, so they are not shown on tronscan. 3. If the value of the parameter is zero, getchainparameters will returns empty for that parameter.

@laurenceja Is the parameter ID assigned during the release or during development?

[laurenceja]

This doc provides the network id and the parameter name and value: https://developers.tron.network/reference/wallet-getchainparameters .
@ferdinand026 i have 2 questions

1. Why the number of parameters are not continuous?
2. We can see 70 parameters by using the api, but in tronscan there are only 65, the other 5 parameters don't have value, so how to assign values when these 5 parameters are used in main network?

@King31T 1. If multiple features are developed at the same time, each of which contains a parameter, but only one of them is released first, at this time it is possible that the IDs are not continuous. 2. Some parameters are deprecated, so they are not shown on tronscan. 3. If the value of the parameter is zero, getchainparameters will returns empty for that parameter.

@laurenceja Is the parameter ID assigned during the release or during development?

I think development.