CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Vameon logo
Vameon
Gaming
GameFi
NFT
Max Payout
$10,000
Project Overview

Vameon’s Empire of Vampire is a 3D AAA Action-RPG/PvP game built on BNB Chain, where players start as low-level vampires and progress through expansive maps to become Count Dracula. Featuring intuitive mechanics and a Play-to-Earn NFT metaverse, players earn NFTs, character skins, and cryptocurrency rewards through immersive gameplay. Currently in beta, the game is available on Google Play and the App Store with over 2 million downloads.

Vameon integrates blockchain, NFTs, and gaming to create a seamless ecosystem where users can mint free NFT characters, build their value via in-game progress, and earn crypto rewards. Positioned at the crossroads of traditional gaming and Web3 technology, Vameon leverages this synergy to drive innovation and adoption in the evolving digital entertainment landscape.

Rewards by Severity

Program Overview Vameon maintains a bug bounty program aimed at reinforcing the security of its smart contracts and supporting infrastructure. By encouraging responsible disclosure of vulnerabilities, the program helps protect users, assets, and the long-term stability of the Vameon ecosystem.

Reward Structure All bug submissions are evaluated using a 4-tier severity model, with rewards varying based on the criticality of the vulnerability and the type of system affected—whether smart contracts, backend APIs, or frontend interfaces. Higher severity findings that pose greater financial or operational risk are eligible for higher-tier payouts.

Submission Requirements To qualify for a reward, bug reports must include a valid proof of concept (PoC) along with detailed steps to reproduce the vulnerability. The report must clearly demonstrate the issue’s impact on an in-scope asset. Submissions that only provide written descriptions or theoretical claims, without supporting code, will not be considered.

Payouts Bounties are denominated in USD and paid in USDT, processed by the Vameon team after successful report validation and KYC compliance.

Smart Contract
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
https://github.com/vameon/von-smart-contract
Smart Contract
VON Smart Contract
In-Scope Vulnerabilities
Only the following impacts are accepted within this bug bounty program. All other impacts are not considered in-scope, even if they affect something in the assets in scope table.
Smart Contract
Critical
Direct theft of any user funds - whether at-rest or in-motion - other than unclaimed yield
Unauthorized mint/burn/transfer of assets
Major
Access control is bypassed - including privilege escalation
Medium
Unexpected logic executions (doesn’t lose value)
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Weak random sources
Low
Smart contract functionality significantly differs from how it is described in its official repo
Missing events for functions that change critical parameters
Out-Of-Scope Vulnerabilities
The following vulnerabilities are excluded from the rewards for this bug bounty program:
  • Vulnerabilities that have already been exploited
  • Centralization-related vulnerabilities related to: private keys, privileged addresses, governance, credentials, etc.
Smart Contract
Basic economic governance attacks (e.g. 51% attack)
Program Rules
  • Please provide detailed reports with reproducible steps. If the report is not detailed enough to reproduce the issue - the issue will not be eligible for a reward., Submit one vulnerability per report - unless you need to chain vulnerabilities to provide impact., When duplicates occur we only award the first report that was received (provided that it can be fully reproduced)., Multiple vulnerabilities caused by one underlying issue will be awarded one bounty., Make a good faith effort to avoid privacy violations - destruction of data - and interruption or degradation of our service. Only interact with accounts you own or with explicit permission of the account holder., Do not attempt to conduct post-exploitation including modification or destruction of data - and interruption or degradation of services., Do not attempt to perform brute-force attacks or denial-of-service attacks., Do not attempt to target employees or customers including social engineering attacks - phishing attacks or physical attacks.
The following activities are prohibited by this bug bounty program:
  • Any testing with mainnet or public testnet contracts
  • all testing should be done on private testnets., Automated testing of services that generate significant amounts of traffic., Public disclosure of an unpatched vulnerability in an embargoed bounty., Social engineering (e.g. phishing
  • vishing
  • smishing) of any kind.
FAQs
How do I search for active bounties?
A: Active bounties can be viewed here [CertiK URL], and by filtering for bounties on the Security Leaderboard. Projects will post bounties along with the assets in the scope of the bounties with a corresponding bounty reward.
How do I submit a bounty?
To submit a bug report, first register an account with us https://www.certik.com/auth/signup. Once your account is created, you can log in and select “Submit Bug” for the specific bounties you're interested in. You will be prompted to fill out a webform; follow the instructions and upon successful submission, you will receive an email confirmation with a reference ID.
Who do I contact if I'm having trouble with my bug report submission?
You can reach out to bugbounty@certik.com for updates and assistance with your bug bounty submission.
I submitted my bug report. What now?
Once your bug report is submitted, CertiK will evaluate the report and contact the respective project. Depending on the criteria stated within a bug bounty, a KYC may be required. With valid bug reports, you will be contacted to begin the process of evaluating the bug with the project.
How is KYC handled?
CertiK has a team of investigative professionals that will handle any needed KYC services for bug bounty submissions requiring KYC.
Why was my bug report submission rejected?
A description of dismissal will be available for any bug bounty that is rejected.
The project is being slow responding to my bug report. What are their required response times / SLAs?
There can be multiple bug bounty submissions therefore there might be some delay in process times.
How do payouts work?
Payments for successful bug bounties will be communicated directly via the project wherein wallet information can be exchanged.
Bounty Highlights
Assets in Scope1
Live SinceJul 4, 2024
Last Updated2mo 22d ago
Funds Reserved$50,000
Max Payout$10,000
Skynet Score
87.94
AA
KYC
Required
PoC
Required
View on Skynet