Skip to content

Asymetrix Protocol

By Asymetrix Bug bounty on HackenProof

Paused Lending Solidity smart contract
Top reward
$100,000
Top severity paid
Critical
Assets in scope
1
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays up to $100,000
for critical bugs.
Report on HackenProof
Submit through the program page.
Replies within 3 days
As the policy promises.
No public write-ups
Keep findings private.

Rewards

What HackenProof lists as the payout for each severity.

Severity Reward
Critical $100,000
Response
Within 3 days First Response 3d

Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

1 asset you may test, 8 excluded.

Source code 1

  • https://github.com/Asymetrix-Protocol/contracts
Out of scope (8)
  • Best practice issues
  • Code style guide violations
  • Gas optimizations
  • Old compiler version
  • Redundant code
  • The compiler version is not locked
  • Theoretical vulnerabilities without any proof or demonstration
  • Vulnerabilities in imported contracts

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Asymetrix Protocol (via HackenProof)'s policy.

While testing

  • Avoid using web application scanners for automatic vulnerability searching which generates massive traffic
  • Make every effort not to damage or restrict the availability of products, services, or infrastructure
  • Don’t access or modify other user data, localize all tests to your accounts
  • Perform testing only within the scope
  • Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
  • Don’t break any law and stay in the defined scope
  • Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
  • ONLY USE YOUR HackenProof ADDRESS (in case of violation, no bounty can be awarded)

Not accepted

  • Theoretical vulnerabilities without any proof or demonstration
  • Old compiler version
  • The compiler version is not locked
  • Vulnerabilities in imported contracts
  • Code style guide violations
  • Redundant code
  • Gas optimizations
  • Best practice issues

Summarised with AI from the program policy on HackenProof, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 21 minutes ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.

Original policy

Copied from hackenproof.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Bug bounty Triaged by HackenProof Asymetrix Protocol: Program info Asymetrix Protocol Company: Asymetrix Scope Review: 206465 Submissions: 52 Total rewards: $0 Program left: 347 days ago Finished Submit report Contest is not active Program info Hackers 24 Reports 0 Asymetrix is the decentralized, non-custodial protocol for asymmetric yields distribution generated from staking. All Scope Focus Area Program Rules Eligibility and Coordinated Disclosure Disclosure Guidelines Scope Search targets In scope Target │ Type │ Severity https://github.com/Asymetrix-Protocol/contracts Copy Web │ Critical Focus Area IN-SCOPE: SMART CONTRACT VULNERABILITIES We are looking for evidence and reasons for incorrect behavior of the smart contract, which could cause unintended functionality: Stealing or loss of funds Unauthorized transaction Transaction manipulation Attacks on logic (behavior of the code is different from the business description) Reentrancy Reordering Over and underflows OUT OF SCOPE: SMART CONTRACT VULNERABILITIES Theoretical vulnerabilities without any proof or demonstration Old compiler version The compiler version is not locked Vulnerabilities in imported contracts Code style guide violations Redundant code Gas optimizations Best practice issues Program Rules Avoid using web application scanners for automatic vulnerability searching which generates massive traffic Make every effort not to damage or restrict the availability of products, services, or infrastructure Avoid compromising any personal data, interruption, or degradation of any service Don’t access or modify other user data, localize all tests to your accounts Perform testing only within the scope Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam Don’t spam forms or account creation flows using automated scanners In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity. Don’t break any law and stay in the defined scope Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission Eligibility and Coordinated Disclosure We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward: You must be the first reporter of a vulnerability. The vulnerability must be a qualifying vulnerability Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary. You must not be a former or current employee of us or one of its contractor. ONLY USE YOUR HackenProof ADDRESS (in case of violation, no bounty can be awarded) Provide detailed but to-the point reproduction steps Disclosure Guidelines Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization No vulnerability disclosure, including partial is allowed for the moment. Please do NOT publish/discuss bugs Live since 28 Apr 2023 Published date 25 Apr 2023 Last updated 25 May 2026 Range of bounty $50 - $100,000 Severity Critical $10,000 - $100,000 High $5,000 - $10,000 Medium $1,000 - $5,000 Low $50 - $500 Lending smart contract Solidity ow @owen0x 1 Si @Sixiecow 2 @Cutiapreta KYC Verified 3 @AminBeheshti Verified 4 @Sbaudh6 KYC Verified 5 Response type Business days First Response 3d Triage Time 3d Reward Time 3d Resolution Time 14d