Crown Atomic development
After the addition of Artem Brazhnikov, a crytpography and software security professional to the Crown dev team several weeks ago with full focus on Crown OP_CODES, the dev team agreed with Artem based on his dedicated work, that he will take a Lead Crown Atomic / API developer position.
This move has resulted in a shift of the originally indicated release dates of the Atomic project. Artem has spotted several system architecture issues, where improvements need to be made so the team has decided to run several research analysis on potential solutions shifting the release of the OP_CODES and API architecture.
Key findings of Artem are available here: OP_code Research
The Crown Atomic Dev team has also put together use cases for Crown Atomic, they are available here: Use Cases
While the code is being written, one of our key document guys, Ivan Labra (iLabra) with the support of Artem and Chaositec, is in the process of drafting technical documentation related to OP_CODES architecture. This document will be released to the public in the coming weeks.
Atomic Team Growth
As Artem recently became a full time Crown team member, there is an extensive amount of work needs to be done to complete the overall Atomic architecture. The core team will continue to bring more developers onboard at every opportunity that allows. The teams main focus is to deliver the OP_codes and API.
Chronos Nodes Expanded to Service Nodes
The development team has rebuilt the idea of Chronos Nodes, and will change the fundamentals completely. We are renaming Chronos Nodes to Service Nodes to represent the changes. The idea behind Chornos was to provide infrastructure for the 3rd way of confirming transactions ÂMiningÂ Service nodes will provide more than just timekeeping services, they will be designed to provide ser...