Multisig
No single party can move funds alone.
W3S Token
W3S powers service payments, discounts, community rewards, and transparency across the Web3 Serv platform. This page describes what W3S is and how it is used.
W3S is a utility token designed for use within the Web3 Serv ecosystem. It is used to pay for eligible services at a discount, to reward community participation, and to power on-chain transparency. W3S is a BEP-20 token on the BNB Smart Chain.
What W3S is used for across the platform.
Service payments
Pay for eligible Web3 Serv services directly in W3S.
Service discount
Receive a 15% discount on the eligible service price when paying in W3S.
Supply burn
5% of each eligible W3S service payment is burned, tying supply to real service usage.
Community rewards
Earn Locked W3S Credits for verified community participation.
On-chain transparency
Payments, burns, and treasury flows are verifiable on-chain.
Eligible services can be paid using W3S. Paying in W3S applies a 15% discount on the eligible service price, and 5% of the W3S payment amount is automatically burned. USDT payments never burn — only W3S service payments do.
15%
W3S discount
5%
W3S burn
Community participation is rewarded with Locked W3S Credits. Before TGE these credits are locked and are non-transferable, non-sellable, and non-withdrawable. They are subject to verification, KYC, fraud checks, and final eligibility review.
Key public utility sale terms. All values are drawn from the platform configuration.
| Sale allocation | 200,000,000 W3S |
| Payment currency | USDT only |
| Price | 0.25 USDT / W3S |
| Per-wallet minimum | 100 USDT |
| Vesting | 25% at TGE + daily over 365 days |
| Sold / allocation | 400 / 200,000,000Live on-chain |
KYC is mandatory before purchase.
Public sale tokens release 25% at TGE, with the remainder vesting daily over 365 days. Transfers are disabled before TGE at the smart-contract level, not only in the interface.
The complete supply distribution across all categories, each category's daily vesting schedule, and the illustrative circulating-supply curve.
Per category: an instant TGE unlock, a full-lock cliff, then daily linear release — no cliffs dumps.
No token — including public-sale purchases — can be sold or transferred before the Token Generation Event. Enforced at the smart-contract level.
Every gradual release is computed and unlocked daily instead of monthly batches — smoother, fairer distribution with less sell pressure.
| Category | Share | Amount (W3S) | TGE unlock | Cliff | Daily release |
|---|---|---|---|---|---|
| Public Utility Sale | 20% | 200,000,000 | ≈ 25% | — | 365 days |
| Team & Founders | 10% | 100,000,000 | 0% | 12 months | 36 months |
| Ecosystem & Community Boost | 17% | 170,000,000 | 0% | — | 48 months |
| Treasury & Operations | 16% | 160,000,000 | 0% | — | 48 months |
| Liquidity & Listings | 12% | 120,000,000 | 0% | — | 36 months |
| Launchpad & Project Grants | 12% | 120,000,000 | 0% | — | 48 months |
| Marketing & Growth | 7% | 70,000,000 | 0% | — | 24 months |
| Advisors & Strategic Partners | 3% | 30,000,000 | 0% | 6 months | 24 months |
| Security, Audit & Compliance Reserve | 3% | 30,000,000 | 0% | — | 36 months |
A purchase of 100,000 W3S: 25% (25,000) unlocks at TGE, then ≈ 205.48 W3S releases daily over 365 days until fully vested (one year from TGE).
An illustrative lower bound pending final TGE calibration — a disciplined float signalling responsible supply management.
50,000,000 / 1,000,000,000 W3S
A smooth, ascending unlock curve with no cliff dumps thanks to daily vesting — new tokens enter circulation as operational demand grows.
Roadmap
Five stages ordered by dependency, not by date. Each one states what already works, what is built but empty, and what is deliberately switched off — and ends on a condition anyone can check.
Ends whenthe contracts are deployed, publicly verified, and no longer owned by a single key.
Ends whenthe directories hold published work rather than empty states, and services are delivered for revenue.
Ends whenan independent audit is published, the owner lifts the mainnet hold, and the token generation event fires.
Ends whenservice payments settle in W3S and the burn total on the public dashboard stops being zero.
Ends whenthis stage does not end — it compounds.
No dates: the two decisive gates — an external contract re-audit and the mainnet lift — are paced by auditors and by the owner's signature, not by a calendar we control. Publishing a date we cannot keep would be the least trustworthy thing on this page.
Treasury & Transparency
Operations are run by the team with transparent, published reporting.
Treasury funds move only through a 3-of-5 multisig — no unilateral action.
Treasury and burn activity are published on BscScan for public verification.
No single party can move funds alone.
Treasury and burn activity published on BscScan every quarter.
Clear allocation — partnerships, development, project support — instead of discretionary spending.
A held-back portion for market volatility and operational continuity.
Contract addresses, token supply, burns, and treasury custody are published and verifiable on-chain. Figures shown across the platform are on-chain facts, never projections.
View trust & verificationToken disclaimer
W3S is a utility token designed for use within the Web3 Serv ecosystem. It does not represent equity, ownership, dividends, profit-sharing rights, or guaranteed returns.