/wallet/validateaddress

Validate the format of an address (auto-detects hex / base58check / base64). Does not query the chain — only checks encoding + checksum.

• Source: framework/src/main/java/org/tron/core/services/http/ValidateAddressServlet.java
• Method: GET / POST

Request parameters

Field	Type	Required	Description
address	string	Yes	Address to validate; format is detected by length: 42 chars hex / 34 chars base58check / 28 chars base64

Example:

curl --request POST \
     --url https://nile.trongrid.io/wallet/validateaddress \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '
{ "address": "41dd791d6b49e190062d650e6a23c575510d35f2f9" }
'

Response

Field	Type	Description
result	bool	Whether the address is valid
message	string	Hex string format / Base58check format / Base64 format / Length error / Invalid address

Response example:

{ "result": true, "message": "Hex string format" }

Error responses

Address-parsing errors (length mismatch, checksum failure, base58/base64 decode failure, etc.) are conveyed via result=false plus message — they do not produce an {"Error": ...} body.

However, two steps in doPost run before validAddress and can throw, and the servlet's outer catch (Exception e) only calls logger.debug without writing a response body — clients receive HTTP 200 with an empty body:

Trigger	Response
Request body exceeds node.maxMessageSize (POST)	Empty body (Util.checkBodySize throws java.lang.Exception, which is swallowed by the catch)
Request body is not valid JSON (POST)	Empty body (JSON.parseObject throws com.alibaba.fastjson.JSONException, which is swallowed)

The GET path does not read the body, so the two cases above only trigger on POST.

---