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.
Pre-launch
These metrics activate when the Payment Router is deployed (post-audit). Until then the dashboard shows the structure with zero values — no burn figures are estimated or simulated.
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%
Fiat payments never trigger a burn — only on-chain W3S payments do.
Burn metrics
Aggregate figures proven from the Payment Router contract once it is live.
Total W3S burned
0 W3S
Not yet activeTotal W3S paid via the platform
0 W3S
Not yet activePayment transactions
0
Not yet activeSupply reduction
0%
Not yet activeBurn 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 |
|---|---|---|
| No burn transactions yet. Once the Payment Router is deployed, each payment's burn will be listed here with an explorer link. | ||
Verify on-chain
Once deployed, the Payment Router address is published here and links to BscScan.
Payment Router: Address published at deployment
Pre-launch
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.