> For the complete documentation index, see [llms.txt](https://maiga.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://maiga.gitbook.io/docs/incentives/boost-xp/reward-hash.md). # Reward Hash {% hint style="success" %} **To win 1 BTC, 100 BNB with total prize pool worth $1M USD, start by** [**boosting your MAIGA XP today**](https://t.me/maigaxbt_bot)**!** {% endhint %} ## What is MAIGA’s Reward Hash? Every time you boost your XP using the MaigaXBT AI agent, you’re also triggering a provably fair on-chain reward mechanism: the Reward Hash. It’s a native way to reward users onchain activities, using the raw mechanics of blockchain. No off-chain RNG, no centralized logic, just verifiable transaction hashes and pure luck. ## How the Reward Hash is generated: “Hash within Hash”

To generate these hashes, Maiga developed a verifiably fair method called "Hash within Hash", which uses Ethereum's *keccak256* hashing algorithm to combine several on-chain variables: #### Breakdown: * **tokenId** – Unique ID from the boost * **msg.sender** – Your wallet address * **block.chainid** – The current blockchain (e.g. BNB = 56) * **boostCount\[tokenId]** – Number of times the NFT has been boosted * **block.timestamp** – Timestamp of block confirmation * **blockhash(block.number)** – The actual block hash These inputs ensure every Reward Hash is: * **Unique** (boost count, sender, tokenId) * **Unpredictable** (block timestamp and hash) * **Immutable** once confirmed on-chain This makes any attempt to game the system practically impossible unless you can control the network (e.g. a 51% attack). ## Why It’s Different ### 100% On-Chain Unlike traditional raffles that rely on opaque backend logic, MAIGA’s Reward Hash system is: 1. Completely on-chain where hashes are generated during actual blockchain transactions 2. Immutable, meaning once a transaction is confirmed, the hash cannot be altered. 3. Self-verifiable - anyone can view the reward hash using blockchain explorers. ### Provably Fair Each reward hash is based on a mix of variables that cannot be predicted before your transaction is mined. 1. `Block.timestamp`: Exact time the block is mined 2. `blockhash(block.number)`: Hash of the current block These inputs are only known after the block is confirmed, making it impossible for users or developers to force a specific outcome. The only way to generate one is by executing real transactions and leaving it (your luck and trust) to the chain. **Let’s further break down how it exactly works:** A Reward Hash is a 32-byte hexadecimal string (like transaction ID) generated when a user boosts XP via the MaigaXBT AI agent. Each /boostxp action signs and submits an on-chain transaction through your MAIGA MPC wallet or your web3 wallet. This transaction hash will be used to create a reward hash and the **final 6 alphanumerics of that hash** are evaluated for reward eligibility, like this: 0xddaa624d505222c1da48831db68f8440ce478d74728a6f8255b36669316ae361 Last characters = ...361. If the ruleset rewards hash like 123, this transaction isn’t a winner. But if it ends in 123, 456, 789, abc, def, you could win up to **$100 and more**. This suffix is called your **Reward Hash**. ## Updated Reward Hash prizes


Reward Hash Lucky Draw Ending	$ USDT Prize	USD Value ($1,000/BNB)
00, 11, 22, 33, 44, 55, 66, 77, 88, 99, aa, bb, cc, dd, ee, ff	$5 USDT	$15
123, 456, 789, abc, def	$100 USDT	$150
1234, 6789, abcd	$1,000 USDT	$1,500
12345, abcde	$10,000 USDT	$15,000
123456	1 BTC	$100,000 +

{% hint style="success" %} **The more you boost, the higher your chances of hitting a winning reward hash.** {% endhint %} ## Example of actual reward hash: Alice boosted XP on the Telegram MaigaXBT and sends a transaction on-chain on BNB or opBNB mainnet. In 6 transactions, Alice managed to get an actual on-chain reward hash of **98EEAA** (see screenshot) and won a Reward Hash lucky draw prize of **0.015 BNB** (\~$15).

https://opbnb.bscscan.com/tx/0x0e7c86c27690f8d9c615479068b505b6fd581bc8f43dffc179e4170362d9ab79#eventlog

--- # 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://maiga.gitbook.io/docs/incentives/boost-xp/reward-hash.md?ask=&goal= ``` `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.