Skip to main content

Smart contract audit

Learn what a smart contract audit is, why we are scheduling it closer to public launch, and what the audit will cover.

Written by VPR
Updated over a week ago

A smart contract audit is an independent security review of the on-chain code that manages NFTs and related on-chain rules. In VPR, the goal of an audit is to validate that the contract behaves exactly as described, and to reduce security risks before broad public exposure.

Current phase (Q1-2026)

We are currently in a private pre-launch phase limited to a small group of selected participants. NFTs are minted using managed infrastructure through our partner Venly.

The smart contract:

  • Enforces fixed supply

  • Does not custody user funds

  • Does not include staking or token mechanics

  • Does not contain complex on-chain gameplay logic

Because this is a small, controlled release using established infrastructure, a full third-party audit has not yet been commissioned.

Prior to any public mint expansion or introduction of additional on-chain mechanics, we will complete an independent smart contract audit and publish the results.

This phased approach allows us to validate the platform responsibly before scaling.

Audit commitment and timing

A smart contract audit delivers the most confidence when it reviews the locked, launch-ready code. That is why we will complete an independent audit and share the results publicly before the full public launch.

The audit will review, at minimum:

  • Contract security and common vulnerability classes

  • Supply limits (including the Generation 1 cap)

  • Confirmation that there are no hidden administrative controls or backdoors

  • Verification that core NFT rules match published claims (minting rules, immutability rules, permissions model)

Until a third-party audit is completed, we rely on established standards and infrastructure (ERC-1155 on Polygon via Venly) and a controlled release approach, and we will publish audit results before scaling to a full public launch.

Did this answer your question?