> For the complete documentation index, see [llms.txt](https://doc.lockerprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.lockerprotocol.com/reference/qr-formats.md).

# QR formats (BC-UR / Keystone)

For developers: the codes the Vault and the extension exchange.

Everything that crosses the air gap is a **BC-UR** payload (`ur:<type>/…`), single-frame or animated (fountain-coded) when it does not fit in one QR. The formats come from the Keystone family, so the signing requests are the ones hardware wallets already speak.

## Sync (Vault → extension)

| UR type                 | Content                                                                                                                                                                                                                                                      |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `crypto-multi-accounts` | Every chain family of one account, with its derivation path: Ethereum, Solana, Tron, Bitcoin (payment + ordinals), Litecoin, Dogecoin, Sui, Stellar, the Cosmos chains, Aptos and XRP. **The only payload the Vault emits**, from **Extension Sync**.        |
| `crypto-account`        | Bitcoin watch-only descriptor, meant for Sparrow or Nunchuk. Show it to the extension by mistake and it says so by name. (The extension can still read an old EVM-only descriptor from another wallet; the Vault has not produced one since September 2026.) |

## Requests (extension → Vault)

| UR type                            | Chain                                                                                          |
| ---------------------------------- | ---------------------------------------------------------------------------------------------- |
| `eth-sign-request`                 | Ethereum & EVM: transactions (legacy, EIP-2930, EIP-1559), `personal_sign`, EIP-712 typed data |
| `eth-batch-request`                | EIP-5792 batch: several EVM transactions under one review                                      |
| `crypto-psbt` / `btc-sign-request` | Bitcoin PSBT / Bitcoin message                                                                 |
| `sol-sign-request`                 | Solana transaction or off-chain message                                                        |
| `sui-sign-request`                 | Sui transaction or message                                                                     |
| `stellar-sign-request`             | Stellar transaction, Soroban call, or SEP-10 sign-in                                           |
| `cosmos-sign-request`              | Cosmos: SignDoc (protobuf) or amino bytes                                                      |
| `aptos-sign-request`               | Aptos raw transaction                                                                          |
| `keystone-sign-request`            | Tron, XRP Ledger, Litecoin and Dogecoin (a typed envelope with the chain's own coin code)      |

## Responses (Vault → extension)

`eth-signature`, `eth-batch-signature`, the signed `crypto-psbt` / `btc-signature`, `sol-signature`, `sui-signature`, `stellar-signature`, `cosmos-signature`, `aptos-signature`, and `keystone-sign-result` for the families that travel in the typed envelope.

Each response carries the **request id**. A signature made for another request is refused on sight (*That QR does not answer this request*), so an old answer cannot be replayed into a new transaction.

## Bounds

Both sides refuse an oversized code before it is decoded: a part count above **10 000** is rejected rather than allocated, so a QR held in front of either camera cannot make the app eat memory. A request that is too large to prove (for example a Bitcoin input whose funding transaction would need hundreds of frames) is refused with a message that says so, instead of being signed on a fee nobody can check.

## Backups

The **encrypted QR backup** is a Locker-specific payload: account data encrypted under a password you choose at export time. It is not a Keystone format, and only a Locker Vault can restore it.

{% hint style="info" %}
Reference implementations: the extension's `core/background/keystone/` and the per-family `core/background/<family>/envelope.ts`, and the Vault's `keystone-sync.service.ts`, `ur.service.ts` and `src/app/multichain/*`.
{% endhint %}
