> For the complete documentation index, see [llms.txt](https://nemoprotocol-1.gitbook.io/nemoprotocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nemoprotocol-1.gitbook.io/nemoprotocol-docs/nemo-v2-object-native-yield-trading-on-sui.md).

# Nemo V2 — Object-Native Yield Trading on Sui

Abstract

Nemo V2 is a Move-native protocol on Sui for fixed- and floating-yield trading. It decomposes yield-bearing assets into Principal Tokens (PT) and Yield Tokens (YT) using per-split SplitEscrow objects that lock SY assets at the Move object level. Price discovery is performed by on-chain order books (DeepBook) instead of AMMs. The protocol separates an immutable core (nemo\_base), an upgradable facade (nemo\_ext), and adapter packages that integrate external Yield Bearing Token(YBT)s. This document provides an expanded technical summary, selected code excerpts, operational guidance, and references into the codebase for implementers and auditors.


---

# 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://nemoprotocol-1.gitbook.io/nemoprotocol-docs/nemo-v2-object-native-yield-trading-on-sui.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.