> 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/move/nexus_interface/version.md).

# version

* [Struct `InterfaceVersion`](#struct-interfaceversion)
* [Constants](#constants)
* [Function `v`](#function-v)
* [Function `number`](#function-number)
* [Function `expect_v`](#function-expect_v)

### Struct `InterfaceVersion`

Identifies the interface revision implemented or expected by the surrounding stored state.

```move
public struct InterfaceVersion has copy, drop, store
```

<details>

<summary>Fields</summary>

`inner: u64`

</details>

#### Constants

```move
#[error]
const EInterfaceVersionMismatch: vector<u8> = b"Interface version mismatch";
```

#### Function `v`

Wraps a raw version number into an [`InterfaceVersion`](#nexus_interface_version_InterfaceVersion).

```move
public fun v(version: u64): nexus_interface::version::InterfaceVersion
```

#### Function `number`

Returns the raw version number.

```move
public fun number(self: &nexus_interface::version::InterfaceVersion): u64
```

#### Function `expect_v`

Asserts that this interface version equals the expected number.

Aborts with [`EInterfaceVersionMismatch`](#nexus_interface_version_EInterfaceVersionMismatch) if the version does not match.

```move
public fun expect_v(self: &nexus_interface::version::InterfaceVersion, expected: u64)
```


---

# 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/move/nexus_interface/version.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.