> For the complete documentation index, see [llms.txt](https://docs.aozo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aozo.io/stake/developers-and-ecosystem/builder-resources/slpx-integration-reference.md).

# SLPx Integration Reference

SLPx lets an application initiate vToken minting from a supported source chain. The Bifrost module completes the liquid-staking flow and returns the resulting vToken.

### Integration model

SLPx reduces user-managed bridging, path finding, network switching, and interchain gas handling. Bifrost will become AOZO's dedicated liquid-staking sub-brand. SLPx remains a Bifrost technical integration.

### Common interface

`create_order(address,uint128,uint64,bytes,string,uint32)` creates an order. Use a 20-byte receiver for EVM or a 32-byte receiver for Substrate. Keep `remark` under 32 bytes. Use `channel_id` for Reward-Share Program attribution.

### Supported networks

| Network       | SLPx contract                                |
| ------------- | -------------------------------------------- |
| Astar         | `0xc6bf0C5C78686f1D0E2E54b97D6de6e2cEFAe9fD` |
| Manta Pacific | `0x95A4D4b345c551A9182289F9dD7A018b7Fd0f940` |
| Moonbeam      | `0xF1d4797E51a4640a76769A50b57abE7479ADd3d8` |
| Moonriver     | `0x6b0A44c64190279f7034b77c13a566E914FE5Ec4` |

Manta Pacific does not support inter-contract calls. Verify addresses, asset IDs, and network availability before deployment. Ethereum support remains unavailable.


---

# 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.aozo.io/stake/developers-and-ecosystem/builder-resources/slpx-integration-reference.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.