> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/community/developers-events/hacking-poland-2025.md).

# Hacking Poland 2025

​Build real-world dApps, connect with the local builder scene, and compete for a chance to hack at **Parc des Princes** during [Hacking Paris 2025](https://hacking-paris.devfolio.co/).

Full details here:

{% embed url="<https://lu.ma/bf07xfmw>" %}

## Tracks

* ​​Fan Token & Wallet Integration Challenge
* ​Fan-Created Content and Monetization Platforms
* DeFi
* ​AI Agents / Tools for Sports

## Prizes

* ​**Grand Prize:** Fully-paid trip to Hacking Paris up to 4 people + $2,000 CHZ
* ​**Second Prize:** Fully-paid trip to Hacking Paris up to 4 people + $1,500 in CHZ
* ​**Third Prize:** $1,250 in CHZ

## Useful information

### About Chiliz Chain

* As a fork of BSC Chain, Chiliz Chain is EVM-compatible.
* Our Testnet is called Spicy Testnet 🌶️
* Our block explorers ->[ https://chiliscan.com](https://chiliscan.com/) and[ https://scan.chiliz.com](https://scan.chiliz.com/)
* Minimum gas price -> 2501 Gwei
* Gas limit -> Some transactions use a bit more gas since our governance contracts are a bit more complex, so if your transactions/deployments fail, always check if they are out of gas.
* Chiliz Chain is EIP 1559 compliant.
* Please use compiler version 0.8.0+commit.c7dfd78e.

### How to get some CHZ?

#### On Spicy Testnet

* Faucet ->[ https://tatum.io/faucets/chiliz](https://tatum.io/faucets/chiliz)
* Wrapped Chiliz (wCHZ) ->[ https://spicy-bridge.chiliz.com/wrap](https://spicy-bridge.chiliz.com/wrap)

#### On Chiliz Chain Mainnet:

* Bridge from Ethereum ->[ https://bridge.chiliz.com/transfer](https://bridge.chiliz.com/transfer)
* Use an exchange which is connected to Chiliz Chain
  * E.g. Binance, ChilizX
* Wrapped Chiliz (wCHZ) ->[ https://bridge.chiliz.com/wrap](https://bridge.chiliz.com/wrap)

### Available Dev Tools

#### Tools to get connected: RPCs

* Ankr
  * Mainnet:[ https://rpc.ankr.com/chiliz](https://rpc.ankr.com/chiliz)
* AllNodes
  * Mainnet:[ https://chiliz.publicnode.com/](https://chiliz.publicnode.com/)
  * Testnet:[ https://chiliz-spicy.publicnode.com](https://chiliz-spicy.publicnode.com/)
* Chiliz
  * Testnet:[ https://spicy-rpc.chiliz.com](https://spicy-rpc.chiliz.com/)

#### Tools to BUIDL:

* [Moralis](https://moralis.io/)
* [Tatum](https://tatum.io/) (only available on mainnet)
* [Thirdweb](https://thirdweb.com/)
* [WalletConnect](https://walletconnect.com/) (only available on mainnet)
* [Magic](https://magic.link/) (only available on mainnet)
* [Pyth Orcale / RNG](https://docs.pyth.network/home)
* etc.

### Resources

* [Testnet faucet](https://spicy-faucet.chiliz.com/)
* [RPCs](https://docs.chiliz.com/develop/basics/connect-to-chiliz-chain/connect-using-rpc)
* [Bridge](https://bridge.chiliz.com/transfer)
* [Tools](https://docs.chiliz.com/community/chiliz-chain-ecosystem)

### Support Groups

* [Discord](https://discord.gg/chiliz)
* [Telegram](https://t.me/BuildOnChiliz)


---

# 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.chiliz.com/community/developers-events/hacking-poland-2025.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.