Overview
Last updated
Last updated
“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:
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.
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):
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.
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.
After the Bifrost SLPx module logic is processed, the LST will be sent to user on source chain.
