Integrate RSP
Table of Contents
RSP members (with existing channel_id
) can integrate RSP through the following three options:
Option 1 - Through Bifrost SLP API
Option 3 - Through Bifrost Dapp Portal
Option 1 - Bifrost SLP API
Target Audience: Your front end can directly connect to the Bifrost (Polkadot / Kusama) parachain, such as Wallets and Dapps, etc.
Showcase 1: Staking Rewards - A PoS Data Platform

Showcase 2: Subwallet - Polkadot Wallet

Integrating Steps
Get your UI & UX ready.

Option 2 - Bifrost SLPx API (Cross-chain)
Target Audience: Blockchains that can call or deploy Bifrost SLPx across chains, such as Hydration, Moonbeam, Astar, Manta, Ethereum (coming soon), Base etc.
Integrating with EVM Contract
Showcase: Moonbeam, Astar, Manta (Omni.ls) - An omni-chain liquid staking dapp

Integrating Steps
Get your UI & UX ready.
Integrate SLPx API in your corresponding environment:
Your Dapp deployed on Ethereum Mainnet (Coming soon…)
Integrating with Parachain
Showcase: Hydration’s Treasury Minted vDOT via SLPx
Hydration democracy called Bifrost SLPx via XCM and minted 1M DOT to vDOT: https://hydration.subscan.io/referenda/138?tab=preimage
Inside of this preimage, it contained the call data to call SLPx mint for vDOT.

Integrating Steps
Construct a XCM batch call to call Bifrost-Polkadot API:
slpx_mint
Let’s assume Alice wants to mint DOT to vDOT on Hydration, a utility.batchAll call is needed:
Extrinsic Call Data, which includes several calls inside
Call 1:
Call xToken sending 1 DOT to Alice’s derived account on Bifrost.

Call 2:
Call xToken sending 0.02 BNC to Alice’s derived account on Bifrost.

Call 3:
Execute slpx_mint

FAQs:
Why do I need to send 0.02 BNC when minting/redeeming DOT?
Because after the user on Hydration sends an XCM transact with the command to Bifrost, it needs the derived address of the Hydration user to perform the SLPx mint operation, and there is no asset in the derived address, which will cause the transaction fail.
How that derived account is being calculated?
# Alice
yarn calculate-multilocation-derivative-account \\
--ws-provider wss://eu.bifrost-polkadot-rpc.liebi.com/ws \\
--address 5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY \\
--para-id 2034 \\
--parents 1
# console
Remote Origin calculated as SiblingChain
ParaID 2034
Parents 1
AccountId32: 5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY
32 byte address is 0xf959d131179b0264f98ac96d2c9c13c403129f5de93e52f3a611ccd4294d1741
20 byte address is 0xf959d131179b0264f98ac96d2c9c13c403129f5d
Option 3 - Bifrost Dapp Portal
Target Audience: Any entities need a Bifrost Dapp Portol to direct users by attached with your channel_id
.
Make sure you already have a
channel_id
Generate your Bifrost Dapp Portal
Bifrost Dapp frontend has adapted to the RSP. Attach your channel ID at the end of app.bifrost.io, for instance, https://app.bifrost.io/?channel=[channel_id]. All stakes via this link will be counted as your valid minting.
Last updated
Was this helpful?