# COSMOS+ (v1)

(docs for <https://stake.tax> )

## **Notes**

* The COSMOS+ (v1) tab is for experimental CSVs for unlisted tokens in cosmos ecosystem.

  * Untested CSVs.  As-is tool for users. &#x20;
  * Requires blockchain node LCD endpoint.  See [LCD Endpoints](#lcd-urls) section.
  * V1 uses LCD endpoint for transaction data.
  * Generally less likelihood of complete history than v2.

* Example:

  * address: akash2lkpdc...
  * token symbol: AKT
  * node url (LCD endpoint): <https://rest-akash.ecostake.com>

## **LCD URLS**

* Examples
  * <https://stake.tax/cosmosplus>: list that StakeTax users have tried. &#x20;
    * Best bet is to usually try the node with largest OLDEST\_DATA\_IN\_DAYS\_AGO. &#x20;
  * <https://cosmos.directory/cryptoorgchain/nodes> (Nodes -> REST) : explorer for nodes
  * <https://github.com/cosmos/chain-registry> : chain registry list
    * LCD node URLs will be found in chain.json, under "rest".
    * Probably easier to use <https://cosmos.directory/cryptoorgchain/nodes>, since it draws from same data (as far as I know).&#x20;

* Endling slash (or omission) may matter:&#x20;

  * i.e. <https://myurl.com> is different than <https://myurl.com/>

* It is common for nodes to truncate history (i.e. only having the last 3 months of transactions).  The gems:gem: are when they do not truncate history.

* [What is an LCD URL?](/faq/faq.md#what-is-an-lcd-url)

## **Limits**

* &#x20;5000 most recent transactions

## Change Log

COSMOS+ (v1) changes

<https://github.com/hodgerpodger/staketaxcsv/search?o=desc&q=cosmosplus&s=committer-date&type=commits>

IBC Changes

<https://github.com/hodgerpodger/staketaxcsv/search?o=desc&q=ibc&s=committer-date&type=commits>


---

# 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.stake.tax/tokens/cosmos+-v1.md?ask=<question>
```

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.