# Extended Functions This section desribes each extended functions of the TAP Protocol. From how to prevent transferable grief attacks to functions that help to support programmability, you'll find everything you need here. Many of the extended functions are tappable. **Tappable** means that these functions require an approval. This process is simple: inscribe a function into your wallet and send it to yourself to approve. The TAP Protocol got its name from this process to allow for most of the special features to function. ### Prerequisites * A Bitcoin wallet with Ordinals support. * An inscription service or app of your choice that is capable of inscribing text for Bitcoin Ordinals. * The [TAP Reader](https://github.com/Trac-Systems/tap-reader/) to lookup deployments, mint status, account balances and much more. * Additional resources - if any - in the description of each extended function. --- # 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://docs.tap-protocol.com/functions/publish-your-docs.md?ask= ``` 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.