> 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/glossary.md). # Glossary The words used in these docs, explained simply. | Word | What it means | | --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | **Vault** | The Locker Vault app on a phone or tablet that never goes online. It holds your keys and signs by QR. *The safe.* | | **Wallet extension** | Locker Protocol Wallet in your browser. Holds no keys; shows balances, prepares transactions, talks to websites. *The window.* | | **Air-gapped** | Physically cut off from every network. No Wi-Fi, no mobile data, no Bluetooth, no cable. | | **QR loop** | The four moves of every signature: request QR on the computer → Vault reads it → Vault shows the signed QR → computer reads it. | | **Watch-only account** | An account the extension knows by its *address* only. It can look, not sign. | | **Secret phrase** (recovery phrase, mnemonic, seed) | 12 or 24 words that *are* your account. Anyone with them controls the funds. Paper only. | | **Private key** | The secret number behind one address on one chain. A secret phrase generates many private keys. | | **Address** | Your public identifier on a chain, safe to share. `0x…` on Ethereum, `bc1…` on Bitcoin, and so on. | | **Master password** | The password that encrypts everything stored on the Vault (and, separately, the one that locks the extension). | | **Signature** | Mathematical proof made with a private key that you approved a specific transaction or message. | | **Transaction** | An instruction sent to a blockchain: a payment, a swap, a contract call. Irreversible once confirmed. | | **Message signing** | Signing text instead of a transaction. Moves nothing, but often logs you in to a site. | | **Typed data (EIP-712)** | Structured message signing. Used by many dApps for permits, orders, and Locker Protocol operations. | | **Network / chain** | A blockchain. Ethereum, Base, Arbitrum… are *EVM* networks sharing one address; Bitcoin, Solana, Tron, Sui, Stellar each have their own. | | **Gas / network fee** | What you pay the network to process a transaction. Paid in the network's own coin. | | **Nonce** | The sequence number of a transaction on an account. Same nonce + higher fee = replacement (speed up / cancel). | | **Approval / allowance** | Permission you give a contract to move up to N of your tokens. *Unlimited* means all of them, forever, until revoked. | | **dApp** | A website that talks to a wallet. | | **Swap** | Trade one token for another on the same network. | | **Bridge** | Move value from one network to another. Takes minutes; cannot be recalled. | | **On-ramp** | A provider that sells crypto for cards or bank transfers. | | **Perps** | Perpetual futures contracts (here: on Hyperliquid). Leveraged; you can lose the whole deposit. | | **Agent key** | A time-limited key that may *trade* on Hyperliquid for you, but never withdraw. | | **Ordinals** | Inscriptions on individual Bitcoin sats. The Vault keeps them on a separate address so they are never spent by accident. | | **Trustline** | On Stellar, your account's agreement to hold a given asset. Locks 0.5 XLM each. | | **Memo** | A short tag on a Stellar payment. Exchanges need it to credit your deposit. | | **PSBT** | *Partially Signed Bitcoin Transaction*: the format the extension and the Vault exchange for Bitcoin. | | **BC-UR** | The standard for putting binary data into (animated) QR codes. Same as Keystone hardware wallets. | | **Phishing** | A fake site or message that imitates a real one to make you sign something bad. | | **Address poisoning** | Sending you dust from a look-alike address hoping you copy it later. Cure: verify on the Vault. | --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.lockerprotocol.com/reference/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.