On-chain transparency
W3S Burn Dashboard
Paying an eligible service in W3S applies a 15% discount and burns 5% of the W3S paid, routing the remaining 95% to the treasury. Every burn is a supply mechanic recorded on-chain — not a return of any kind.
Payment policy
The published rates applied to every W3S service payment (config-driven, not editorial).
Service discount when paying in W3S
15%
W3S burned per payment
5%
Routed to the treasury
95%
USDT payments never burn — only W3S service payments do.
Burn metrics
Aggregate figures read directly from the Payment Router contract on BSC Testnet — refreshed every 60 seconds.
Total W3S burned
0 W3S
Live on-chainTotal W3S paid via the platform
0 W3S
Live on-chainPayment transactions
0
Live on-chainSupply reduction
0%
Live on-chainBurn by service type
How burns break down across eligible service categories.
Service-level burn totals appear here once payments settle on-chain. The eligible-services matrix is owner-ratified before launch.
Latest burns
The most recent burn transactions, each with a BscScan link.
| Transaction | W3S burned | When |
|---|---|---|
| The router is live and readable; no service payment has routed through it yet, so every total is a real zero. | ||
Verify on-chain
The deployed Payment Router address, linked to BscScan so every figure above can be checked against the chain.
Payment Router: 0x623F…28EB
Disclaimer
The burn is a token supply mechanic tied to real service usage. It is not an investment, yield, dividend, or a promise of price or profit. Figures shown are on-chain facts, never projections.