TAP Protocol Developer Docs
  • Welcome
  • Functions
    • Basic Functions
    • Extended Functions
      • Block Transferables
      • Unblock Transferables
      • Mass Send
      • Token Authority
      • Privilege Authority
      • Peer2Peer Trading
      • Digital Matter Theory
  • Smart Contracts
    • TAP / ICP Overview
    • TAP / ICP Boilerplate
    • More Chain Support
  • Resources
    • TAP Reader (Node)
    • TAP Wallet (Chrome Store)
    • TAP Wallet (Github)
    • Whitepaper
    • Tapalyticcs
    • TAP API (hosted)
Powered by GitBook
On this page
  1. Functions

Extended Functions

PreviousBasic FunctionsNextBlock Transferables

Last updated 6 months ago

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 to lookup deployments, mint status, account balances and much more.

  • Additional resources - if any - in the description of each extended function.

TAP Reader