> ## Documentation Index
> Fetch the complete documentation index at: https://docs.istravex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Maintenance

> Who maintains Istravex, what happens on a protocol upgrade, and how to get involved.

Istravex is Apache 2.0 licensed and open by default. Code, corpus, results and docs all live in one public repository.

## Commitments

| | |
| - | - |
| **License** | Apache 2.0 |
| **Maintainer** | A named maintainer for at least six months after launch |
| **Protocol upgrades** | At least one protocol upgrade covered end to end |
| **Telemetry** | None. Neither the site, the API, the tools nor the docs collect any. |

## On a protocol upgrade

**1. Re-pin stellar-core**

Update `kit/capture/core-pin.json` with the new version, commit and per-platform binary hashes, and the CI job's apt package version.

**2. Bump the SDKs**

Move the JS, Go and Rust runners to the SDK releases for the new protocol.

**3. Regenerate and re-run**

`npm run corpus:generate -- --force`, `node kit/goldens/fetch.mjs`, `npm run corpus:run`. The goldens move with the core pin.

**4. Audit**

`npm run corpus:audit` against the latest stellar-protocol. New XDR-changing CAPs appear as gaps.

**5. Release**

Tag a release with the results, and note any SDK or indexer behaviour that changed.

## Getting involved

* **Report** a wrong fixture, a lint false positive, or a broken page as a [GitHub issue](https://github.com/hackcat29/istravex/issues).
* **Contribute** a fixture for an uncovered CAP. See [Contributing a fixture](https://docs.istravex.com/corpus/contributing.md).
* **Run a pilot** on your indexer and share what you find. See [Replaying into your indexer](https://docs.istravex.com/pilots/your-indexer.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.