# 6. Business & Technical Logics

## TDT is a web3.0 sports digital asset platform based on sports IP.

TDT is a web3.0 sports digital asset ecosystem that started as a blockchain-based 300FIT athletic content platform that produces and trades athletes' athletic know-how as digital content, and has expanded to various business models such as sports NFTs and merchandise utilizing various IPs of athletes such as game records, game videos, and images.

TDT's core value is that sports are not something to watch, but something to participate in and own, giving sports fans in the Web 3.0 era a new way to enjoy sports.

TDT will introduce a variety of business models in collaboration with top partners in each field, all of which will be powered by the Web 3.0 Sports League-TDT ecosystem, where fans and players can interact in new digital ways, where fans can directly participate in leagues with the players they watch, and where they are rewarded based on their performance.

<figure><img src="/files/0XGbTF0gGKnYq4Jn4GA8" alt=""><figcaption></figcaption></figure>

## [6.1 Workout Content Asset Ecosystem](/300fit-white-paper/english/6.-business-and-technical-logics/6.1-workout-content-asset-ecosystem.md)

## [6.2 Sports digital asset ecosystem](/300fit-white-paper/english/6.-business-and-technical-logics/6.2-sports-digital-asset-ecosystem.md)

## [6.3 Web 3.0 Sports Leagues](/300fit-white-paper/english/6.-business-and-technical-logics/6.3-web-3.0-sports-leagues.md)


---

# 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/6.-business-and-technical-logics.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.