every tron address is a gasless address
a tron hotwallet or child is now always created together with its gasless account, and deposit_address is that account. there is no second kind of tron address anymore: what you hand to your customer is the address that later sweeps and pays out without trx.
children created earlier that were missing a gasless account have been completed automatically. for those, deposit_address in GET /v1/hotwallets/tron/children now returns the gasless address. the address you handed out before keeps working: a deposit sent to it is still detected and can still be swept.
if the gasless address cannot be resolved at the moment of creation, nothing is created and the call says so. see the breaking change note above and the api reference.
deposits picked up in seconds, from any kind of sender
a tron deposit is now read from the transaction itself, so it no longer matters how the sender moved the usdt. plain wallets, exchanges that pay out through a contract, and payment processors that use transferFrom are all picked up the same way, within seconds of the block.
the deposit appears as detected right away and deposit.confirmed follows once the network confirms it, about a minute later on tron.
two safety nets sit behind that. when the transaction is not readable yet, we look again after 30 seconds, 90 seconds and 5 minutes. and the background check that used to watch only your newest addresses now goes through the older ones too, so an address you created months ago is still covered.
the tron network fee, apart, in the quote
GET /v1/quote?network=tron now returns two numbers instead of one. fee_usdt is our fee alone, the margin of your plan. network_fee_usdt is what the gasless rail charges in usdt inside the transfer, and it never passes through us.
both come for the typical case and for the worst case, which is an account making its first transfer and paying the one-time activation on top.
this has been live since september 26. sweep and withdraw responses carry the same network_fee_usdt, so what the quote says and what the operation reports line up. the current values are on the pricing page.
fixes and improvements
- the api reference now documents webhook deliveries in full: headers, both signatures with a verification example, and the retry schedule.