> For the complete documentation index, see [llms.txt](https://stellar-developer-tools.gitbook.io/authmatrix-core/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stellar-developer-tools.gitbook.io/authmatrix-core/overview.md). # Overview Soroban authorization entries changed in Protocol 27. This repo checks that two independent implementations compute the same signature payload for the same entry, and that the real Soroban host agrees. AuthMatrix core is a language-neutral, versioned set of **authorization vectors** (with single-field **mutation vectors**), **two independent adapters** (TypeScript on `@stellar/stellar-sdk` 17.2.1, Rust on `stellar-xdr`), a **conformance runner**, a pair of **nested fixture contracts**, and **recorded host evidence** (offline with the Soroban host, and live on Stellar testnet). The browser UI that consumes it is a separate repo, `authmatrix-inspector`. Background: CAP-71 (Protocol 27) added `SOROBAN_CREDENTIALS_ADDRESS_V2` and `..._ADDRESS_WITH_DELEGATES`, whose signature payload is `ENVELOPE_TYPE_SOROBAN_AUTHORIZATION_WITH_ADDRESS` (binds the signer's address). The legacy `ADDRESS` payload is still valid. See the SDK's [Protocol 27 migration page](https://stellar.github.io/js-stellar-sdk/migration/protocol-27-soroban-auth/). Testnet reported Protocol 29 when the evidence here was recorded. Source: [authmatrix-core on GitHub](https://github.com/Auth-Matrix/authmatrix-core). Releases: [GitHub releases](https://github.com/Auth-Matrix/authmatrix-core/releases). --- # 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://stellar-developer-tools.gitbook.io/authmatrix-core/overview.md?ask=&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.