> 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/overview.md).
# Overview
“Bifrost SLPx streamlined the complex process of bridging funds to destination chain, allowing users to liquid stake on any chain without leaving UI to interact with bridges.”
We call it:
#### SLPx Chain Abstraction
The core principle behind the model is simple: Users don't need to navigate the complexities of path-finding, cross-chain bridging, switching chains, and paying gas fees for interchain transactions. They only need to interact with the SLPx contract on their source chain to delegate these operations to be completed on their behalf.
### How does it works?
SLPx mainly consists of two parts:
* SLPx Contract: deployed on user’s source chain, receive user’s request and teleport to Bifrost.
* SLPx Module: deployed on Bifrost chain, receive the request from SLPx Contract and call to stake.
SLPx has three core steps to wrap up “Stake with Bifrost” between Bifrost chain and user’s source chain (assume a EVM chain):
1. User initiate a request on a source chain: The token is sent to a Bifrost chain account for asset transfer and processing. Each EVM address corresponds to a Substrate account. For conversion details, see the [Frontier Account Mapping Rules](https://github.com/paritytech/frontier/blob/master/frame/evm/src/lib.rs#L669).
2. Execute the Bifrost SLPx module remotely. The EVM user's address (`msg.sender`) is embedded in the calldata for the remote execution. This allows the Bifrost chain to identify the calling EVM user when the module is executed.
3. After the Bifrost SLPx module logic is processed, the LST will be sent to user on source chain.
---
# 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/overview.md?ask=&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.
