How we measure launch-wallet supply

1. The first transfer into a contract that then sends the token on to at least two different addresses: a liquidity add to a pool, or a launchpad seeding its bonding curve. This is when the token became buyable.
2. If no such contract exists yet: the deployer's first transfer to anyone else.
3. If the deployer is unknown: the first transfer that isn't a mint.

Pools, curves and routers active in the first seconds are never counted as wallets. Neither are the burn addresses, the token itself, or Virtuallock's contracts.

Deployer

Sent the token's creation transaction (or, without an explorer record, the transaction that minted the supply).

Before launch

Received tokens before the launch transfer: mint allocations, team splits.

First seconds

Received tokens within 10 seconds of the launch block, from anyone, including through a router.

From the deployer

Received tokens directly from the deployer (not through a pool) within 7 days of launch.

We describe what each wallet did. We don't label wallets or people. Receiving tokens early isn't proof of a link to the team.

• Circulating supply: total supply minus the balances of the 0x…dEaD and 0x0 addresses.
• Held by a wallet: its balance, plus its Virtuallock locks, plus its unvested and vested-but-unclaimed VestingVault tokens.
• Locked 30 days or more: Virtuallock locks that unlock at least 30 days from now, plus vesting still unvested 30 days from now. The same for 90 days and 1 year.
• Could be moved within 30 days: held minus locked 30 days or more. The band comes from this, as a share of circulating supply.

Mostly locked

Under 5% of circulating supply could be moved within 30 days.

Partly locked

5% to under 20%.

Mostly unlocked

20% or more.

No launch wallets identified

No wallet matched. That doesn't mean none exist.

Not enough data

Circulating supply couldn't be read.

• We don't see ETH transfers, so wallets funded with ETH by the team and buying later aren't linked. Only direct token transfers link wallets.
• Launchpad-specific data (such as tax-exempt buys) isn't decoded. Auction bidders on a crowd launch can look early.
• A deposit into another locker or a team multisig before the pool can be read as the launch if that contract then pays out to two or more addresses.
• A smart-contract wallet that buys and forwards tokens inside the first seconds is treated like a pool and drops out of the set.
• Only Virtuallock's TokenLock and VestingVault count as locked. Tokens in any other contract count as held, not locked.
• Rebasing tokens can drift, because balances are summed from Transfer events.

Tell us the token, the wallet and why. Contact the Virtuallock team through the channels listed on the Security page. The figures follow the published rules, so we change a rule (and the method version) rather than edit one token by hand.