> For the complete documentation index, see [llms.txt](https://docs.tap-protocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tap-protocol.com/functions/publish-your-docs/mass-send.md).

# Mass Send

{% hint style="info" %}
Tappable
{% endhint %}

Enables mass-transfer of different tokens to many recipients:

* Users inscribe a "token-send" inscription to their Bitcoin address.
* After the transaction confirmed, the inscription has to be resent to the same address for confirmation (tapping).
* Upon tapping, the Bitcoin address must own the the amounts of tokens that are given with the inscription.
* Only if the "token-send" inscription is tapped, sending tokens will be performed.
* The receiver addresses must be carefully validated: must be valid Bitcoin addresses, must be trimmed, addresses starting with bc1 have to be lowercased.
* "token-send" is atomic upon inscribing (before tapping): all amounts, tickers and addresses must be syntactically valid.
* Upon tapping, invalid and semantically incorrect token sends must be skipped (e.g. insufficient funds, invalid amounts or invalid data types).
* Each successful token send must credit the given amounts to recipient and be removed from the sender's balance.
* Each send item must exclusively operate on available balances, not overall balances (available = balance - transferable).

```json
{
  "p" : "tap",
  "op" : "token-send",
  "items" : [
     {
      "tick": "-tap",
      "amt": "10000",
      "address" : "bc1p9lpne8pnzq87dpygtqdd9vd3w28fknwwgv362xff9zv4ewxg6was504w20"
     },
     {
      "tick": "tap",
      "amt": "10000",
      "address" : "bc1p063utyzvjuhkn0g06l5xq6e9nv6p4kjh5yxrwsr94de5zfhrj7csns0aj4"
     }
  ]
}
```