Block:87,725,416
Transactions:380
Transfers:158
Contracts:60
Delegations:99
Stakes:0
Tokens:0
Energy:4.9M
TronRelic
← All posts

TronLink Adds TRONSCAN API Security Services for On-Chain Risk Control

tronlinktronscanwallet-securityusdttethertron-tipsmultisig-feetvm

Drafted with AI, reviewed and published by a human editor.

TronLink now works with TRONSCAN's API Security Services, which the wallet describes as an on-chain risk-control solution from TRONSCAN, the TRON ecosystem's official explorer, according to @TronLinkWallet (Nov 4, 13:00 UTC; post). The post links to more details but does not say which TronLink versions or features use the service.

TRON's all-time transfer volume has passed $31 trillion, @TRONSCAN_ORG reported (Nov 4, 14:30 UTC; post).

On-Chain

According to TronRelic's on-chain data, Tether destroyed the USDT held by at least nine TRON addresses that were already on its freeze list. All of it happened between Nov 4, 15:55 UTC and Nov 4, 15:56 UTC. The largest amount was 5,488,287.95 USDT at TRafR5rg6ADs8TPiE71K3m1Vtc8pXecT6C (transaction). The other eight were:

  • 229,794.42 USDT at TMnNWAT1CrKgYPXZ8CyfA4Ko3c9po8Ka7h (transaction)
  • 214,837.26 USDT at TCs1nqiooT5JuSyjNtL6Nh8omsUVaWULBn (transaction)
  • 205,174.18 USDT at TQCp1sKYigTMEADjGsvoVQYCyZVwNGs62W (transaction)
  • 157,258.92 USDT at TKRZEmNeMazqEdEGkdiYhSgedMyXLAT3bi (transaction)
  • 150,165.36 USDT at TCBkd7qBzo9y4twS6TqFDQtjbui3tSFzax (transaction)
  • 85,388.09 USDT at TYf7vFyhU9jTt5pJ6f7114bE1BdJx2oZex (transaction)
  • 65,997.71 USDT at TMeEucdrpPs4fvn4uPGSR4eWVSFmtCSvFK (transaction)
  • 10,717.86 USDT at TAubH3AjxkFsafxex26N2SkNcY9d7zBx1t (transaction)

Project Updates

TIP #938: the burn-share figures may be overstated. waynercheung is an outside commenter with no commit history in this repository. He wrote that if you divide the reported multisignature surcharge burn by total burn, you get about 0.59% for 2026-Q1 and 0.70% for Q3. The proposal's caption gives 0.64% and 0.72%, and he traced the difference to a weighted spreadsheet column. He also asked for three things:

  • a review after activation, covering one full quarter
  • a fix for an empty spreadsheet cell, which explains an 806 TRX gap in the Q1 total
  • a note saying that failed transactions are excluded from both figures

(comment, Nov 4, 11:48 UTC)

Earlier the same day, repository contributor lxcmyf called the 0.5 TRX target a reasonable, more conservative cut. He also pointed out that a multi-signed transaction included in a block still pays the surcharge when its contract call fails, because the fee is charged before the contract runs. Excluding failed transactions therefore leaves that burn out of the dataset (comment, Nov 4, 03:01 UTC). Issue #938, "Proposal: Decrease getMultiSignFee fees," would lower chain parameter 23 from 1 TRX to 0.5 TRX per multi-signed transaction.

TIP-945: regression tests pass. yanghang8612, a repository contributor and the author of TIP-945, said the processor and virtual machine regression tests for it pass in java-tron PR #7069. He has also added examples to the specification. They show results on both sides of the rounding boundary, delegated-out balances, branches where no transfer happens, repeated operations and rollback, and how an existing offset in global stake weights is preserved (comment, Nov 4, 08:27 UTC). TIP-945, "Optimize TVM Resource Processing," is an open draft. It covers vote-list validation and Stake 2.0 weight accounting when a contract self-destructs.

TIP-944: same author, matching PR. For TIP-944, yanghang8612 pointed to PR #7068 for the matching regression tests. The specification now maps each quantity to its account fields and gives before-and-after examples for:

  • initialization
  • receiving stake
  • source cleanup
  • repeated operations
  • rollback of the enclosing call

(comment, Nov 4, 08:27 UTC). TIP-944, "Optimize TVM Voting Power Management," is an open draft. It proposes an ALLOW_TVM_VOTE_POWER_OPTIMIZATION switch to bring voting-power handling inside the TRON Virtual Machine in line with native transactions.

Briefly

@trondao repeated the $19.4B single-day USDT figure that TronRelic covered on Nov 4. This time it added, citing @Crypto_Briefing, that TRON handles roughly 73% of stablecoin transfer volume across major blockchains (Nov 4, 23:18 UTC; post).

TRON's protocol revenue was $224 million in October 2026, and the network averaged 11.58 million transactions a day, per a Chinese-language post from @trondaoCN (Nov 4, 09:06 UTC; post).

@usddio_cn posted USDD's October report. It puts total staked assets at $2.2B, sUSDD TVL at $170.54M, circulating supply at 1.5B and Smart Allocator investment income at $33.59M (Nov 4, 07:36 UTC; post).

Tron Inc. bought 154,403 TRX at an average price of $0.3238, which takes its treasury above 721.9 million TRX, per @TRON_INC (Nov 4, 01:15 UTC; post).

Tether froze at least 15 TRON addresses between Nov 4, 03:13 UTC and Nov 4, 22:07 UTC, according to TronRelic's on-chain data.

On Nov 3, TRON processed at least 12.65 million transactions and burned at least 3.33 million TRX in fees, according to TronRelic's on-chain data.