Recent Development Progress

The whitepaper that explains the magic of Fractal Technology is now live and available. The whitepaper has been kept under wraps for nearly a year. The impact of Fractal is profound, so excessive testing was completed prior to releasing the whitepaper and documentation.

Version 3.1 of the data processing neurons, collectively known as 'Hives' are live and functioning. They have been in testing for the past two months.

The Vertisan Exchange is supposed to be a non-profit that exists to facilitate the needs of individuals holding Vertisan Coins and other cryptocurrencies. Since it's a non-profit, then technically the domain name should not end with ".com", because that is an indicator of a commercial organization. A non-profit should have a ".org" top level domain. As such, the Vertisan Exchange is now at the website address vccx.org.

The exchange website was updated with multiple enhancements.

• A random selection process was implemented to select sell orders for the home page.
• The website was further optimized for mobile devices.
• The build process was updated to provide a more granular view into individual assemblies and components.
• More "About Us" information was added.
• The new Vertisan Exchange logo was deployed to the website.

The version 3.2 object models for Fractal are now live in production. The new models facilitate significant improvements to Fractal's processing speeds between Fractals.

Sell orders are now live on the Vertisan Exchange. The sell orders provide the ability for holders of Vertisan Coin to offer them for sale. Completion of exchange transactions is still manual, but the exchange is fully functional and effective.

Multiple updates were published for the Vertisan Coin website. Improvements were made to the website design, scaling for mobile devices, and responsive design. Significant middleware improvements were also deployed.

There was a technical issue where the firewalls between the application servers and back-end data sources dropped all of their configuration rules. That was an issue that shouldn't happen because there are multiple firewalls and redundant routes. The anomaly was resolved by clearing all caches, purging all existing routes, and then pushing the rule-bases back onto the equipment. Testing has shown everything to be functioning normally.

Significant progress and improvements were completed on business managers, stores, and validation:
• VertisanIdentityUserStore
• VertisanUserManager
• VertisanPasswordHasher
• VertisanIdentityUser
• VertisanPasswordValidator
• Localization for error messages

Extensive work was done in the past several days on the data structures and data access implementation, which is used by the Vertisan Centralized Authorization system.
• Schemas were added and modified.
• Entity table structures were enhanced.
• Data modification timestamping was enhanced.
• VertisanUserManager was significantly expanded.
• Claims, roles, tokes, and logins validation was enhanced.