> For the complete documentation index, see [llms.txt](https://docs.bsc.lista.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsc.lista.org/introduction/rwa-markets/slisxaue.md). # slisXAUE slisXAUE is a yield-bearing gold token issued by Lista DAO in partnership with XAUE Protocol, it is obtained by depositing XAUT on Lista DAO. slisXAUE carries a native yield of roughly 3% APR. ### slisXAUE Gold Campaign Phase 1 For 60 days starting from August 10th 2026, users can deposit to be one of the top 10 addresses by time-weighted average holding to each independently earn an additional 5% APY (up to 8% APY) on top of slisXAUE's native yield. Per-address rewards are capped at $1,000 XAUT. The baseline for participation is 20 slisXAUE, held on average across the full 60-day campaign. THe average is calculated using a time-weighted average: every address gets a daily snapshot (at a random, undisclosed time), and your qualifying holding is the average across all 60 days. Reward = (your average holding, converted to USD at settlement-day price) × 5% × (60 / 365) \*capped at $1,000 XAUT per address. Total exposure across all 10 spots is hard-capped at $10,000 XAUT. If there’s a tie for the 10th spot, users that are tied will get an equal split of whatever budget remains after the non-tied addresses are paid. --- # 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.bsc.lista.org/introduction/rwa-markets/slisxaue.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.