Crown Platform NF Tokens Layer
Motivation/Problem
Originally, in order to register any specific data/metadata on the blockchain opcodes were planned to use. One of the main disadvantages of using the Bitcoin Scripting language opcodes is that they are tied to inputs/outputs and their financial logic. It was the main reason for such complex registrations opcodes system originally. In order to simplify the implementation of the registration layer, it was decided to use special transactions proposed by Dash developers dip-002. During the implementation, a new name was proposed that represented the nature of this registration layer. The closest definition in the tech for this is a non-fungible token or NFT. NF token represents any unique asset existing in the real world that we can put on a blockchain, or in other words tokenize it. NF tokens should be used to represent different real-world assets like identities, app representations, crypto-collectables etc. The Crown opcodes are still may be used for creating connections between special transactions and classic transactions. The platform goals and architecture stays the same, only implementation details have changed.
Notes/link/references
More about nf tokens: link
Technical document overview: link