Atomic Explained

CROWN ATOMIC invites enterprising individuals to build new economy applications running on the Crown code. One of its goals is to support its fast growing community in their path towards creating a new application economy model, which is about much more than just a token.

Learn more about Atomic
A

API driven Model

Crown Atomic is a description of separate pieces of work which enable different functions/uses on the platform. Crown Atomic adds an API to the Crown network for businesses to use the existing Tron Masternode structure.

Trons are blockchain based companies

Some of the applications running on the Crown platform will be persistent or continuous and some will be temporary, or ephemeral. All applications running on the platform will be managed by the Trons.

Not congesting the CRW blockchain

Open source projects will have the option to have their applications run on the Crown network with the Trons providing and managing the resources the application requires.

Verification and Billing

Proprietary projects will be able to utilize Crown for user verification and billing, but will not have the option to run their code on the network.

Easy communication

Applications will be able to communicate with the Trons managing the server level of the network and application resource provisioning, as well as the application user.

NO to anonymity

The Crown code does not support anonymous features such as Darksend

All applications running on the platform will be managed by the Tron masternodes. It will mainly consist of the following two elements.

Chronos staking nodes with NTP servers and a new consensus protocol will enable greater speed and transaction capacity on the network by keeping a more precise sense of time and use the network topology instead of mining to secure the network. This will allow for similar transaction speeds and capacity to PayPal. These Chronos nodes will be rewarded in a similar fashion to Trons, but will only require 100 to 500 CRW as collateral.

The API and new key registration and de-registration op_codes will enable the registration of services on the network the initial keys will be keys identifying application services, and the API will be used for the masternodes to be able to communicate with application services which they are offering to subscribers. The blockchain will basically be the user list and verify payment of users and the keys will be used by paid subscribers to log in to the service. Payment for services will be in CRW and in order to use the API you will need to be a verified Tron on the network. Each masternode will functionally be its own software vendor.