> For the complete documentation index, see [llms.txt](https://docs.mayaprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mayaprotocol.com/mayachain-dev-docs/examples/tutorials.md). # Tutorials Example actions within MAYAChain ### Find Savers Position Endpoints have been made to look up a savers position quickly. ### **Savers Position using Thornode** **Request**: *Get BTC saver information for the address 33XBYjiR3B7g8755mCB56aHtxQYL2Go9xf* **Response:** ```json { "asset": "BTC.BTC", "asset_address": "33XBYjiR3B7g8755mCB56aHtxQYL2Go9xf", "last_add_height": 8794877, "units": "71338", "asset_deposit_value": "71723", "asset_redeem_value": "71830", "growth_pct": "0.001491850591860352" } ``` Returns all savers for a given asset. To get all savers you can use ### **Savers Position using Midgard** **Request** *Get Savers Position for address 33XBYjiR3B7g8755mCB56aHtxQYL2Go9xf* **Response:** ```json { "pools": [ { "assetAddress": "33XBYjiR3B7g8755mCB56aHtxQYL2Go9xf", "assetBalance": "71723", "assetWithdrawn": "0", "dateFirstAdded": "1671838673", "dateLastAdded": "1671838673", "pool": "BTC.BTC", "saverUnits": "71338" } ] } ``` **Find Liquidity Position** Similar to savers, looking up the liquidity position with a given address is possible. ### **Liquidity Provider Position using Thornode** **Request**: *Get liquidity provider information in the BTC pool for the address* bc1q00nrswtpp3zddgc0uvppuszhnr8k8zfcdps9gn **Response:** ```json { "asset": "BTC.BTC", "asset_address": "bc1q00nrswtpp3zddgc0uvppuszhnr8k8zfcdps9gn", "last_add_height": 6332320, "units": "3190637579", "pending_rune": "0", "pending_asset": "0", "rune_deposit_value": "5340160943", "asset_deposit_value": "548543", "rune_redeem_value": "6217698938", "asset_redeem_value": "500382", "luvi_deposit_value": "1696309", "luvi_redeem_value": "1748188", "luvi_growth_pct": "0.030583460914255598" } ``` ### **Liquidity Provider Position using Midgard** Several endpoints exist however the member's endpoint is the most comprehensive **Request**: Get *liquidity provider information for the address* bc1q0kmdagyqhkzw4sgs7f0vycxw7jhexw0rl9x9as **Response:** ```json { "pools": [ { "assetAdded": "67500000", "assetAddress": "bc1qw5cj49wng7jpfg2zq6ca5py7uctq4maulyc66c", "assetPending": "0", "assetWithdrawn": "0", "dateFirstAdded": "1669373649", "dateLastAdded": "1669373649", "liquidityUnits": "466600725237", "pool": "BTC.BTC", "runeAdded": "955003804620", "runeAddress": "thor169lfsnv2myg8yrudx4353xakq44756w9830crc", "runePending": "0", "runeWithdrawn": "0" } ... ] } ``` Any address can be used with this endpoint, e.g. bc1q0kmdagyqhkzw4sgs7f0vycxw7jhexw0rl9x9as with `?showSavers=true` to show any savers position also. **User Transaction History** Actions within THORChain can be obtained from Midgard which will list the actions taken by any given address. **Request**: *List actions by the address bnb1hsmrred449qcmhg9sa42deejr8nurwsqgu9ga4* **Response:** ```json { "actions": [ { "date": "1647866221415353933", "height": "4778782", "in": [ { "address": "thor169lfsnv2myg8yrudx4353xakq44756w9830crc", "coins": [ { "amount": "63684757953", "asset": "THOR.RUNE" } ], "txID": "ED1384012BA129B889CCF3285A1FB73B127101A0924F49B64FE58A6939FA47C4" }, { "address": "bnb1hsmrred449qcmhg9sa42deejr8nurwsqgu9ga4", "coins": [ { "amount": "541348102046", "asset": "BNB.BUSD-BD1" } ], "txID": "F8CEAF2EA762D08AE22CC173BC4B2781B082927990C4F623D2629C4EE2BEC93F" } ], "metadata": { "addLiquidity": { "liquidityUnits": "38152218105" } }, "out": [], "pools": [ "BNB.BUSD-BD1" ], "status": "success", "type": "addLiquidity" }, .... ], "count": "6" } ``` Will also include savers' actions. The Action endpoint is very flexible, see the [docs](https://midgard.ninerealms.com/v2/doc#operation/GetActions). ### Check the status of a Transaction Transactions can[ take time to fully process](https://gitlab.com/mayachain/docs/one-stop-shop/-/blob/main/mayachain-dev-docs/examples/broken-reference/README.md) once sent to THORChain. **Request**: Get the status for BTC tx A56B423250020E4960D9836C6F843E1D3333FAE583C9CA26776F0D68DA69CE4A sent to the Savers vault. **Response**: ```json { "tx": { "id": "A56B423250020E4960D9836C6F843E1D3333FAE583C9CA26776F0D68DA69CE4A", "chain": "BTC", "from_address": "bc1qmlw9x4xnkmyd5xgtvn5cuwc5jcq033g4cj2ur9", "to_address": "bc1q02hrv5y4dm7rux2swg020yzykhaufrglyv7kkj", "coins": [ { "asset": "BTC.BTC", "amount": "30051812" } ], "gas": [ { "asset": "BTC.BTC", "amount": "2500" } ], "memo": "+:BTC/BTC:t:0" }, "stages": { "inbound_observed": { "completed": true }, "inbound_finalised": { "completed": true } } } ``` Note this endpoint is in alpha and the response will differ for swaps. For more details information, can be used looking for `updated_vault` --- # 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.mayaprotocol.com/mayachain-dev-docs/examples/tutorials.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.