Skip to main content
POST
/
95e61622bf6a8af293978377718e3b77
/
wallet
/
clearabi
wallet/clearabi
curl --request POST \
  --url https://tron-mainnet.core.chainstack.com/95e61622bf6a8af293978377718e3b77/wallet/clearabi \
  --header 'Content-Type: application/json' \
  --data '
{
  "owner_address": "THPvaUhoh2Qn2y9THCZML3H815hhFhn5YC",
  "contract_address": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t",
  "visible": true
}
'
{
  "visible": true,
  "txID": "<string>",
  "raw_data": {
    "contract": "<array>",
    "ref_block_bytes": "<string>",
    "ref_block_hash": "<string>",
    "expiration": 123,
    "timestamp": 123
  },
  "raw_data_hex": "<string>"
}
TRON API method that clears (removes) the ABI (Application Binary Interface) information from a smart contract. This operation removes the contract’s ABI data from the blockchain, making the contract functions less discoverable but still executable if the function signatures are known.
Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.

​
Parameters

  • owner_address — address of the contract owner who can clear the ABI
  • contract_address — address of the smart contract to clear ABI for
  • visible — boolean indicating whether to use visible (Base58) address format instead of hex

​
Response

  • visible — boolean indicating whether addresses are in visible format
  • txID — unique transaction ID for the ABI clearing transaction
  • raw_data — raw transaction data containing:
    • contract — array with contract ABI clearing details
    • ref_block_bytes — reference block bytes for transaction validation
    • ref_block_hash — hash of the reference block
    • expiration — transaction expiration timestamp
    • timestamp — transaction creation timestamp
  • raw_data_hex — complete transaction data encoded in hexadecimal format

​
Use case

The wallet/clearabi method is used for:
  • Removing contract ABI information for privacy or security reasons.
  • Cleaning up contract metadata when ABI information is no longer needed.
  • Implementing obfuscation strategies for proprietary smart contracts.
  • Managing contract visibility and discoverability in explorers.
  • Reducing on-chain storage by removing unnecessary ABI data.
  • Preparing contracts for migration or deprecation processes.
Clearing the ABI makes the contract less user-friendly as tools and interfaces will not be able to automatically understand the contract’s functions. However, the contract remains fully functional and can still be called using raw function signatures and data.

​
curl example

Shell
curl --request POST \
  --url 'https://tron-mainnet.core.chainstack.com/95e61622bf6a8af293978377718e3b77/wallet/clearabi' \
  --header 'Content-Type: application/json' \
  --data '{
  "owner_address": "THPvaUhoh2Qn2y9THCZML3H815hhFhn5YC",
  "contract_address": "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t",
  "visible": true
}'

Body

application/json
​
owner_address
string
required

Address of the contract owner

​
contract_address
string
required

Address of the smart contract

​
visible
boolean

Whether to use visible (Base58) address format

Response

200 - application/json

Contract ABI clearing transaction

​
visible
boolean

Whether addresses are in visible format

​
txID
string

Transaction ID for the ABI clearing

​
raw_data
object
​
raw_data_hex
string

Raw transaction data in hex format

Last modified on November 1, 2025