Skip to content

Document TRON gRPC service scope (full node services only)#405

Merged
akegaviar merged 3 commits into
mainfrom
docs/tron-grpc-service-scope
Jun 3, 2026
Merged

Document TRON gRPC service scope (full node services only)#405
akegaviar merged 3 commits into
mainfrom
docs/tron-grpc-service-scope

Conversation

@akegaviar
Copy link
Copy Markdown
Member

What

The TRON tooling page documents the gRPC endpoint, x-token auth, and proto setup, but not which gRPC services the endpoint serves — the most common follow-up question for anyone coming from java-tron's two-port model (full gRPC on 50051, solidity gRPC on 50061) or generating clients from the official protos, which define Wallet, WalletSolidity, WalletExtension, and Database.

Verified behavior

Tested against a live TRON mainnet node with generated Python stubs, one probe per service (multiple methods each):

Service Result
protocol.Wallet ✅ responds (GetNowBlock, GetAccount, GetBlockByNum)
protocol.Database ✅ responds (GetNowBlock)
protocol.WalletSolidity UNIMPLEMENTED: Method not found on every method
protocol.WalletExtension UNIMPLEMENTED: Method not found

Change

  • Add an Available services table to the gRPC section: the endpoint maps to the full node API; WalletSolidity/WalletExtension are not served; use the HTTP /walletsolidity API for solidified (confirmed) data
  • Note the difference from setups that expose a separate solidity gRPC port
  • Cross-link from the top support callout

The gRPC section listed the endpoint, auth, and proto setup but not
which gRPC services the endpoint actually serves. Verified against a
live TRON mainnet node:

- protocol.Wallet and protocol.Database respond
- protocol.WalletSolidity and protocol.WalletExtension return
  UNIMPLEMENTED (Method not found) on every method

Add an 'Available services' table stating the endpoint maps to the
full node API, note the difference from setups that expose a separate
solidity gRPC port, and point readers to the HTTP /walletsolidity API
for solidified data.
@infra-bot-atlantis
Copy link
Copy Markdown

Error: This repo is not allowlisted for Atlantis.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 3, 2026

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0e0c7f1c-6399-4dbb-8685-da47e3af370e

📥 Commits

Reviewing files that changed from the base of the PR and between 3d0a69b and 3023238.

📒 Files selected for processing (1)
  • docs/tron-tooling.mdx
✅ Files skipped from review due to trivial changes (1)
  • docs/tron-tooling.mdx

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Enhanced TRON gRPC documentation with detailed service availability information
    • Added clarity on which services are supported and alternatives for unsupported ones
    • Updated server reflection and proto file guidance

Walkthrough

Adds an "Available services" subsection to TRON gRPC docs, links the Info gRPC bullet to it, lists which proto services Chainstack serves (Wallet, Database) vs unserved ones, explains UNIMPLEMENTED responses, and updates proto/reflection guidance.

Changes

TRON gRPC Service Documentation

Layer / File(s) Summary
TRON gRPC service availability and usage guidance
docs/tron-tooling.mdx
gRPC support bullet is bolded and linked to a new "Available services" section that documents protocol service support (protocol.Wallet and protocol.Database available; protocol.WalletSolidity, protocol.WalletExtension, protocol.Monitor not served), notes unserved services return gRPC UNIMPLEMENTED, instructs clients to use the Wallet stub and the node HTTP /walletsolidity for solidified data, warns that reflection may advertise unserved services, and updates the Proto files text regarding reflection and proto definitions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • chainstack/dev-portal#260: Introduced the TRON gRPC tooling/content that this PR refines with an "Available services" listing and service-mapping clarifications.

Poem

🐰 I nibble docs with tidy paws,
Linking services, fixing flaws,
Wallet sings and Database hums,
Reflection teases, truth becomes,
Hop—solid data finds its cause.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title directly and accurately describes the main objective of the PR—documenting which TRON gRPC services are served by the endpoint (full node services only).
Description check ✅ Passed The description is well-related to the changeset, providing context, verified behavior, and specific details about which services are served and why the change matters.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/tron-grpc-service-scope

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented Jun 3, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
chainstack 🟢 Ready View Preview Jun 3, 2026, 3:27 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Verified live: the endpoint serves gRPC server reflection (v1 and
v1alpha), and the reflection list advertises every service from the
TRON protos including ones that are not routed (WalletSolidity,
WalletExtension, Monitor). Fix the stale 'no server reflection' claim
and warn against inferring availability from reflection.
Comment thread docs/tron-tooling.mdx Outdated
Comment thread docs/tron-tooling.mdx Outdated
- 'currently serves' + 'Not available yet' instead of 'full node
  services only' and per-row error strings
- Keep the UNIMPLEMENTED error string once in prose for searchability
@akegaviar akegaviar merged commit f789a6e into main Jun 3, 2026
3 checks passed
@akegaviar akegaviar deleted the docs/tron-grpc-service-scope branch June 3, 2026 04:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants