> For the complete documentation index, see [llms.txt](https://docs.peach.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peach.ag/documentation/arc/adaptive-pools/changelog.md).

# Changelog

Release notes for @masterpeach/market-sdk.

Release notes for [@masterpeach/market-sdk](https://www.npmjs.com/package/@masterpeach/market-sdk). Publication dates are in UTC.

### 1.0.1 — 2026-10-21

* Updated mainnet presets to the 2026-10-21 configuration.

[View SDK 1.0.1](https://www.npmjs.com/package/@masterpeach/market-sdk/v/1.0.1)

### 1.0.0 — 2026-10-20

* First stable SDK release: deployment verification, pool discovery, fee/session reads, liquidity operations, net earnings, share and claim authorization, and permission-aware management.
* Provides the root, /abi and /core package entry points.

[View SDK 1.0.0](https://www.npmjs.com/package/@masterpeach/market-sdk/v/1.0.0)

### Documentation reference scope

Direct-contract reference material is based on the supplied `v1.1` integration guide and its pinned contract version. This documentation scope is separate from the SDK release versions above.

* Records the Arc Hook deployments, PoolKeys, PoolManager and Quoter.
* Specifies ordinary and keeper fees, RWA calendar curves, and Mid-block observations.
* Includes block-pinned state reads, quote and settlement rules, executable fee examples and historical validation evidence.


---

# 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.peach.ag/documentation/arc/adaptive-pools/changelog.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.
