nOS, a virtual operating system on NEO, has posted an update report on recent project developments.

nOS allows users to access a new and decentralized internet. With nOS, dApp developers can host their applications in an open and decentralized environment using NEO smart contracts, thereby giving users control and transparency over how their data is used. A token generation event for nOS is due Q3 2018.

As part of the update, nOS outlined its client design competition. Contestants are welcomed to create a user interface for the nOS client, with prizes awarded to the best entries. 10 winners will receive access to the nOS pre-sale, with the top three designs also receiving a share in a 350 GAS prize pool, valued at around USD $8,000 at time of writing.

The award structure for the nOS client design competition will be as follows:

  • First place: 200 GAS
  • Second place: 100 GAS
  • Third place: 50 GAS

The deadline for submissions is May 29th. You can read more details about the contest here.

nOS also added one new advisor to its team: Roger Lim, founding partner of NEO Global Capital (NGC). NGC is an investment firm that has supported numerous NEO projects, such as Switcheo, Ontology, Trinity, and Zilliqa. It’s claimed that Lim’s involvement will play a pivotal role in the success of the nOS project and ecosystem.

One of the most significant developments in the report was the introduction of the nOS protocol. The nOS protocol allows users to access the nOS Open Internet via nos://, similar to the way https:// allows access to the traditional internet. The nOS protocol as been implemented into the MVP Developer Client, which now supports both nos:// and https://.

The protocol will soon be integrated with the nOS Name Service, a specialized domain name service for the nOS ecosystem, along with support for Chrome and Firefox.

You can view a complete list of features here on Github.

The report also introduced documentation on how to deploy the Master Contract Token (MCT) to the nos-local environment.

MCT is an NEP-5 compatible token implementation; the token’s purpose is to enable automatic exchange of value between smart contracts and users, thus solving a limitation of NEO’s smart contract code.  You can read a full description of how MCT tokens work and why they were introduced here, and a tutorial for deploying it to nos-local at this link.

There were also a large number of bug fixes made to the nOS client that can be viewed here.

More information on nOS can be found at the following links.

Tags: