> 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/pl/szybki-start/adresy-smart-kontraktow.md).

# Adresy smart kontraktów

Kompletny wykaz adresów systemowych smart kontraktów Chiliz Chain: Staking, Governance, ChainConfig, Tokenomics, staking Fan Tokenów, Pepper oraz kontrakty LayerZero endpoint dla chain ID 88888 i 8888

Budując na Chiliz Chain, będziesz musiał zintegrować funkcjonalności dostarczane przez nasze smart kontrakty. Ta strona zawiera wszystko, czego potrzebujesz.

## Adresy kontraktów Chiliz Chain

{% hint style="info" %}
Adresy są takie same zarówno dla Chiliz Chain Mainnet, jak i dla Spicy Testnet.
{% endhint %}

{% hint style="warning" %}
Upewnij się, że zawsze używasz właściwego Chain ID w swoim kodzie:

* Chiliz Chain Mainnet: `88888`
* Spicy Testnet: `88882`
  {% endhint %}

| Kontrakt                                                               | Adres kontraktu                            |
| ---------------------------------------------------------------------- | ------------------------------------------ |
| Staking                                                                | 0x0000000000000000000000000000000000001000 |
| Slashing Indicator                                                     | 0x0000000000000000000000000000000000001001 |
| SystemReward                                                           | 0x0000000000000000000000000000000000001002 |
| StakingPool (wrapper Stakingu, używany przez użytkowników, dApps itp.) | 0x0000000000000000000000000000000000007001 |
| Governance                                                             | 0x0000000000000000000000000000000000007002 |
| ChainConfig                                                            | 0x0000000000000000000000000000000000007003 |
| RuntimeUpgrade                                                         | 0x0000000000000000000000000000000000007004 |
| DeployerProxy                                                          | 0x0000000000000000000000000000000000007005 |
| Tokenomics                                                             | 0x0000000000000000000000000000000000007006 |
| <p>Multicall<br><em>(tylko Mainnet)</em></p>                           | 0x0E6a1Df694c4be9BFFC4D76f2B936bB1A1df7fAC |

Ponadto zespoły [Kayen Finance](https://www.kayen.finance/) i [FanX](https://app.fanx.xyz/) stworzyły dedykowane kontrakty do pracy z ich DEX:

{% embed url="<https://kayen-finance.gitbook.io/docs/contracts/contracts>" %}

{% embed url="<https://fanx.gitbook.io/fanx-docs/contract/contracts>" %}

## Adresy kontraktów Fan Tokenów

### Lista Fan Tokenów

Pełną listę tokenów znajdziesz na tej stronie:

{% content-ref url="/pages/8MXJeZIURce27Kq8nNci" %}
[Adresy kontraktów tokenów](/pl/szybki-start/adresy-kontraktow-tokenow.md)
{% endcontent-ref %}

### Kontrakty stakingu Fan Tokenów

Do stakingu Fan Tokenów możesz użyć tych adresów na Chiliz Chain Mainnet:

| Kontrakt       | Adres kontraktu                            |
| -------------- | ------------------------------------------ |
| Proxy          | 0x5ff7f9724fd477d9a07dcdb894d0ca7f8fae1501 |
| Implementation | 0xD1bAfa7A246f5685cd22A563FD20fb164fAF0A4c |

## Adresy kontraktów Pepper

[Token społecznościowy $PEPPER](https://www.peppercoin.com/) posiada własny zestaw adresów na Chiliz Chain Mainnet:

| Kontrakt       | Adres kontraktu                            |
| -------------- | ------------------------------------------ |
| Pepper Factory | 0xb06709919e0279fC7e01bfBc4Cead2dD99F74Ca8 |
| Pepper Staking | 0x5cA4C88339D89B2547a001003Cca84F62F557A72 |

## Adresy kontraktów LayerZero

Chiliz Chain implementuje [protokół LayerZero](https://layerzero.network/), aby Fan Tokeny były omnichain.

{% tabs %}
{% tab title="Chiliz Chain Mainnet" %}
Layer Zero Endpoint ID (`eid`) dla Chiliz Chain Mainnet: `30409`.

| Kontrakt                                                       | Adres kontraktu                            |
| -------------------------------------------------------------- | ------------------------------------------ |
| EndpointV2                                                     | 0x6F475642a6e85809B1c36Fa62763669b1b48DD5B |
| sendUln302                                                     | 0xC39161c743D0307EB9BCc9FEF03eeb9Dc4802de7 |
| receiveUln302                                                  | 0xe1844c5D63a9543023008D332Bd3d2e6f1FE1043 |
| <p>blockedMessageLib<br><em>(Blocked Message Library)</em></p> | 0xc1ce56b2099ca68720592583c7984cab4b6d7e7a |
| executor                                                       | 0x4208D6E27538189bB48E603D6123A94b8Abe0A0b |
| Dead DVN                                                       | 0x6788f52439ACA6BFF597d3eeC2DC9a44B8FEE842 |
| {% endtab %}                                                   |                                            |

{% tab title="Spicy Testnet" %}
Layer Zero Endpoint ID (`eid`) dla Spicy Testnet: `40440`.

| Kontrakt                                            | Adres kontraktu                            |
| --------------------------------------------------- | ------------------------------------------ |
| EndpointV2                                          | 0x3aCAAf60502791D199a5a5F0B173D78229eBFe32 |
| sendUln302                                          | 0x45841dd1ca50265Da7614fC43A361e526c0e6160 |
| receiveUln302                                       | 0xd682ECF100f6F4284138AA925348633B0611Ae21 |
| <p>blockedMessageLib<br>Blocked Message Library</p> | 0xa229b65cc2191bf60bc24efcda3487d7b5c0c9f0 |
| executor                                            | 0x701f3927871EfcEa1235dB722f9E608aE120d243 |
| {% endtab %}                                        |                                            |
| {% endtabs %}                                       |                                            |

Możesz zweryfikować te informacje w dokumentacji LayerZero:

{% embed url="<https://docs.layerzero.network/v2/deployments/chains/chiliz>" %}

{% embed url="<https://docs.layerzero.network/v2/deployments/deployed-contracts?chains=chiliz>" %}

Zespół LayerZero udostępnia też szybki przewodnik po mintowaniu i transferze Omnichain Fungible Token (OFT) między Chiliz Mainnet a dowolną inną obsługiwaną siecią:

{% embed url="<https://docs.layerzero.network/v2/deployments/evm-chains/chiliz-mainnet-oft-quickstart>" %}


---

# 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/pl/szybki-start/adresy-smart-kontraktow.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.