Document TRON gRPC service scope (full node services only)#405
Conversation
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.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughAdds 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. ChangesTRON gRPC Service Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 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.
- '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
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, andDatabase.Verified behavior
Tested against a live TRON mainnet node with generated Python stubs, one probe per service (multiple methods each):
protocol.WalletGetNowBlock,GetAccount,GetBlockByNum)protocol.DatabaseGetNowBlock)protocol.WalletSolidityUNIMPLEMENTED: Method not foundon every methodprotocol.WalletExtensionUNIMPLEMENTED: Method not foundChange
WalletSolidity/WalletExtensionare not served; use the HTTP/walletsolidityAPI for solidified (confirmed) data