Transparency first
Trust Center
Every number on this page is read live from the BSC chain or from verified-source contracts — what we promise is enforced by contracts, not press releases.
Live on-chain proof
Read directly from the live v2.0 contracts deployed on BSC testnet — refreshes every 60 seconds.
Total supply
1,000,000,000 W3S
Static valueLaunch status
Pre-TGE — transfers locked
Static valueSold / public-sale allocation
0 / 200,000,000
Static valueNetwork
BSC Testnet (97)
Platform metrics
Aggregates from the live database — growing with every new participant.
W3S Passports
—
Verified quests
—
Live projects
—
Badges awarded
—
Deployed contracts
Live v2.0 deployment on BSC testnet — explorer-verified addresses. Click any address and check for yourself.
| Contract | Address | Network |
|---|---|---|
| W3S token (BEP-20) | 0x8f1B…8582 | BSC Testnet (97) |
| Daily vesting | 0x0A80…b404 | BSC Testnet (97) |
| Public utility sale | 0x7C6A…9C4a | BSC Testnet (97) |
| Payment router (burn) | 0x623F…28EB | BSC Testnet (97) |
Multisig treasury
No single key controls the treasury — every transaction needs signer consensus.
The Web3 Serv treasury is a Safe wallet with a 3-of-5 threshold across independent signers. Any transfer or settings change requires three signatures — no single point of failure, no unilateral decisions.
What the contract enforces — not promises
These rules are written into verified-source contracts and proven by automated tests.
No transfers before TGE
Before TGE the token cannot be sold or transferred at the contract level itself — not merely a UI restriction.
Daily vesting, never monthly
Releases accrue per completed day via an on-chain formula, and rounding dust is swept exactly in the final claim.
Fixed supply — no new minting
1,000,000,000 W3S is minted once at deployment; the contract contains no additional mint function whatsoever.
Sales flow through vesting only
Every purchase is granted through the vesting contract automatically — buyers never receive free tokens before TGE.
Sale parameters are owner-gated
Price and limits can only change via the contract owner, and every change emits a public on-chain event.
Payment burn
5% of every W3S service payment is burned via the Payment Router — enforced by the deployed contract, not by policy alone.
- Total burned
- 0 W3S
- Payments routed
- 0
No service payment has routed through the Payment Router yet, so there is nothing to burn — every total below is a real zero read from the contract.
Compliance posture
A loyalty-and-access services platform — access and recognition, never profit promises.
Jurisdiction gate
The token sale sits behind a mandatory eligibility gate: server-side geolocation, VPN detection, and user attestation.
Disciplined vocabulary
Community rewards are loyalty & access only — automated tests keep profit-promise vocabulary out of production.
Data privacy
Data handling aligned with PDPL and GDPR principles: data minimisation, and no personal data ever written on-chain.
The block list covers 9 jurisdictions under the published eligibility policy.
Security & responsible disclosure
Found a vulnerability? Responsible reports are welcome.
Treasury custody is multisig, secrets live entirely outside the codebase, and every production change passes a test gate. To report a security issue, contact us through the channels in security.txt — we take reports seriously and respond fast.