January 5, 2026
Burn Event #7
Summary of Burn Event #7:
| Parameter | Details |
| Event Date | January 4, 2026 |
| Pledged CBPAY Tokens* | 62,500,000 |
| Total XDB Burned (event #7) | 12,204,647.53 |
| Total XDB Burned (BBB events only) | 238,533,334.43 |
| Total XDB Burned since launch | 1,264,163,369.6 |
*during this event CBPAY tokens were sold to OTC markets in light of lack of liquidity on the available market pairs
Branded Coins issued on XDB CHAIN allocate up to 2.5% of their supply to recurring XDB burns. Burns run quarterly through dedicated public burn addresses — every event is numbered, published, and auditable on-chain.
Official BURN Address and Impact on Supply
The balance of the official burn address has been updated following Burn Event #7, the fourth BBB event on XDB CHAIN after the launch of CBPAY. The burn address now holds 1,264,163,369.6 XDB CHAIN native coins (XDB), reducing the total supply by 12,204,647.53 XDB to 18,735,836,630 XDB coins. You can view the transaction details TRX Link
This move further reduces the circulating supply, from 17,039,341,340 to 17,027,136.692.
Recap of Official BURN Parameters:
| Parameter | Details |
| Burn Address Balance | 1,264,163,369.6 BURN Address Link |
| Total Supply Reduction | 12,204,647.53 XDB |
| New Total Supply | 18,735,836,630 XDB |
| Transaction Details | TRX Link |
How Burning Works on XDB CHAIN
By submitting transactions on the XDB CHAIN network with specific parameters like zero weights and thresholds, developers can invalidate keys, including the master key, preventing further transactions and token creation. This is how token BURN works on XDB CHAIN This feature, primarily for developers, can significantly impact the overall supply of the cryptocurrency. Detailed information on this feature is available in the official XDB CHAIN documentation with the launch of XDB Chain v19.
Creating a “BURN” Address (Technical Instructions)
Developers can create a “locked address” to burn tokens. Once transferred, these tokens become unusable in any future transaction. This process involves setting the weights and thresholds to zero, creating a scenario where all keys, including the master key, become invalid, effectively locking the account forever.
Conclusions
Burn #7 is now complete. The BBB framework reduces XDB supply over time through published, verifiable on-chain burn events. Subsequent burn events are announced when completed.
Disclosure note: This communication is informational and summarizes the burn event based on the referenced on-chain transaction and reported burn totals. It does not constitute financial advice or an offer to buy or sell any asset.
