# Tap

TAP is an extendible OrdFi-enabling protocol that includes - but is not limited to - the TAP token standard.

TAP works entirely without the use of L2 chains or other overly complex mechanics, but utilizes tapping - a simple mechanism to verify transactions within the protocol.

The goal of TAP is to built upon what made BRC-20 great but maintaining independence from centralized entities. TAP allows for new features that will be consistently added to the protocol by community driven governance.

The BRC-20 ticker lengths 1,2 and 4 are reserved for future interordinal bridging between BRC-20 and TAP Tokens and cannot be deployed on TAP.

Tap: <https://github.com/BennyTheDev/tap-protocol-specs>\
\
This section will introduce how to use 4 functions related to Tap.<br>

{% content-ref url="/pages/l3wYhAQhfwSqwEtj0qow" %}
[Mint🚧](/satx/inscribe/tap/mint.md)
{% endcontent-ref %}

{% content-ref url="/pages/j6I57ptf9LObxE1F2khS" %}
[Transfer🚧](/satx/inscribe/tap/transfer.md)
{% endcontent-ref %}

{% content-ref url="/pages/Qw0Ku9vJSeGL44oII4ld" %}
[Deploy🚧](/satx/inscribe/tap/deploy.md)
{% endcontent-ref %}

{% content-ref url="/pages/ExUf0D06dhGIK9rLCGjd" %}
[Token-Send🚧](/satx/inscribe/tap/token-send.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://satxio.gitbook.io/satx/inscribe/tap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.