> 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/whitelisted-shipment.md).

# Whitelisted Shipment

<figure><img src="https://1392582159-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcyWS6C4exRxDQQnciexT%2Fuploads%2FZ8kht3u7eC6NzkOit8Qg%2Fwhitelisted-shipment.jpeg?alt=media&amp;token=9b161bc6-2baa-494b-b609-72cc4643806d" 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** (Daniella). Bob is sending a large amount of funds, and wants to ensure that multiple checks are in place before the asset Capsule can be accepted. As such, Bob requires 6/10 signatures to be confirmed from 10 different addresses: **0x…10**, **0x…11**, **0x…12**, and so on.

Daniella cannot claim the assets until at least 6 signatures are attached to her acceptance transaction. Once enough signatures have been assembled for the shipment, Daniella properly accepts the shipment and redeems for the funds.&#x20;

Of course, in this situation or any other, as many checks and balances can be added to the shipment as required, including password, time lock, asset key, signatures, and so on.

***

If this interests you view our developer example of a [Whitelisted Redemption contract](/protocol-overview/developer-walkthroughs/code-examples/whitelisted-redemption.md).
