BTNS Token Reservations

[jdogresorg]

When the BTNS was first created, it was created out of necessity as an entirely new/open system for creating tokens.

As my intentions with BTNS are to experiment and build out features which could be implemented into Counterparty at some future date, I feel that it makes the most sense respect the Counterparty ledger at this time, and reserve BTNS token names for CP asset name holders (if you own JDOG on CP, you hold the rights to issue JDOG on BTNS).

All that BTNS really uses from CP is the broadcast function and the data encoding methods (multisig, op_return, etc). At some point in the future, it is entirely possible for BTNS to branch off into it's own entirely separate platform and not a layer that runs on top of counterparty.

If/when BTNS becomes its own platform and parts ways with the underlying protocol (counterparty/dogeparty), it would make sense at that time to open up the "reserved" token names for anyone to register.

My hope is that the CP community sees BTNS as a fun way to experiment with features on CP before possibly integrating the features into counterparty codebase.... but, if the CP community sees BTNS as a net negative, and wants to divorce the two, I am entirely prepared to "fork" BTNS off into its own thing (would only require 1-3 days of work) and open up the "reserved" names for registration.