Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Discrepancies in TON Network Burning Mechanism: Elector Smart Contract, Burn Address, and Tonstat Data - What's Going On?

I have a question about the burning mechanism. It seems that the Elector smart contract does not send half of network fees to black hole address.

Indeed, the burn address (https://tonscan.org/address/EQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAM9c#transactions) supposedly dedicated to burning contains only 321 TON, far from the 12750 burned coins reported by tonstat. The .ton DNS address (https://tonscan.org/address/EQC3dNlesgVD8YbAazcauIrXBPfiVhMMr5YYk2in0Mtsz0Bz), which is supposed to contain the frozen TON resulting from the domain purchase contains 5.15 M, again different from the 6.09 M reported by tonstat.

I wonder where tonstat (tonapi) gets its data from.
Moreover, according to the network config (https://explorer.toncoin.org/config#configparam5) the parameter 5 is the black hole address, however it is not present in the documentation (https://docs.ton.org/develop/howto/blockchain-configs), probably because it is outdated (26/05/23).

This question was imported from Telegram Chat: https://t.me/tondev_eng/31129

Posted 12 months ago
Votes Newest


Hi, I think the burn address for each block is not the same as the address you've pasted here. That might be the reason.

Posted 12 months ago
1 Answer
12 months ago
12 months ago