# 7.1 Service Flow 1

## Web3 Sports League Platform - TDT

TDT matches avatar NFTs of domestic and foreign sports players and sports characters from cartoons, movies, etc. with real-world My Health data, allowing sports stars and players to participate in the ecosystem as one and experience sports in a new way. All athletes, users, and sponsors (companies) who participate in the ecosystem will be rewarded for their contributions to the ecosystem.

Athletes participate in the ecosystem by creating digital avatar NFTs that represent their brand values, as well as promotional and marketing activities. Athletes and teams participating in sports competitions and games provide exercise data such as walking, running, and other activities performed by real users to the TDT ecosystem.

Sports fans (users) acquire TDT teams by purchasing team owner NFTs and acquiring digital player NFTs. They then sign up to participate in upcoming competitions or leagues in sports such as walking, running, baseball, soccer, and more.

Users match their digital athlete NFTs with real-world athletes participating in the game.

After all of this, participants are rewarded based on the outcome of the match or league.

Our goal is to drive interest and participation in all sports - elite and popular, as well as amateur and social - to take the fun of competition to a new level.

Participants aim to create their own sports ecosystem by sharing and experiencing the tension of competition through the changing value of sports digital assets.

### We are fascinated by and enjoy web3 sports leagues, and contribute to the development of the sports industry.

<figure><img src="/files/VdisomLKNY2mLRZKK2Xq" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://300fit.gitbook.io/300fit-white-paper/english/7.-service-flow/7.1-service-flow-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.