Anyone can start creating non-fungible tokens (NFTs) and other tokens on the RUN protocol by clicking a few buttons thanks to Joshua Henslee\u2019s latest launches, Tique Case and Mint.Tique.<\/p>\n
Tique Case and Mint.tique come at a crucial time. Many people have been discussing the benefits of working on the RUN network; however\u2014until the launch of Tique\u2014it was not exactly easy to create on Run unless you were a software developer. When asked what inspired him to create Tique, Henslee said:<\/p>\n
\u201cHonestly, it was the frustration in December 2020 I had with wallets and token adoption. I was particularly frustrated with RelayX who had supported RUN in the past but disabled it (for legitimate reasons). Funnily enough, they have pushed this further in the first three months of 2021 than I would have imagined.<\/p>\n
\u201cSecondly, I wanted to integrate tokens into my apps Windbell and retrotwetch, but would have had to build my own wallet in the app to do so\u2014which I was not willing to do.<\/p>\n
\u201cI have always believed tokenization on BSV would push the space forward, but I thought it was taking much too long so I decided to build a couple of tools to help bootstrap adoption.\u201d<\/p>\n
Tique filled a crucial infrastructure gap that existed in Bitcoin SV (BSV)\u2014several people want to create apps, products, and services on the RUN network; however, only a few people have the technical know-how to accomplish this. With the launch of Mint.Tique\u2014the tool that allows individuals to create Jigs in a matter of minutes\u2014and Tique Case, the client-side wallet that can hold BSV as well as tokens and NFTs in the form of JIGs\u2014everyone, including non-technical individuals, can create on the RUN network.<\/p>\n
\u201cA client-side wallet means that all keys, configurations and UTXOs are stored on the user\u2019s device in their browser. I do not run a back-end server for the Tique Case wallet. The user has full control over the wallet; I do not collect any data whatsoever from Tique Case users,\u201d Henslee said. \u201cThis is a stark contrast to how other major players in the space believe Bitcoin should be handled by the users, but I feel ownership and control are important, especially for the purposes I intended of this wallet which are both a development and user token management tool.\u201d<\/p>\n
He added, \u201cA jig is an NFT on the RUN protocol. It is a non-fungible token that can have whatever properties the creator likes. Jigs are interactive objects, meaning they have the ability to work with other Jigs and change over time. For example, a player jig can equip a sword jig increasing their attack power. Jigs can also own other jigs so that you could have a forgery Jig that is responsible for forging weapon Jigs. A jig could also be an egg that hatches over time into a digital pet like a dragon. Those pets can also have different attributes depending on what actions were taken on them in the past. The possibilities are endless.\u201d<\/p>\n
It\u2019s worth noting that Tique Case is the very first Bitcoin wallet that allows individuals to hold and view NFTs.<\/p>\n
\u201cIf you associate an on-chain image via BitcoinFiles to your NFT, that will also display in the wallet. In theory, you can do this now with Mintique and set the supply to be 1,\u201d Henslee said.<\/p>\n
At the moment, the fungible tokens created via Mint.tique are compatible with RelayX; the fungible tokens created via Mint.tique can be sent to Tique Case as well as RelayX via paymail and vice versa.<\/p>\n
\u201cUsers can send tokens from RelayX to Tique Case by pasting 1OWNERaddress@tique.run in the Paymail or Address field when sending from the RelayX wallet,\u201d Henslee said. \u201cMoney Button does not support RUN yet \u2013 but I look forward to them doing so in the near future. If any user would like to send their Tokens or Jigs to other wallets, please let those wallet developers know to add RUN support!\u201d<\/p>\n
Who will win the token protocol wars?<\/strong><\/p>\n Bitcoin SV is currently in the midst of a token protocol war; there are several competing token protocols being created on BSV, and it is not yet clear which token protocol will be BSV\u2019s ERC-20 standard. Henslee says he decided to build on Run rather than another token protocol because,\u00a0<\/p>\n \u201cRUN has been used on the main chain by BSV businesses for almost two years at this point. I have been toying with it on and off since then and am quite familiar with it. I have also witnessed first-hand someone who had zero coding experience before 2019, end up developing a full application on RUN and BSV in a matter of months,\u201d he said.\u00a0\u201cWhile the other token protocols have different features and strategies to gain adoption, I feel that the only one that is appealing to new developers is RUN. I think developers of all skill levels will be able to pick it up quickly and build applications.\u201d<\/p>\n When I asked him if he believed there was going to be one winner in the protocol war, or if several token protocols would co-exist he said:<\/p>\n \u201cI have thought about this a lot. Many well-known leaders in the space have stated there will be different token protocols for different use-cases. I have also believed that in the past. I now do think the one that is the most flexible and can handle all use-cases will end up being the dominant one. I do find it interesting that Ethereum has two dominant protocols (ERC-20\/ERC-721) but the BSV narrative is multiple will thrive. After recent events in the space, I believe that one token protocol will end up as the dominant one, which is yet to be decided.\u201d<\/strong><\/p>\n So what\u2019s next for Tique?<\/p>\n \u201cI tried to keep the wallet as simple as possible, which is the reason I open-sourced it and would like other developers to take it and expand upon it,\u201d Henslee said. \u201cI do not plan on adding many features myself, since it is open-sourced I would like to see other developers build features they would like. If there is enough demand for particular features, I will consider adding them myself. Some examples I can think of are the ability to destroy or burn tokens, and upgrade contracts (for example, change the image or fix the supply). Whatever is next is what others would like to build. My goals for the wallet were to be primarily a tool that users can hold tokens in so that I can interact with them. Additionally, I wanted to bootstrap other developer’s projects by giving them a user interface to manage their tokens so they can hit the ground running when building on the RUN protocol. I will leave what I am currently working on to other\u2019s imagination based on the products I am building.\u201d<\/p>\n