# Developers #### Read Only Applications Dashboards, explorers etc 1. Connect to Midgard to get rich data about the system, included time-series graphs and aggregated values like TotalVolume etc. 2. Connect to SwipeNode (or proxied via Midgard) to drill into the state-machine and access the current state (or historical just by adding a `?height=1234` to specify a certain height. 3. Connect to RPC to get information about the Ledger, which is not specific to SwipeChain, such as `/genesis` or account/transaction information #### Write Applications Wallets, interfaces etc. These applications require first-principle thinking and excellent understanding of how the system works. 1. Connect to a trusted SwipeNode or connect to several public SwipeNodes and ensure they all agree 2. Get the `/inbound_addresses` 3. Compose the transaction with the correct memo and correct gas price. 4. Send the vault the transaction and wait for execution **Connecting** First, you need to connect to SwipeChain. You can use the official clients which have SSL, or run your own node, host it on SSL. {% hint style="info" %} If you don't need SSL, you can connect to any of the non-SSL public nodes (ie, just their IP address). Web applications need SSL, but mobile and desktop apps don't. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.swipe.org/swipechain/developers.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.