The Tokenized Protocol was developed specifically for the Bitcoin SV (BSV) blockchain given the network\u2019s advanced capabilities at managing large amounts of data. It gives businesses and other entities tools to create smart contracts that comply with regulations in jurisdictions across the globe, allowing those businesses to confidently introduce blockchain solutions. As with any technological innovation, there comes a time when updates are needed to make improvements and offer new features, and minds behind the protocol have announced the completion of an overhaul to keeping Tokenized moving forward. In a blog post from yesterday, Tokenized explains, \u201cDue to continued research, we have made several changes to the protocol and implementation for the upgrade to version 0.1.0.\u201d These updates required some major restructuring, which could result in users of the platform having to upgrade in order to keep the platform\u2019s integrity intact. Among the changes was a separation of actions, assets and messages into their own distinct schemas. Each has its own package, while the Tokenized protocol contains the common code. Tokenized adds, \u201cYou may see compiler issues like \u2018undefined protocol.ContractOffer\u2019 which should now be \u2018actions.ContractOffer.\u2019\u201d Developers working with specification implementation may have seen an issue with how sizes were defined in the protocol, with different values representing different things depending on the context in which it was used. Object sizes were mostly listed in bytes, but bits were used in some lists or variable size types. Going forward, size \u201conly specifies the size in bytes of the object, mostly for numbers, and fixed binary and text.\u201d Explaining the issue further, Tokenized specifies that \u201ctiny\u201d means up to 256 bytes or items, \u201csmall\u201d means up to 65,535, \u201cmedium\u201d is up to 4,294,967,295 and \u201clarge\u201d is for 1.8x1019 bytes or items. In the protocol\u2019s previous version, all addresses had to be P2PKH (pay to public key hash), allowing Tokenized to only maintain the public key hashes in order to reference addresses in the protocol or code. Going forward, other locking scripts have been added. Tokenized provides clarification, stating, \u201cTo serialize and use them we use a new class called RawAddress (smart-contract\/pkg\/bitcoin) which contains a type and the data required by that type. RawAddresses can be converted into an Address, by adding the network ID, that can be encoded as a commonly known bitcoin address string.\u201d Other changes, including the inclusion of additional pointers and an improved serialized interface, will make the platform run more smoothly. Changes to certain coding terminology have been made, as well, in an effort to make the code more consistent with general naming conventions. These improvements build on what was already an extremely useful tool for businesses as they adopt blockchain technology into their operations. With the ability to handle larger blocks than any other blockchain, BSV is able to be offer a business-grade solution to help any entity advance its framework, becoming more efficient with optimized business processes.