Skip to content
Menu

Wizz by Virtuals

$WIZZ

AI Agents

Researched

Is this your project? Claim and verify →

Wizz started as a contributor network helping Web3 projects grow through bounties, content, research and distribution. Today, we're expanding that network into a data layer for AI Agents by transforming those internet signals into structured, developer-ready data. Backed by 30,000+ users and 250+ partners, the network continuously generates real-world signals that power AI applications through DataCore.

Read more

What HEY knows

Building
No builder source linkedHEY holds no repository, changelog or feed it can read, so no count here is a measured zero.
FollowCreate alertTerminal preview
ShareShare on X

Follow puts Wizz by Virtuals on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me Wizz by Virtuals’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Known so far
Contract
0xfb60…17bb0xfb60fa2db6a8c6e7d510ad33551defae89a917bb
Deployed
2026-07-29, read from the chain
Launched via
Virtuals
Token market
Active market$146K fully diluted valuationToken verifiedThe project’s own site names this contract.

Same ticker, different contract: 1 other published project uses the ticker $WIZZ. This page: its site wizzhq.xyz names 0xfb60…17bb. WizzHQ by Virtuals: its site wlzzhq.xyz names 0x45c6…8641. HEY does not say which is the real one — only what each project’s own sources name.

Product usage
1 of 1 watched contract active · 199 calls in 7 days — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches.
Links
WebsiteX
Latest read
HEY last read this project’s records 6m ago.

What HEY can’t verify yet

  • Building activity — No repository, changelog or feed to read.
  • Repositories — No repository the project claims as its own.
  • Releases — No repository, changelog or feed to read.
  • API description — HEY has not read its website’s published files yet.
  • Official site changes — HEY has no first reading of its website to compare against yet.
  • Contract activity — Calls were read, but the days’ events could not be decoded.

HEY cannot answer whether anyone is building this yet (building activity: no source); it can answer 11 of the 17 research questions that apply.

What HEY is researching

  • Still to read: API description, Official site changes.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
No builder source linked.
HEY holds no repository, changelog or feed it can read building from, so it cannot say whether anyone is building.
SourceHEY holds no repository, changelog or feed it can read for this project.ReadWhat HEY derivedHEY’s activity rule reads the counted events as “No builder source linked”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Researched.
HEY researched this project; the gate has not found verified building evidence from its own sources.
Source15 registered sources, 0 of them context only.ReadWhat HEY derivedThe quality gate’s stored decision: “Researched”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Token verified.
Token verified: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.
SourceThe project's own published sources and HEY's check of the contract.ReadWhat HEY derivedToken verified: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Active market.
Active market: the pool holds liquidity and the token traded in the last day.
Source9 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Market figures are context only and never change activity status. Methodology
LinksWebsiteXDEX ScreenerRHToolsSources

Shared change · Official source change

Wizz by Virtuals' official site changed.

Links the official site declares changed: 2 added, 1 removed.

Observed by HEY on 2026-10-08Source: official site

View evidence ↗Evidence receipt

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about Wizz by Virtuals? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

11 changes on HEY’s record for Wizz by Virtuals: 2 contracts in use again or for the first time · 1 market check · 2 official source changes · 1 usage change · 5 other changes in 1 more kind.

All 11 changes for Wizz by Virtuals →

The full change record holds 14 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Sources

10 more sources (docs)

Security context: bug bounty page on the project’s site. An audit shows an audit took place; it is not a guarantee of safety.

Contract
0xfb60…17bb0xfb60fa2db6a8c6e7d510ad33551defae89a917bb