> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/archive/funding-administration-archive/intersect-administration-services/2025-apply-for-tender/open-tenders/civics-committee/cip-149-optional-drep-compensation/considerations.md).

# Considerations

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

### Grant Structure & Payment

* **Wallet providers:** 10 grants available - 5,000 ada per eligible applicant
* **Governance tools:** 5 grants available - 5,000 ada per eligible applicant
* **SDKs:** 5 grants available - 5,000 ada per eligible applicant

### Timeline

Target for completion of implementing CIP-149 functionality: End of Q4 2025

### Payment Terms

Grants will be disbursed on a first-completed basis. Once the maximum number of grants has been fulfilled and paid out, no further funds will be available.

While funds remain, payment will be made to all applicants who:

1. Meet the technical requirements, confirmed by the Civics Committee.
2. Successfully complete KYB with Intersect Procurement Team.
3. Provide proof of completion, including a working implementation, documentation, and open-source code contributions.


---

# 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.intersectmbo.org/intersect-knowledge-base/archive/funding-administration-archive/intersect-administration-services/2025-apply-for-tender/open-tenders/civics-committee/cip-149-optional-drep-compensation/considerations.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.