> For the complete documentation index, see [llms.txt](https://docs.amp.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amp.xyz/whitepaper.md).

# Whitepaper

The AMP whitepaper introduces the primary technical elements of the AMP token contract and collateral managers. In particular, it presents novel partition strategies for enabling "stake-in-place" designs for Ethereum tokens. 

The paper also presents an analysis of legacy payment infrastructure, distributed payment networks, and token economics. This research uses established economic models in addition to a unique, in-depth assessment of the long-term utility, value, and stability of a collateral token network.

Sections include:

* **Digital Payments and the Flexa Network**
* **Decentralized collateral**
  * Finality assurance and scale
  * Meta-staking and risk distribution
* **Amp token contract**
  * Operators and partition scopes
  * Partition strategies
  * Token hooks
  * Flexa collateral manager
  * Further extensibility
* **Token economics**
  * Production model
  * Tokenization model
  * Network efficiency model
  * Stability analysis

{% file src="/files/FT3GMsOtddJAr84hIPVq" %}


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.amp.xyz/whitepaper.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.