# Test BRC-100 conformance

> For the complete documentation index, see [llms.txt](https://bsvblockchain.com/docs/llms.txt).

Run the ts-stack test vectors against a BRC-100 wallet and back a conformance claim with a pass for every required vector.

import ConformancePath from '/snippets/ConformancePath.jsx';

Prove that your wallet answers each BRC-100 (BSV Request for Comments 100, the standard interface between apps and wallets) method the way the TypeScript reference does. You run the ts-stack test vectors against your wallet and end with a result that names every vector it passes and every vector left open. [Build a wallet](https://bsvblockchain.com/docs/wallet-dev/) shows where this step sits in the path of a wallet.

## How it works

A run has three parts, and the runner is the only one you write or adapt:

<ConformancePath />

A conformance run has three parts. 1. The vectors: one JSON file per BRC-100 method under wallet/brc100/, from a pinned ts-stack commit. 2. Your runner: builds the wallet from each vector's root key, calls the method and compares the result with the expected one. 3. Your claim: every required vector passes, and every intended one is listed with its reason.

Pin the ts-stack commit you test against, as a git submodule or a fixed checkout, so the expected results do not change under your wallet. This page was written against ts-stack commit `389d5d8` of October 27, 2026.

## Know what a claim covers

Each vector carries a parity class, and the BRC-100 vectors use two of them:

- `required`: every conformant wallet passes the vector.
- `intended`: the vector needs wallet state that the reference harness does not build yet, such as a funded wallet, so the runners skip it and record the reason.

A first claim passes every `required` vector and lists the `intended` ones as open, with their reasons. To pass an `intended` vector, your test harness has to build the state it needs, such as funds or a stored certificate, and then run it.

## Choose a runner

The runner depends on the language of your wallet:

- A TypeScript wallet runs the vectors with the Jest runner in ts-stack, described in [Run the vectors in TypeScript](https://bsvblockchain.com/docs/wallet-dev/conformance/typescript-runner/).
- A wallet in another language reads the JSON files from the pinned checkout with its own runner. Keep the file and vector IDs in its output, report the methods it does not test instead of leaving them out, and follow the flags and exit codes in the [runner contract](https://github.com/bsv-blockchain/ts-stack/blob/389d5d806495903ee56273978ccc7e8ab71ceb86/conformance/VECTOR-FORMAT.md#runner-contract).

## Next steps

With the path clear, see what each vector file covers:

- [Browse the test vectors](https://bsvblockchain.com/docs/wallet-dev/conformance/vector-catalog/)