CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Valinity logo
Valinity
DeFi
Max Payout
$5,000
Project Overview

Valinity embodies the principles of Decentralized Finance by enabling every participant to directly earn from token sales, reverse staking, peer-to-peer fees, and transfer fees. By bridging the gap between developers and users, Valinity elevates the crypto and blockchain experience, introducing novel concepts such as Floor Price representing Yield Rate to redefine value generation within its ecosystem.

Rewards by Severity

Program Overview Valinity operates a bug bounty program aimed at reinforcing the security of its smart contracts and platform infrastructure. This program encourages responsible disclosure from ethical hackers and researchers to proactively identify vulnerabilities that could affect users, protocol functionality, or overall system integrity.

Reward Structure All submissions are assessed using a 4-tier severity model, with reward amounts determined by the criticality of the vulnerability and the type of asset impacted. Vulnerabilities that present significant financial or operational risk qualify for higher-tier rewards, subject to internal review and classification by the Valinity team.

Submission Requirements To qualify for a reward, all bug reports must include a complete and working proof of concept (PoC) as well as step-by-step reproduction instructions. The submission must demonstrate clear impact on an in-scope asset. Reports that lack executable code or do not establish real-world impact will not be considered for rewards.

Payouts All bounty rewards are denominated in USD-equivalent value and paid in VA, the native token of Valinity. Payouts are handled directly by the Valinity team following successful report validation and KYC approval.

Smart Contract
Application/Web
The bounty will be paid out in VA
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
Freezing or shutdown of systems
Major price manipulation (>=50)
Unauthorized mint/burn/transfer of assets
Permanent denial of services
Double spending
Protocol insolvency
Major
Minor price manipulation
Temporary denial of services
Temporary freezing of funds for any amount of time
Access control is bypassed - including privilege escalation
Medium
Unexpected logic executions (doesn’t lose value)
Users could lose funds due to rounding
Griefing (e.g. no profit motive for an attacker but damage to the users or the protocol)
Low
Important gas optimizations
Missing events for functions that change critical parameters
Application/Web
Critical
Important gas optimizations
Missing events for functions that change critical parameters
Major
Remote code execution and code injection
SQL injection
Obtaining high-impact sensitive information from the internal system
Authentication and authorization bypass with high impact
Large scale account takeover
Medium
Account takeover
Low
Other vulnerabilities with low-security impact
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.
Application/Web
Email Spoofing - SPF/DMARC Records Misconfiguration
Clickjacking
Previously known vulnerable libraries without a working Proof of Concept
Reports exploiting the behavior of - or vulnerabilities in - outdated browsers
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions - Login/Logout CSRF
Non-Sensitive Data Disclosure - for example server version banners
CSV/formula injection
Self-XSS with no security impact
CORS misconfiguration with no security impact
Missing HttpOnly or Secure flags on cookies
Presence of autocomplete attribute on web forms
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 Scope6
Live SinceOct 13, 2022
Last Updated4mo 28d ago
Funds Reserved$100,000
Max Payout$5,000
Skynet Score
86.32
A
KYC
Required
PoC
Required
View on Skynet