> 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 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://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 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.