> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/wiki/addresses-and-wallets/bitcoin-address/brainwallet.md). # Brainwallet Brainwallets are like the mnemonic seeds generated by hardware wallets, however, the human user generates the words themselves and memorises them without any written record. The mnemonic seed/ passphrase is never written down. It is 'stored' in the holder's brain. If the holder forgets the passphrase (or becomes incapacitated), the money is likely lost forever - not a very secure storage method. Creating randomness in passphrase words is extremely difficult to do by hand, therefore security is again compromised. It is possible to use a [BIP 39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki) passphrase generator to get strong entropy/ randomness and optionally add a salt value for additional security, however storing anything in the human brain carries inherent risks. Use a brainwallet at your own (high) risk. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hub.bsvblockchain.org/wiki/addresses-and-wallets/bitcoin-address/brainwallet.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.