Topic: [ANN][CRW] CROWN (SHA256) | Platform | Governance | Systemnodes | Masternodes | - page 108. (Read 317079 times)

I Luiz,

be great if you could join our private chat if you want to get involved and get to know the team and its plans.

But let me answer a bit, our third way is a situation where miners do not play a key role in the distribution of coins and keeping the network safe, since mining coins is not the most efficient way to sustain a blockchain 2.0 project. In our plans Thrones or Trons masternodes will be playing a much important role.

Let me paste here a text which will be online on crown.tech in the next few days concerning Trons:

What is a TRON?
The Crown platform utilizes masternodes called TRONs.  The minimal requirements for running a masternode are to just have a small compute session which is always on and connected to the network, and load the Crown software on it and set some configuration files up with some keys to confirm that you have the required 10,000 CRW collateral on the blockchain.
TRONs are still under development, but the TRONs on the Crown network server to:
Secure and stabilize the network and transactions.  
For those interested in how this works, there are ways that network security can be accomplished using mathematical properties which don’t involve mining algorithms, but functionally leverage randomness and network topology.  These techniques are used by a variety of different systems, from WeChat to Zookeeper -- just look up the Paxos Algorithm and go from there.  The Dash paxos implementation with InstantX is an elegant example.  
The network is secured by both the TRONs and merge-mining.  We like having multiple layers of security.

Provide another layer of governance.
TRONS will be able to make and vote on proposals for allocating the 10% of the block rewards which has been held back since the last code update in February 2017.  None of the funds held back from the block rewards have been allocated yet, and the existing development fund is composed of tokens contributed personally by members of the core team so that the project would have the resources to get to the point at which TRON voting would be turned on.  This code is in place and it is just a matter of turning it on this function that the platform inherits from Dash in the next update.

Provide Application Developers and TRON Operators with Business Opportunities
Once the API is developed, developers will be able to integrate Crown API calls and package applications which TRON operators would be able to offer to users managing the provisioning of compute resources, and payment for the application, through the Crown API in concert with other API’s or development tools.  TRON’s are, in a sense, franchises to operate a cloud application business running open source applications and accepting payment denominated in CRW.
The overall goal of the project is to do something useful with crypto.  The first use is to see if we can create an application economy running a cloud of open source applications.  The TRONs are the backbone to the Crown Cloud, which doesn’t exist yet – but which we hope to work with the community to build.

Why TRON?
Well… we needed a name.  Tron is close to the old name for the servers, throne – but a “tron” is active and not passive, and “tron” refers to the history of crypto where Hal Finney was involved with building the Atari game The Adventure of Tron.  
The key idea is that TRONs are active server nodes on the network.  A TRON can generate revenues by confirming transactions on the network – but it will also be able to use the Crown API, alongside other API’s to allow developers to build other businesses as well.

Which is the third way quoted in STAGE 1 in >>> http://crown.tech/crown-revolution