> For the complete documentation index, see [llms.txt](https://moveflow3.gitbook.io/moveflow-token-distribution-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://moveflow3.gitbook.io/moveflow-token-distribution-protocol/contract-addresses.md).

# Contract Addresses

### Introduction

MoveFlow utilizes smart contracts deployed on various blockchains to facilitate programmable payments, including token vesting, payroll, airdrops, and subscriptions. These contracts ensure transparency, security, and automation in on-chain financial transactions.

#### Key Features:

* **Secure & Auditable**: All transactions are recorded on-chain, ensuring transparency and immutability.
* **Automated Execution**: Transactions follow predefined rules based on time and events.
* **Multi-Chain Support**: Currently deployed on Aptos and EduChain, with future plans for expansion to Solana, Ethereum, Arbitrum, and BSC.

### Contract Addresses

Below is a table listing the contract addresses for MoveFlow on different blockchain networks

| **Blockchain** | **Contract Address**                                               |
| -------------- | ------------------------------------------------------------------ |
| Aptos          | 0x15a5484b9f8369dd3d60c43e4530e7c1bb82eef041bf4cf8a2090399bebde5d4 |
| EDU Chain      | 0x408BDA1fe3Ed15Dc6b06a00055a2894e5D79369E                         |

Please ensure that you are interacting with the correct contract addresses to avoid any security risks. Always verify the addresses from official sources before making transactions.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://moveflow3.gitbook.io/moveflow-token-distribution-protocol/contract-addresses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.