> For the complete documentation index, see [llms.txt](https://docs.capsulelabs.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.capsulelabs.xyz/protocol-overview/use-cases/wrong-address.md).
# Wrong Address
The above figure displays an example of a user at address **0x…1** (Bob) attempting to send assets to user **0x…3** (Alice). Upon creation of the Capsule Shipment, Bob specifies to send his assets to **0x…2** – Bob has made a mistake inputting Alice’s address. This is no problem for Bob or Alice – Alice simply lets Bob know he has made a mistake, and he should update the shipment to ship to address **0x…3** instead (her address). Bob does so, and Alice is able to properly accept the assets shipped. No assets were lost due to an incorrect shipment address.
If this transaction were to have been broadcasted and accepted as is (without using CPaS, directly from **0x…1** to **0x…2**), all assets are lost – the assets at **0x…2** are inaccessible by both Bob and Alice. This results in a loss for Bob (who owned the funds) and Alice (who expected the funds). Additionally, had multiple assets been bundled within a Capsule - this would have saved multiple assets from being lost (assuming the incorrect address was input multiple times). These situations can be easily averted by using CPaS.
---
# 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://docs.capsulelabs.xyz/protocol-overview/use-cases/wrong-address.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.