> 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

<figure><img src="/files/YFKS6SCLV6dDLigO6Y4s" alt=""><figcaption></figcaption></figure>

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.&#x20;

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.