> For the complete documentation index, see [llms.txt](https://passiveincome.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://passiveincome.gitbook.io/whitepaper/passive-income-the-solution/tokenized-assets.md).

# Tokenized Assets

Assets can be used to generate passive income. This is the second pillar/principle of economic activity that will benefit sustainability.

A 1.5% fee gets applied to each transaction that is defined as a tradable asset. Difference compared to holding is that the fee will be split in 2 parts, 0.75% will go to PSI Holders and 0.75% will be used for buyback integration or be added as liquidity.

A special exemption to the aforementioned is that PSI also offers the ability to earn ETH. On our presale platform a presale buyer can deposit ETH to participate in a presale. A x% fee gets applied to the ETH deposits and will be shared amongst all PSI holders. On the other hand there are the parties that want to execute a presale on the PSI presale platform. A x% fee gets applied to deposited amount of native tokens and the accumulated tokens will be distributed amongst all PSI holders when the presale succeeds.


---

# 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://passiveincome.gitbook.io/whitepaper/passive-income-the-solution/tokenized-assets.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.