> 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/proposal-templates/salp.md). # SALP ### **TL:DR** \[SAMPLE NETWORK] plans to participate in \[*POLKADOT OR KUSAMA*] Crowdloan via Bifrost SALP. ### **Network Information:** Brief description of Network such as “\[SAMPLE NETWORK] is a an scalable, non-custodial decentralized cross-chain liquidity staking specialized parachain (Omnichain LSD Layer1) built on Polkadot, currently supporting liquidity derivatives on over 9+ blockchains.” * Website: \[PARACHAIN WEBSITE] * Twitter: \[PARACHAIN TWITTER] * Discord: \[PARACHAIN DISCORD] * Telegram: \[PARACHAIN TELEGRAM] ### Crowdloan Information: * Relay-chain: *\[POLKADOT OR KUSAMA]* * Paraid: *\[NUMBER]* * Crowdloan Cap: *\[AMOUNT OF DOT OR KSM]* * Auction: *\[AUCTION NUMBER]* * Slot: \[FROM SLOT START PERIOD - SLOT END PERIOD] * Token: \[*TOKEN NAME*] * Reward: 1 DOT = \[AMOUNT OF *TOKEN*] \[SAMPLE NETWORK] Crowdloan reward plan: ### Statement： \[SAMPLE NETWORK] had noticed: Since Bifrost SALP is using XCM + Sovereign account for contribution, thus it is a KEYLESS account to execute contribute, which means Bifrost CANNOT do reward distribution for \[SAMPLE NETWORK]. \[SAMPLE NETWORK] will finally distribute the Crowdloan reward to contributors via Bifrost SALP contributed api: --- # 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/proposal-templates/salp.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.