> 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/transactions-and-utxos/bitcoin-transactions/ip-transactions.md). # IP Transactions Sending bitcoins to an IP address was a convenient way of sending bitcoins to a Bitcoin address along with additional information. To send Bitcoin transactions using IP, the following steps are used: * The sender contacts the IP address of the receiver's server to discover if there is a service running which is capable of accepting IP transactions * The sender's additional information ("from", "message", etc.) is exchanged with the server * The server generates a brand new Bitcoin address and sends it to the sender * A Bitcoin transaction is created and sent to the network in the normal way IP transactions were disabled early in Bitcoin's history however the BSVAlias service marks the beginning of a return to enabling Bitcoin commerce using server infrastructure to manage receiving wallets for users. 1. Attribution This content is based on content sourced from under [Creative Commons Attribution 3.0](https://creativecommons.org/licenses/by/3.0/). Although it may have been extensively revised and updated we acknowledge the original authors. --- # 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/transactions-and-utxos/bitcoin-transactions/ip-transactions.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.