GoTRON FAQs

Question 1

Does GoTRON support transaction signing and broadcasting?

Accepted Answer

GoTRON primarily focuses on building *unsigned* transactions. For local deployments, it offers an *opt-in* feature to sign and broadcast transactions using a local keystore for enhanced control. This functionality is automatically disabled in hosted (zero-install) mode for security.

Question 2

What types of TRON operations can AI agents perform with GoTRON?

Accepted Answer

AI agents can perform extensive read-only operations including fetching account details, TRC20 token balances, block information, smart contract ABIs, and governance proposals. They can also build unsigned transactions for TRX transfers, TRC20 transfers, staking, voting, and smart contract calls.

Question 3

How can I deploy and integrate GoTRON into my projects?

Accepted Answer

GoTRON offers flexible deployment options: a local server installable via Go, Homebrew, curl, or Docker, providing stdio/HTTP transport. Alternatively, a zero-install hosted mode is available for direct HTTP connections. It's designed for seamless integration with AI agent platforms like Claude Desktop.

Question 4

What is GoTRON and its primary purpose?

Accepted Answer

GoTRON is an MCP (Model Context Protocol) server that empowers AI agents to interact with the TRON blockchain. It enables them to query comprehensive TRON data, such as balances, tokens, blocks, and also to construct unsigned transactions.

Question 5

What are the key security considerations when using GoTRON?

Accepted Answer

GoTRON prioritizes security. It never stores or directly manages private keys. All transaction builders return unsigned transaction hex, requiring explicit user signing. Keystore signing is an opt-in local feature, and in hosted mode, all write and sign tools are automatically disabled for maximum security.

GoTRON

GoTRON

Key Features

Use Cases

Key Features

Use Cases