A TRON node that provides transactions with resources itself
Proxy is a full mirror of a node. You change one line of configuration, and each of your senders receives Energy and Bandwidth at the moment of sending.
Path of a transaction
- 1
Node address
Replace the node address with your personal node address.
- 2
Senders
Add sender addresses or take them from Mate.
- 3
Calculation
The node calculates the Energy and Bandwidth of every transaction.
- 4
Sending
The resource reaches the sender, the transaction goes to the network in its original form.
One line in the configuration
Your service builds and signs transactions exactly as it does today. The node address changes — everything else stays in place: code, keys, response handling.
The response to a broadcast arrives after the resource is supplied, so allow a few seconds in the timeout.
# TRON node tron: - node_url: http://10.0.4.12:8090 + node_url: https://n-7f3a.proxy.example + timeout: 15s
What the node does
-
A full node mirror
HTTP fullnode, solidity and PBFT, JSON-RPC, gRPC. Responses match those of a TRON node.
-
Calculation before sending
The node calculates the Energy and Bandwidth of the transaction on our node and supplies the sender with exactly that volume.
-
The transaction in its original form
Proxy receives the transaction already signed. The signature fixes every field — the recipient, the amount, the contract: the network rejects a changed transaction. We supply the resource to the sender, pass the transaction to the network as is and see exactly what any node of the network sees.
-
A personal node address
The node serves the list of your senders. You manage the list in the cabinet.
-
Payment for what was consumed
The same unit as in Mate: the resource the transaction consumed from our supply.
-
Full transparency
Every broadcast is in the journal: txid, block, Energy, Bandwidth, delegation.
Questions
- Where do the keys stay?
- With you. Your service builds and signs the transaction, and it reaches the node already signed. The signature fixes every field, so the node passes to the network exactly what it received.
- How does the node treat other addresses?
- Transactions of addresses outside your list go to the network as through a regular node.