> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/previous-funds/fund13-docs/project-onboarding/funded-proposers-guides/test-transaction-tx.md).

# Test Transaction (Tx)

Test Tx confirmation is part of your onboarding process. You can confirm Test Tx once Formal Due Diligence process is completed. The goal of it is to make sure that FP receives funds in the correct wallet. The test Tx is made in the following way:

1. Catalyst sends 1 ADA to the wallet provided in the onboarding form (IMPORTANT: The wallet address you provide in the onboarding form is the wallet address that will be used for the test transaction, If for any reason the wallet address needs to be changed from the one submitted in the onboarding form this will delay your onboarding and initial fund release).
2. Catalyst sends an email with Google form where FP confirms obtaining of 1 ADA


---

# 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.projectcatalyst.io/previous-funds/fund13-docs/project-onboarding/funded-proposers-guides/test-transaction-tx.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.