Virvi BEATsCheck a wallet

How BEATs work

A BEAT (Basic Event Attendance Token) is an on-chain record that someone was at an event. Hosts create one for their event; the people who come receive it in their wallet, free, as proof they were there. It’s built to be open by default and private where it matters, and to survive a lost or stolen wallet.

The token

  • Every BEAT comes from one public ERC-1155 contract on Polygon, 0x2ca6538745C5D611F14291631B16373B05F1F0d3. Each event is its own token id.
  • Claiming is free. Attendees never sign or pay anything: Virvi sends the token and pays the network fee, and the host pays a flat price per event.
  • A BEAT can’t be sold or sent on by default, so it keeps proving who was there. A host can make theirs tradeable when creating it; that choice is fixed on chain and can never change.
  • There’s no token sale, and a BEAT carries no promise of value. Its name, picture, place and time are its metadata.

Given out where people gather

  • In the metaverse, automatically. In a Virvi scene, an attendee chooses to track their attendance, stays as long as the host asks, and claims. Live today in Decentraland.
  • In AR experiences. The same tracking and claiming in Virvi’s AR spaces. Planned.
  • At in-person events. The host scans attendees’ wallet codes at the door, or shows a code that changes every 30 seconds for attendees to scan. Planned.

Wherever it’s given out, it’s the same token on the same contract, with one supply and one claim per wallet.

Open and on chain

  • The contract’s source code is published and verified on Polygonscan and Sourcify, and Virvi’s code is public on GitHub.
  • No single key controls it. The admin is a Safe multisig, 0xd119BDeA989C2816b412D8ECd7368f2C9C7F45b6, that needs two of three signers. Virvi’s server holds only a minter key, which can create, send and close BEATs, and nothing else: it can’t move anyone’s tokens or change the contract.
  • The transparency page shows the live contract, the commit it was deployed from, and the signed build Virvi runs, so anyone can check it against the code.
  • More chains, planned. BEATs live on Polygon today. Solana and other chains are planned, so attendees can choose where their BEAT is minted. Each attendee will still get one BEAT per event, on the chain they choose.

Private by design

BEATs follow the Standards for Ethical Analytics and Data Collection in the Metaverse, the open privacy whitepaper Virvi published in 2023: informed consent, collecting only what’s needed, and the user in control. In practice:

  • Nothing until you opt in. Attendance is tracked only after the attendee agrees, and the consent says exactly what’s stored and what becomes public.
  • Only what’s needed. A wallet address, a display name and how long they stayed. Per-network limits use a scrambled, keyed code, never an internet address, and aren’t linked to the claim.
  • On chain, only the essentials. The blockchain records the wallet, the BEAT and when it was sent. Names and time spent stay off chain.
  • In the attendee’s control. Stopping before claiming deletes what was stored. Deleting their data later removes their name, time and account link from BEATs already sent; unclaimed data is deleted 30 days after the event.

The full details are on Virvi’s privacy page.

If a wallet is compromised

A BEAT that can’t be transferred would be lost with a stolen wallet. Instead, the contract has a reissue built in:

  1. The owner asks for their BEATs to be moved to a new wallet from their Virvi settings.
  2. Virvi reviews the request. On approval, the old wallet is blocked from the account and from BEATs.
  3. The Safe’s signers approve the move, and the contract sends a fresh copy to the new wallet.
  4. The contract records for good that the old copy was replaced. The old copy can never move again, and collection pages show only the new one.

The record stays open, the attendee keeps their proof, and whoever took the old wallet gets nothing they can use.

Check a wallet’s BEATsAbout Virvisupport@virvi.io