> For the complete documentation index, see [llms.txt](https://docs.talus.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talus.network/talus-docs-v2.1.0/reference/sdk/protocol.md).

# Protocol Resolution

**Audience:** Nexus SDK integrators (Rust). **Area:** protocol-resolution compatibility. **Generated from:** Nexus SDK public API at release `v2.1.0` commit `45d397aafcfbeeeaf5032d5fb9fa5d99b3f36205`; historical comparison revision `c8ff64c347f2aa95febabba8d02cf1c482a94a18`.

{% hint style="warning" %}
This page contains a historical compatibility note. The documented `v2.1.0` SDK does not expose the old `ProtocolResolver` module or its snapshot API.
{% endhint %}

### Current v2.1.0 boundary

Protocol and package bindings come from the SDK's generated Move binding modules. The build-time IR under `sdk/src/move_bindings/` is the ABI authority: declaration order determines BCS layout, and package versions must be resolved through the selected `NexusObjects` and `NexusContext`. Do not recreate these bindings as hand-written application mirrors.

For a client integration, resolve the selected deployment with `NexusClient`, `StateResolver`, and the context helpers, then use the action, transaction, and crawler APIs documented in [Decoded SDK Types](/talus-docs-v2.1.0/reference/sdk/types.md#package-and-deployment-types). Confirm object identities, versions, and transaction effects with authoritative readback before signing.

### Historical compatibility boundary

Older SDK revisions exposed `ProtocolResolver`, `ProtocolExtras`, and a maximum supported Protocol version. Those APIs are retained here only to explain legacy integrations. Their errors, including `StaleProtocol`, `UnsupportedProtocolVersion`, and `ProtocolValidation`, are historical and are not `NexusError` variants in the documented SDK.

#### Legacy names

`ProtocolResolver`, `ProtocolExtras`, `MAX_SUPPORTED_PROTOCOL_VERSION`, `NexusClient::refresh_protocol`, and `NexusClient::into_protocol_snapshot` belonged to the removed module. Do not copy their signatures into code targeting the documented SDK.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talus.network/talus-docs-v2.1.0/reference/sdk/protocol.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 `build a script that syncs our docs to a CMS` 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.