Today I am proud to announce the ‘Broadcast Token Naming System (BTNS)’ spec, which enables various projects to play around with alternate token naming systems in a easy-to-use and scalable format.
Similar to BRC-20 and SRC-20, tokens may be created, minted, and transferred via the DEPLOY, MINT, and TRANSFER actions. The difference here is that the BTNS is an OPEN system which only focuses on creating tokens in the simplest and scalable way, and ignores any additional unnecessary requirements (such as that data must live in UTXOs, or that a DEPLOY must use keyburn).
I feel it is very important to separate technical specs (how to perform a valid action), from project-specific dogma and additional requirements.
The BTNS system is an open system which anyone can use to experiement and mint Tokens immediately using Counterparty Broadcasts.