← Back to Virvi

Transparency and safety

Virvi’s code is public at github.com/virvi-xr/virvi. Every release is built from a public commit by GitHub Actions, which signs a record of exactly what it built. This page shows which commit is running, and how to check it yourself.

What’s running now

Loading what’s running…

Smart contracts

BEATs, Virvi’s free attendance tokens, are made by one public contract on each network. Its source should be published on Polygonscan, the public record of the Polygon blockchain, so you can check it matches the code in the repo.

Loading…

Ask your AI agent to check

Paste this into an AI agent that can read GitHub and websites. It reviews the code for you and reports back in plain language.

Please check the Virvi app for me. Its code is public at https://github.com/virvi-xr/virvi.

1. Wallets: find every place the code asks a wallet to sign or send something. Confirm it only signs me in, or deploys or pays for something I chose, and that nothing can move my tokens, NFTs or money without me approving it in my wallet.
2. Smart contracts: list every contract address and contract call in the code. Say what each one is, and flag anything unknown, unverified or suspicious.
3. Privacy: read https://virvi.io/privacy/ and check the code only collects and shares what that page says.
4. Live version: get the commit from https://api.virvi.io/api/transparency, confirm that commit is in the public repo, and do the checks above on that commit.
5. Contracts: for each contract listed there, check that its Polygonscan-verified source matches the file at its sourceUrl.

Tell me in plain language what you found, anything that looks risky, and anything you couldn't check.

Check it yourself

With Git, Docker and the GitHub CLI installed, run this from a copy of the repo:

bash scripts/verify-release.sh

It:

It prints PASS, or exactly which files differ.

What this proves, and what it can’t

What isn’t in the repo

Report a security issue

Email support@virvi.io. Please don’t post it publicly until we’ve had a chance to fix it. Our security.txt has the details.