CertiK LogoCertiK Logo
Bounty OverviewRewards by SeverityAssets in ScopeIn-scope VulnerabilitiesOut-of-scope VulnerabilitiesProgram RulesFAQs
Portkey Wallet logo
Portkey Wallet
Wallet
Payment
Web3
Max Payout
$10,000
Project Overview

Portkey is an Account Abstraction (AA) wallet within the aelf ecosystem, designed to onboard users, developers, and projects from Web2 to Web3 through an intuitive DID-based login system. Users can access their wallets via familiar Web2 social credentials—without private keys or mnemonics—while benefiting from social recovery and a decentralized guardian model that protects assets from centralized control. Portkey also features a payment delegation mechanism, enabling third parties to sponsor user activity fees, including free account creation and broader fee coverage, lowering barriers to Web3 adoption.

Rewards by Severity

Program Overview Portkey Wallet maintains a bug bounty program to identify and resolve potential security vulnerabilities within its wallet infrastructure and associated smart contracts. The program encourages responsible disclosure from security researchers to strengthen platform security and protect user assets.

Reward Structure The program follows a 4-tier severity model, with rewards based on the impact and criticality of the vulnerability. For critical vulnerabilities, rewards are capped at 10% of the potential economic damage, taking into account the funds affected as well as public relations and brand impact, at the discretion of the Portkey Wallet team. High-severity vulnerabilities may receive rewards of up to 100% of the affected funds. All risk assessments are based on on-chain and system conditions at the time the bug is reported.

Submission Requirements Bug reports must contain a clear and technically sound description of the vulnerability along with reproducible steps. While a proof of concept (PoC) is not required, reports must convincingly demonstrate how the issue affects an in-scope asset. Submissions that fail to prove impact will not be eligible for rewards.

Payouts Bounties are denominated in USD and paid out in USDT, processed by the Portkey Wallet team upon successful report validation and KYC completion.

Application/Web
The bounty will be paid out in USDT
Assets In-Scope
Target
Severity
Name
https://github.com/Portkey-Wallet
Web Application
Portkey Wallet
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.
Application/Web
Critical
Non-intuitive return values
Important gas optimizations
Smart contract functionality significantly differs from how it is described in its official repo
Smart contract fails to deliver promised returns - but doesn’t lose value
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
XXE/XML injection vulnerability with high-security impact
Authentication and authorization bypass with high impact
Wormable stored XSS
Large scale account takeover
Leakage of a lot of source code
Medium
Account takeover
Stored XSS on general pages
CSRF involving core business
IDOR with medium security impact/Horizontal and Vertical Privilege Escalation
The leakage of locally-stored sensitive authentication key information
Medium impact information disclose
Low
General information leakage - such as web path traversal - system path traversal - directory browsing etc
Reflected XSS - DOM XSS and Flash-based XSS
SMS bombs - mail bombs (each system only accepts one type of this vulnerability)
No return value and no in-depth utilization of successful SSRF
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
Any activity that could lead to the disruption of our service (DoS)
Missing best practices in SSL/TLS configuration
Previously known vulnerable libraries without a working Proof of Concept
Issues that require unlikely user interaction
Unconfirmed reports from automated vulnerability scanners
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 Scope1
Live SinceJan 30, 2024
Last Updated2mo 22d ago
Funds Reserved$10,000
Max Payout$10,000
Skynet Score
86.05
A
KYC
Required
PoC
Not Required
View on Skynet