> For the complete documentation index, see [llms.txt](https://gitbook.mor.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.mor.org/~/revisions/3ulU7lsttK8DsMz9IH4e/smart-contracts/documentation.md).

# Documentation

At genesis, the Morpheus network utilizes six smart contracts, including the MOR token itself, used to incentivize key contributors to the network, as well as contracts enabling the [Techno Capital Machine](/~/revisions/3ulU7lsttK8DsMz9IH4e/tokenomics/techno-capital-machine.md) mechanism functioning.&#x20;

### **Morpheus Smart Contracts Set**

* [`MOROFT`](/~/revisions/3ulU7lsttK8DsMz9IH4e/smart-contracts/documentation/mor-oft.md) – the Morpheus token, a [LayerZero Omnichain Fungible Token](https://docs.layerzero.network/v2/developers/evm/oft/quickstart) (OFT)
* [`Distribution Protocol`](https://gitbook.mor.org/~/revisions/3ulU7lsttK8DsMz9IH4e/smart-contracts/documentation/distribution-protocol/v7-protocol) – used to lock capital for the Techno Capital Machine and claim rewards
* [`LinearDistributionIntervalDecrease`](broken://pages/QJAF4licTtnk8gO0yzFM) – a library for calculating rewards
* [`L1Sender`](broken://pages/8Q5sZjVjdD5OOV2DVErF) – sends MOR claiming (minting) requests; wraps and transfers stETH to Arbitrum
* [`L2MessageReceiver`](broken://pages/LfN3h4BtBwGVOXUILj1e) – receives and processes MOR claiming (minting) requests on L2
* [`L2TokenReceiverV2` ](broken://pages/f69hcuxePxUiqwFzarS9)– receives wstETH and manages Protocol-Owned Liquidity on L2

With the exception of the MOR token and `LinearDistributionIntervalDecrease` library, all contracts utilize the [UUPS proxy pattern](https://docs.openzeppelin.com/contracts/5.x/api/proxy#UUPSUpgradeable) to enable upgradeability and are owned by the [Morpheus multisignature accounts](/~/revisions/3ulU7lsttK8DsMz9IH4e/smart-contracts/multisig.md) on their respective chains.\
\
Within the contracts, **deposit token** is used to refer to the token deposited by Capital Providers (stETH) or its wrapped counterpart (wstETH), while **reward token** refers to the MOR token.

### Audits

The Morpheus smart contracts were audited [by Renascence](https://github.com/MorpheusAIs/Docs/blob/main/Security%20Audit%20Reports/Distribution%20Contract/Distribution%20V2%20Audit%20%7C%20Renascence.pdf) and later subject to a public [CodeHawks audit](https://www.codehawks.com/contests/clrzgrole0007xtsq0gfdw8if).


---

# 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://gitbook.mor.org/~/revisions/3ulU7lsttK8DsMz9IH4e/smart-contracts/documentation.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.
