> For the complete documentation index, see [llms.txt](https://docs.lazarusbounty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lazarusbounty.com/rewards-and-participation.md).

# Rewards & Participation

Bybit offers a bounty amounting up-to 10% of stolen funds that have been returned to Bybit ("**Returned Funds**") to participants in this programme that rewards participants for tracking, freezing and returning funds ("**Bounty**").

Distributions are made as follows:

1. **5%** to the entity that assists in freezing the funds. Freezing shall be the first durable and acting freeze at the time of the funds return to qualify.
2. **5%** to the first reporters who helped trace the funds up to the stage of successful freezing.
3. A participant may fufill both roles.

**Bounty Payment Terms**

1. Bounties will be paid for the respective appliable participation in Returned Funds.
2. Bounties will be paid porportinate to the amount of Returned Funds and out of the Returned Funds.
3. Payouts will be made directly to the contributor's wallet address within 1-2 weeks.
4. Bounty payouts are not automatic and will be done on request.
5. Each request is audited and verified.

### **How to Join**

Take action to safeguard the crypto industry—submit a report and contribute to the fight against cybercrime.

{% embed url="<https://www.lazarusbounty.com/en>" %}

## **Disclaimer**

Participation does not guarantee a bounty award. Admission on the leaderboard does not represent a qualified Bounty. Bybit reserves the right to modify or terminate this program at its discretion. All participants must comply with applicable laws and regulations. Fraudulent or misleading claims will result in disqualification.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lazarusbounty.com/rewards-and-participation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.