> For the complete documentation index, see [llms.txt](https://docs.cyberbrokers.com/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cyberbrokers.com/user-guide/missions/alpha/qa-m02/rewards.md).

# Rewards

Now on to what you’ve been waiting and working hard for. The reward for solving Quest#2 is an airdrop of a coveted Mech Engine Blueprint.

<figure><img src="/files/CyyhDt16zcP5eTd8YlL4" alt=""><figcaption></figcaption></figure>

This is a well-earned gift for helping Ken, Spice, and Zinc get the message out to the citizens of the Paradigm. The information on distribution and reward tiers is below.

**Airdrop Details**

***Important Security Notice:** Quest #2 airdrop’s contract address is: 0xf4bacb2375654ef2459f427c8c6cf34573f75154. Never claim any airdrops from us or click on any links unless they are posted directly in our Announcements channel in*[ *Discord*](http://discord.gg/josie)*. We will never DM you with a link for a claim. The airdrop for the Mech Engine Blueprints is completely free and automatic. You do not need to do anything to receive your airdrop.*

All CyberBroker and Lupis Mech Arm holders will receive a number of airdrops from a pool of five different Mech Engine Blueprints, which is currently targeted for Wednesday (5/18) depending on market and chain activity.

On May 15th at the conclusion of Quest #2, we took a snapshot of all CyberBroker and Lupis Mech Arm holders.

* All Lupis Mech Arms will receive a Lupis Mech Engine Blueprint if they participated in Quest 2 and verified their tweet. If the wallet did not participate, they will receive Enforcer Mech Engine Blueprints instead.
* Any wallet that connected, contained at least one CyberBroker, participated in solving the Quest, and verified their tweet in the Power Eleven Terminal is eligible under the **Participation Drops** table.
* Any wallet that held a CyberBroker at the Quest's conclusion that did not participate in the Quest will be eligible under the **Non-Participation Drops** table.

**Reward Tiers**

The number of airdrops and the rarity of the airdrop you receive depends on if you participated and how many CyberBrokers your wallet holds.

<figure><img src="/files/gO0Qf4zPcGVbkPMfZiam" alt=""><figcaption></figcaption></figure>

Examples:

* If you hold 6 CyberBrokers, you will receive the drops indicated on line 6.
* If you own 24 CyberBrokers, you will get the line 10 rewards 2x and line 4 rewards.

### **Build a Mech!**

Mechs are one of the top ways to navigate TPLs hectic airways and protect your Broker from being d’mezzed. You can build a mech from scratch by collecting salvageable parts over time to be assembled at the end of Season 1. Be sure to follow future Quests for the opportunity to earn the highest quality collector model parts.

Your custom-built mech will be used to aid you in solving future Quests. Remember, mechs need operators and can not be used by themselves.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cyberbrokers.com/user-guide/missions/alpha/qa-m02/rewards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
