> 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/use-case.md).

# Use Case

MoveFlow is designed to support a variety of token distribution use cases, enhancing efficiency and security in financial operations:

### Token Vesting

Token vesting is a crucial component of token economies, ensuring that team members, investors, and stakeholders receive their allocations over time rather than in lump sums. MoveFlow enables:

* **Automated Vesting Schedules**: Ensuring tokens are distributed according to predefined rules.
* **Immutable Smart Contracts**: Preventing unauthorized changes and reducing the risk of rug pulls.
* **Transparent Distribution**: Allowing stakeholders to verify their vesting progress on-chain.

### Token Airdrops

MoveFlow simplifies the process of distributing tokens to community members and early adopters. With our protocol, projects can:

* **Automate and Schedule Airdrops**: Ensuring fair and verifiable distribution.
* **Reduce Gas Costs**: Optimize batch processing for efficiency.
* **Engage Users Effectively**: Encourage adoption through controlled token incentives.

### Real-Time Payroll

Payroll processes can be slow and inefficient in traditional finance. MoveFlow introduces **stream payments**, allowing employees and contributors to receive their salaries in real time:

* **Cash Flow Optimization**: Companies can better manage their treasury without large upfront disbursements.
* **Instant Access to Earnings**: Employees can withdraw their earned salaries at any time, improving financial flexibility.
* **Cross-Border Transactions**: Eliminating the friction and costs associated with international payroll processing.

### Subscription and Pay-Per-Use Model

MoveFlow enables flexible, usage-based payment models, transforming how services are billed:

* **Usage-Based Billing**: Users pay only for the time or resources they consume.
* **Automated Subscription Management**: No need for manual renewals or cancellations.
* **Fair Pricing Models**: Businesses can align revenue models with actual service consumption.


---

# 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/use-case.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.