getchainparameters
POST
https://triport.io/rpc/tron/wallet/getchainparametersReturns the current native Tron chain-parameter object.
Tron mainnettron:rpcfree+; tron_read_rpc: 15 / 20 / 100 / 250 RPS (free / basic / pro / business; default, unmeasured)
getchainparameters returns the native network parameters visible at the time
the request is served. It is intended for clients that need the wallet-layer
chain configuration rather than one EVM-compatible scalar.
The response is a current snapshot. The request does not accept a block number, so it cannot be used to reconstruct historical chain-parameter state.
Parameters
The request body is a required empty JSON object.
bodyobjectrequiredMust be
{}; additional properties are rejected by the contract.Response
The concrete response example is unknown. tron.yaml defines an extensible
wallet object and does not publish a response example, so {} is shown only as
a schema-valid placeholder.
responseobjectCurrent chain parameters; field names are not enumerated by the contract.
Errors
Wallet failures use HTTP status plus JSON. See Tron errors.
| HTTP | Meaning | When it happens |
|---|---|---|
400 | Bad request | The request body is malformed or contains fields. |
401 | Unauthorized | The API key is missing or invalid. |
403 | Forbidden | The scope or tier does not permit the request. |
429 | Rate limited | The tron_read_rpc budget is exceeded. |
Examples
const response = await fetch("https://triport.io/rpc/tron/wallet/getchainparameters", {
method: "POST",
headers: { "x-token": process.env.TRIPORT_API_KEY, "Content-Type": "application/json" },
body: "{}",
});
const parameters = await response.json();Notes
- This is current chain state; no historical selector exists in the schema.
- Consumers should tolerate contract-permitted additional response properties.
- Related:
getnextmaintenancetime.