feat: tron sponsored tx doc

[LeoSlrRf]

TL;DR

Added documentation explaining Tron-specific protocol fees and how Request Network handles Tron resource sponsorship.

What changed?

A new section, "Tron-specific fees," has been added to the protocol fees documentation. It explains that:

• Tron transaction fees are paid in TRX and can be costly when a wallet burns TRX directly for energy and bandwidth.
• Request Network sponsors the required Tron resources via CatFee for energy and Tron Energy Rent for bandwidth, removing the need for payers to hold TRX.
• A fixed $5 payer-borne fee is applied to every Tron payment to cover these sponsored resource costs, which is less than what a payer would typically spend burning TRX directly.

How to test?

Navigate to the Protocol Fees documentation page and verify the new "Tron-specific fees" section appears at the bottom with accurate content and working links to CatFee and Tron Energy Rent.

Why make this change?

Payers using Tron may be confused about why a fixed $5 fee is applied or why they don't need TRX to broadcast transactions. This documentation clarifies the fee structure and the rationale behind using sponsored resource providers on Tron.

[LeoSlrRf]

• feat: tron sponsored tx doc #102 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Greptile Summary

This PR adds a new "Tron-specific fees" section to the protocol fees documentation, explaining that Request Network sponsors Tron network resources (energy and bandwidth) via third-party providers and passes a fixed $5 cost to the payer, which is explicitly stated to be on top of the standard 0.05% protocol fee.

• The new section correctly uses a <Note> callout to surface the $5 fee disclosure, and now explicitly states the flat fee is "charged in addition to the standard protocol fee," which resolves the earlier stacking ambiguity.
• Provider attribution language has been softened to "providers such as CatFee and Tron Energy Rent" (removing the specific energy vs. bandwidth role split that was flagged previously), but "such as" implies these are examples from a larger set — if these are the only two providers currently used, the wording slightly overstates optionality.
• The API response metadata format shown earlier in the page (protocolFee, platformFee) does not include a Tron-specific fee field; readers integrating Tron payments may want to know how the $5 fee is reflected in API responses or in what denomination it is collected.

Confidence Score: 5/5

Documentation-only change that is safe to merge; the fee stacking ambiguity from prior review rounds has been resolved explicitly in the Note.

The change adds a single prose section with no code, no API contract changes, and no configuration updates. The previously open question about whether the $5 fee stacks with the 0.05% protocol fee is now clearly answered inline. Remaining observations are about documentation completeness rather than correctness.

No files require special attention; api-features/protocol-fees.mdx is the only changed file and contains only additive prose.

Important Files Changed

Filename	Overview
api-features/protocol-fees.mdx	Adds "Tron-specific fees" section with correct callout and explicit fee-stacking disclosure; minor open questions around API response representation of the $5 fee and the "such as" provider wording.

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant Payer
    participant RequestNetwork as Request Network API
    participant Provider as Resource Providers (CatFee / Tron Energy Rent)
    participant Tron as Tron Blockchain

    Payer->>RequestNetwork: Initiate Tron payment (invoice + $5 Tron fee + 0.05% protocol fee)
    RequestNetwork->>Provider: Request energy and bandwidth sponsorship
    Provider-->>RequestNetwork: Resources confirmed
    RequestNetwork->>Tron: Broadcast transaction (sponsored, no TRX required from payer)
    Tron-->>RequestNetwork: Transaction confirmed
    RequestNetwork-->>Payer: Payment complete

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant Payer
    participant RequestNetwork as Request Network API
    participant Provider as Resource Providers (CatFee / Tron Energy Rent)
    participant Tron as Tron Blockchain

    Payer->>RequestNetwork: Initiate Tron payment (invoice + $5 Tron fee + 0.05% protocol fee)
    RequestNetwork->>Provider: Request energy and bandwidth sponsorship
    Provider-->>RequestNetwork: Resources confirmed
    RequestNetwork->>Tron: Broadcast transaction (sponsored, no TRX required from payer)
    Tron-->>RequestNetwork: Transaction confirmed
    RequestNetwork-->>Payer: Payment complete

Loading

_{Reviews (2): Last reviewed commit: "chore: update" | Re-trigger Greptile}

[greptile-apps]

Third-person "payers" / "payer" should be second-person "you" per the style guide's requirement to write in second person for instructions and procedures. The same applies to the last sentence of the next paragraph.

Suggested change

	To prevent payers from needing TRX to broadcast a transaction, Request Network covers the required Tron resources through dedicated providers. We use [CatFee](https://catfee.io/) to sponsor energy and [Tron Energy Rent](https://tronenergyrent.com/) to sponsor bandwidth. This provider-based flow makes Tron transactions cost less than if the payer burned TRX directly.
	To prevent you from needing TRX to broadcast a transaction, Request Network covers the required Tron resources through dedicated providers. We use [CatFee](https://catfee.io/) to sponsor energy and [Tron Energy Rent](https://tronenergyrent.com/) to sponsor bandwidth. This provider-based flow makes Tron transactions cost less than if you burned TRX directly.

Context Used: AGENTS.md (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[mintlify]

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

Project	Status	Preview	Updated (UTC)
request-network	🟢 Ready	View Preview	Jul 8, 2026, 2:43 PM

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

[MantisClone]

Looks good, but probably hold off on merging until the Tron sponsorship and fee changes are merge.