# Browse the test vectors

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

The BRC-100 test vectors in ts-stack: 955 vectors in 28 files, one file per wallet method, and how many of each a wallet must pass.

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

Find the vectors that test each BRC-100 (BSV Request for Comments 100, the standard interface between apps and wallets) method and see how many of them your wallet must pass. The set holds 955 vectors in 28 files under [`conformance/vectors/wallet/brc100/`](https://github.com/bsv-blockchain/ts-stack/tree/389d5d806495903ee56273978ccc7e8ab71ceb86/conformance/vectors/wallet/brc100), one file per method, and 816 of them are `required`. This page was written against ts-stack commit `389d5d8` of October 27, 2026.

## What each group of methods covers

The files follow the method groups of [BRC-100 Wallet Interface](https://bsvblockchain.com/docs/concepts/wallet-model/). Each file is named after its method in lowercase:

<BlueTable>

| Group | Vector files | Vectors | Required | Intended |
| --- | --- | --- | --- | --- |
| Keys and crypto | `getpublickey`, `createhmac`, `verifyhmac`, `createsignature`, `verifysignature`, `encrypt`, `decrypt`, `revealcounterpartykeylinkage`, `revealspecifickeylinkage` | 583 | 583 | 0 |
| Outputs | `listoutputs`, `relinquishoutput` | 156 | 150 | 6 |
| Actions | `createaction`, `signaction`, `abortaction`, `listactions`, `internalizeaction` | 133 | 20 | 113 |
| Certificates | `acquirecertificate`, `listcertificates`, `provecertificate`, `relinquishcertificate`, `discoverbyidentitykey`, `discoverbyattributes` | 50 | 30 | 20 |
| Wallet state | `isauthenticated`, `waitforauthentication`, `getheight`, `getheaderforheight`, `getnetwork`, `getversion` | 33 | 33 | 0 |

</BlueTable>

## How a vector reads

Each file holds metadata, such as the BRC it covers and the reference it was generated from, and a `vectors` array. This is the first vector of `getpublickey.json`:

> The `root_key` in this vector is a public test value. Never fund a wallet built from it and never reuse it for a real wallet.

```json getpublickey.json
{
  "id": "wallet.brc100.getpublickey.1",
  "description": "getPublicKey protocol=0,wallet keyID=1 counterparty=self privileged=false",
  "input": {
    "root_key": "0000000000000000000000000000000000000000000000000000000000000001",
    "args": {
      "protocolID": [0, "wallet"],
      "keyID": "1",
      "counterparty": "self",
      "privileged": false
    }
  },
  "expected": {
    "publicKey": "0253f70b1025f9f13fb1dec1b2dc6077e6b57e60107642c134997ad8dab54ba290"
  },
  "tags": ["brc-100", "getPublicKey", "standard"]
}
```

- `root_key` is the root private key your wallet is built from for this vector. The vectors use the keys 1, 2 and 3 written in hex, public test values that must never hold funds. A vector without `root_key` runs on key 1 in the TypeScript runner.
- `args` is what an app passes to the method.
- `expected` is the result your wallet must return. When it holds `error`, the vector passes only if the method rejects the call.
- `id` stays the same once published, so your runner reports results by it.

## Why some vectors stay intended

An intended vector carries `"parity_class": "intended"` and a `skip_reason` that names the state it needs. The 139 intended BRC-100 vectors need one of four things:

- A funded wallet: all 90 `createAction` vectors, which need change UTXOs (Unspent transaction output) to pay the fee.
- An action in progress: the 8 `signAction` vectors and 6 of the `abortAction` vectors.
- Records already in storage: an output for 6 `relinquishOutput` vectors, a certificate for 7 `proveCertificate` and 4 `relinquishCertificate` vectors, and one stored record each for a `listActions` and a `listCertificates` vector.
- Valid outside data: real BEEF (Background Evaluation Extended Format (BRC-62)) for 8 `internalizeAction` vectors, a valid certificate signature or a live certifier for 5 `acquireCertificate` vectors, and results from a live overlay (A service that tracks the transactions of one app or protocol and answers queries about them) for 3 `discoverByIdentityKey` and `discoverByAttributes` vectors.

## Next steps

With the vectors mapped, run them:

- [Run the vectors in TypeScript](https://bsvblockchain.com/docs/wallet-dev/conformance/typescript-runner/)