🟧TAP Punks

TAP Tokens paying homage to the original CryptoPunks.

Introduction

Having access to ticks other than 4 ch thanks to the TAP Protocol, we can now deploy Punk Tokens! Inscription Process: (https://github.com/BennyTheDev/tap-protocol-specs)

{ "p": "tap", "op": "token-deploy", "tick": "Punk #2681", "logo": "fb6d2d5e89fd4194e2c17526766aab0538228d1c33d83322a1c1c08c87b5936fi0", "max": "1", "lim": "1", "dec": "0" }

{ "p": "tap", "op": "token-mint", "tick": "Punk #2681", "amt": "1" } { "p": "tap", "op": "token-transfer", "tick": "Punk #2681", "amt": "1" } deploy FIRST, mint SECOND, transfer THIRD (for trading). Replace "tick" and "logo" values with the values of the Punk you are about to inscribe (more below).

Overview

- First is First. - "tick" format: "Punk #XXXX" *blank is required - "max" , "lim", "amt" should be "1". (But , remember , Ⓐnarchy!) If "dec" is "0" , they are 1/1; without "dec", they can be fractionalized. Ⓐnarchy ! - "logo" is optional and doesn't interfer with the indexing of the token by TAP (tested). Use the inscription ID of the corresponding Punk found at https://magiceden.io/ordinals/marketplace/bitcoin-punks - You can try to deploy and mint in the same block , just use lower fees for mint. And inscribe separately (deploy first). - For some reason Unisat gives network error when searching with a blank. Instead, you can search for the numerical Punk #ID , eg: search for #2681 and check if it has already been deployed and minted. - Check balance at https://trac.network/tap.html