Decentralized Security, Community-Powered Recon

Bounty Overview Rewards by Severity Assets in Scope In-scope Vulnerabilities Out-of-scope Vulnerabilities Program Rules FAQs

Ownership Coin

Yield Farming

NFT

Max Payout

$50,000

Project Overview

Ownership Coin is dedicated to upholding the highest standards of security and transparency within its ecosystem. Central to this commitment is an active Bug Bounty Program that invites ethical hackers and security researchers worldwide to help identify and remediate vulnerabilities. By fostering collaboration with the global security community, Ownership Coin ensures the integrity and resilience of its platform.

Rewards by Severity

Program Overview The Ownership Coin Bug Bounty Program is a proactive initiative to strengthen the security and integrity of the Ownership Coin ecosystem. The team welcomes ethical hackers, security researchers, and developers to identify and disclose vulnerabilities—particularly within its smart contracts, including the Jetton Master Smart Contract(https://tonviewer.com/EQC5Dj4AfQaDl40ex6E0WyUDdMBJHbqTXnxNkn8HuQZNzpZt). This initiative reflects Ownership Coin’s commitment to protecting user assets and preserving platform trust.

Reward Structure All submissions are assessed using a standardized 4-tier severity model, with distinctions based on both the impact and type of the vulnerability. For critical smart contract vulnerabilities, rewards are capped at 10% of the potential economic damage, taking into account funds at risk and other considerations such as PR or brand risk. High-severity vulnerabilities may be eligible for rewards of up to 100% of the affected funds, calculated at the time of the report’s submission.

Submission Requirements To be eligible for a reward, all reports must include a working proof of concept (PoC) and clear reproduction steps that show how the vulnerability impacts an in-scope asset. Reports without functional code or demonstrable exploitability will not be accepted.

Payouts Bug bounty rewards are denominated and paid in USDT, and are issued following successful validation by the Ownership Coin team.

Smart Contract

The bounty will be paid out in USDT

Assets In-Scope

Target

Severity

Name

https://github.com/ownershipcoin/minter-contract

Smart Contract

$OC (Jetton Token)

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 project funds other than unclaimed rewards

Direct theft of user funds other than unclaimed rewards

Permanent freezing of funds

Unauthorized mint/burn/transfer of crypto assets

Bad randomness leading to predictable results with serious financial impact

Governance voting result manipulation

Protocol insolvency

Major

Issues leading to temporary freezing of funds for a limited amount of time

Theft or permanent freezing of unclaimed yield and rewards

Temporary denial of services

Broken access control leads to high security risks

Medium

Unexpected logic executions (doesn’t lose value)

Smart contract unable to operate due to lack of funds or misconfiguration

Griefing attacks that can damage users or the protocol without profiting the attacker

Block stuffing for profit

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)

Not following best practices

with no security risk

Centralization risks

Issues with no security or financial impact

Incorrect data supplied by third party oracles - Not to exclude oracle manipulation/flash loan attacks

Lack of liquidity

Best practice critiques

Sybil attacks

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 SinceOct 25, 2024

Last Updated2mo 20d ago

Funds Reserved$100,000

Max Payout$50,000

Skynet Score

81.46

KYC

Required

PoC

Required

View on Skynet