> For the complete documentation index, see [llms.txt](https://spark-ibc.gitbook.io/interchain-info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spark-ibc.gitbook.io/interchain-info/transparency-info-or-revenue-funding-investors-etc.md).

# Transparency Info | Revenue, Funding, Investors, etc

> ℹ️ At [**Spark IBC**](https://sparkibc.zone) **(**[**docs**](https://spark-ibc.gitbook.io/spark-ibc/)**)**, the team behind ICI, we've chosen to reject all investment proposals, upholding our commitment to impartiality. We believe in being accountable ***only*** to our community and the projects that choose to collaborate with us. We're entirely funded through grants, community pool funds, and public revenue channels, ensuring our dedication remains towards the community.

### ICI Public funding to date

ICI has ***only*** raised funds through public sources, which are listed here.\
All additional expenditures have come out of the founders personal pockets, and thus, are not listed publicly.

| Source                            | Information                                                                                                       | Amount                                                                   |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| ICI's Spark IBC campaign          | Charitable donations from the community & organizations. One of which is the cosmos hub community.                | Can be seen live [here](https://sparkibc.zone/earn),                     |
| Cosmos Hub Community Pool Funding | Half was used internally for general ICI development, and half for content creation and incentivization.          | \~1,438 $ATOM, worth around $20k during the time of proposal submission. |
| Atom Accelerator DAO AEZ Grant    | The AADAO granted us funds to build out a dedicated AEZ portal page, alongside updates to ICI that compliment it. | $34,000 worth of $ATOM, split into two payments.                         |
| DoraHacks Quadratic Funding       | Comprised of both ATOM donations from users and community memebers, as well as some amount matched by DoraHacks.  | TBD                                                                      |

### Traditional revenue streams

ICI's longterm sustainability will come from time-tested traditional revenue streams, not risky tokenomics and/or DeFi. This includes things like verification for projects, which benefits the end-users as well, in addition to standard web2 things like add placements and search priority.\
\
Read more details [here](/interchain-info/premium-services.md).

{% content-ref url="/pages/fBGQLnmGThMfW85D6nKg" %}
[Premium Services](/interchain-info/premium-services.md)
{% endcontent-ref %}

### Get in touch!

<contact@interchaininfo.zone>


---

# 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://spark-ibc.gitbook.io/interchain-info/transparency-info-or-revenue-funding-investors-etc.md?ask=<question>&goal=<user_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.