Crown Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - defunctec

Pages: [1]
General Discussion / CrownPi Home hosting
« on: May 27, 2018, 02:31:47 pm »
What is CrownPi?


CrownPi started as a home project with one objective - to safely host Masternodes from home.

CrownVPS have developed what we believe to be the best method to date for home hosting, and are now offering this solution via a new and unique product, CrownPi. We hope that CrownPi will appeal to those that are also interested in the decentralisation home hosting can provide.
By using a VPN, more than one node can be run from home using CrownPi. This is because the IP used to connect to the Crown network belongs to the VPN, rather than your home network.
Example of home setup (8 online):

The CrownVPS team have been working with masternodes since the advent of Dash - around 4 years.

We currently host over 100 VPS for the Crown community via third party server providers; however, we hope to host some of these servers locally using the CrownPi software in the near future.
Understanding CrownPi

Currently only NordVPN can be used with CrownPi but we plan to introduce many more VPN providers in the future
The software is designed in a way that makes it easy to setup and maintain the CrownPi, though you would benefit from a basic understanding of Linux command line and how to create a Masternode.
The CrownPi has a copy of the Crown blockchain and will create a new wallet on initial start up.

OpenVPN will also try to connect to a VPN, but will be unsuccessful until you enter your VPN login details into the appropriate file.

These are the two main attributes of CrownPi. Together they provide a 'VPS-like' server which uses a VPN to hide the home IP of the server, thus making it safe to host multiple nodes from home.
Once setup correctly, the CrownPi will automatically reconnect to your selected VPN if the connection is lost or the device restarted. If you use NordVPN, the chances of the VPN IP address changing are small when reconnecting. CrownVPS currently recommends using NordVPN with CrownPi.
You may only use one IP address per Crown Masternode. NordVPN alone have over 4000 IP addresses that can be utilised, so if you do conflict with someone, it won't be long until you find an IP that is available.

CrownPi is also currently setup to use Private Internet Access and IPVanish, however be mindful that if connection to either of these services is lost, the probability of the IP address changing on reconnection is higher than NordVPN.
Stability is priority with a Masternode - if the connection drops or power to the CrownPi is inadequate, you will have stability issues.

We started with 1 CrownPi to make sure the idea worked, a few minor issues later and the node was live.

We then added 2 more CrownPi devices, using different VPN server details and ran these for two days succesfully.

Our current setup (see image above) is 8 nodes, all using NordVPS. The first CrownPi has been online for over 5 days and has received multiple rewards. The other 7 have been online for just over two days now.

Recommendations & Restrictions
You need enough power going to each device, 1.0A / 5V minimum is recommended. You will have stability issues if not enough power is provided.

You can only use one VPN IP per device, if someone else is using the same IP, you will be unable to connect.

One node only per CrownPi device.

Make sure to use quality wiring with appropriate power outputs, old loose wiring could cause instability.

If hosting several CrownPi's buy a ethernet switch.

Monitor and keyboard are needed to obtain local ip of the device.

There could be a better solution to home hosting, therefore we encourage anyone interested in home node hosting to experiment with CrownPi and their own implementations. Please share these here, we would be very happy to hear from you!

We are offering ongoing access to CrownPi development via our shop.

If you already have the equipment, you can buy a one off package that gives unlimited access to any .IMG file the CrownVPS team creates. You will also benefit from unlimited usage of the .IMG file.
If you have any questions, you can create a ticket at

General Discussion / What is CrownPlatform?
« on: May 15, 2018, 06:27:21 pm »
Introduction to Crown and CrownPlatform

Crown at a glance:


3.6 - MINING



- Crown is a fork of Bitcoin that was created in 2014 and underwent a community takeover in March 2016. It can currently be merge mined with Bitcoin.
- Crown features two incentivised node layers: Masternodes for transaction processing, as well as Systemnodes for application hosting on the upcoming CrownPlatform.
- Crown also uses a governance system which operates in a similar way to Dash.
- Due to the nodes and governance, it is often wrongly assumed that Crown is a fork of Dash. This is not the case, and is one of the things that makes the project unique.
- Crown decided that in order to deliver a global application platform, the blockchain should be more transparent. Darksend was therefore disabled in 2017.


The primary objective is to build an application platform on which users can ‘hook into’ the Crown blockchain by utilising the existing systemnode layer. This will eventually provide access to API tools that can be used to communicate with the Crown network. Benefits of this are that there will be no code language limitations on applications or websites hosted on the systemnode network (unlike Ethereum, for example). Systemnodes are essentially empty Linux servers, which means it is possible to implement or migrate code for new and existing services with relative ease.


Many application platforms are currently under development and are taking different approaches to their respective products, so it is easy to miss what Crown are working toward. Initial Coin Offerings tend only to offer a single use case, as opposed to Ethereum, which is currently dominating the application space.

Ethereum does have it’s issues, though; one factor that could limit long term adoption is their proprietary code base, Solidity, which few programmers are proficient in (compared to alternative coding languages). This could potentially restrict the rate at which new and existing services proliferate on the network, resulting in Ethereum falling behind as more universal application platforms begin to emerge. There will be no coding language prerequisites for access to CrownPlatform. It is expected that programmers will be able to work within their desired codebase and will only be limited by the type of server they choose to be hosted on and the API tools available.

Perhaps the most controversial issue surrounding Ethereum is whether it will be classified as a security by the U.S. Securities and Exchange Commission. It has been anticipated by the Crown team for some time that global financial authorities would begin to draw distinctions between fairly launched cryptocurrencies, pre-mines and ICOs. Crown was fairly launched in 2014 with no pre-mine or ICO, so is not exposed to this risk.

Crown takes the approach that regulations and legal accountability structures already exist around the world, therefore the network should facilitate compliance with these where practicable. As a result, a carefully planned registration and ID verification process have been cemented into the development path of CrownPlatform. This process aims to dissuade nefarious activity on the network; furthermore, it transfers the risks associated with illegal operations away from the network as a whole, placing them instead with the ID verifier, application provider and systemnode owner hosting that particular application.

Should you do not want to participate in the network registration process, that is entirely your decision! You can still host your masternodes and systemnodes as usual and generate block rewards. This procedure is only required if a business (or individual) wishes to provide hosting for CrownPlatform applications, or would like to rent space from a host in order to run a CrownPlatform application.


Crown envisages an ecosystem of responsible and accountable entities that carry out their affairs while observing the law of their respective jurisdictions. Systemnode owners that wish to offer services on CrownPlatform will be required to apply for verification from special ID verifiers that are appointed by the governance system. Application providers will also require the same verification in order to operate.

This process will include a user agreement between the parties that fully encompasses the obligation to comply with any relevant laws that the parties may be governed by. The verifier may also request that candidates produce their company or personal information, contact address, phone number, email etc.

Once the verifier is satisfied, a unique verification hash will be issued to the successful candidate. This hash (and the network privileges associated with it) can be revoked if the verifier finds there to be any activity that is illegal or unlawful.

To become a verifier it is necessary to submit a special type of proposal to the governance system and obtain permission from the Crown network. Ideally, the verifier role should be undertaken by data management professionals that are competent with storing and handling sensitive information. Network participants may at any time vote against the verifier if they are seen not to be fulfilling their duties. Verifiers will likely charge a fee for their services and will operate independently as individuals, businesses or charitable organisations.

Crown hopes to see large demand for obtaining verification on the network, which could potentially make the ID verifier position itself lucrative, enticing more competition into the market and driving up service standards. It is recommended (but not necessary) that CrownPlatform users obtain a minimum of 3 unique verification hashes. Having a greater number of unique verification hashes provides more assurance that you will not lose access to the network if any of these hashes are revoked (as a result of an ID verifier ceasing to exist, for example).


All CrownPlatform users are responsible for conducting their business in accordance with any laws or regulations that may apply to them.

ID verifiers assume some degree of responsibility for ensuring that users they have verified are using the network for its intended purpose. If a verifier suspects any illegal activity, they should take reasonable measures against such activity (e.g. revoking the users unique verification hash, filing a report with any relevant authorities, etc.).

Should an ID verifier fail to carry out its duties in a manner that is satisfactory, the onus is on the network to vote ‘no’ on that particular verifiers ‘special’ proposal in the governance system. Once enough ‘no’ votes have been cast, the verifier will lose the ability to issue new unique verification hases, and any that have already been issued will be rescinded.

Use Case Example #1 - VPS Provider

An existing VPS provider purchases 500 CRW and creates a systemnode, then registers their business in order to obtain a unique verification hash for their systemnode. They migrate their servers over to their new systemnode and are now able to utilise the API tools available on CrownPlatform.

The VPS provider uses their own code (e.g. OpenVPN) to manage and partition the systemnode server into smaller virtual machines which are then rented out to provide revenue. The VPS provider employs login and payment API tools that enable customers to create and manage their account, as well as settle invoices using Crown as the payment vehicle. Benefits of this application include the potential to fully automate the business and receive block rewards from hosting a systemnode to increase profits of subsidise the business.

Use Case Example #2 - Gaming Server

A online gaming server purchases 500 CRW and creates a systemnode, then registers their business in order to obtain a unique verification hash for their systemnode and their application (the gaming server). They set the server up to use the block reward obtained from the systemnode to fund tournament winnings and events. Additionally, the business could create a community website for users to see things like player statistics, tournament results and any other relevant information. Advertising could be sold on this website to provide additional revenue.


Some key functionality that Crown’s API tools will enable include:

- User account creation (sign up/login using a public key/username and password).
- Crown blockchain can be used to record and process transactions.
- Multi-signature escrows can be used utilised to facilitate payment terms agreed between parties.

This list is not exhaustive - the Crown team believes the potential number of API tools that could be developed in the future is innumerable.

Recap: Questions & Answers

Q1: Why do systemnodes require verification if they want to offer services?

A1: The network needs a way to manage and respond to illegal activity. The ID verifier will confirm the identity of the individual or business, then create a hash of any documentation. The verifier should take reasonable measures to prevent illegal actions, including revoking a users unique verification hash.

Q2: Why trust ID verifiers?

A2: ID verifiers are bound by the laws of the jurisdictions they operate in. Some due diligence will be required when selecting which verifier to submit your personal information to. Try to use verifiers from jurisdictions with strong data protection laws.

Q3: Why move my website to a systemnode instead of a standard VPS?

A3: A standard VPS is essentially a blank canvas, whereas a systemnode offers the option of accessing the CrownPlatform API tools. If you also run the systemnode you will earn block rewards, too.

Q4: What is the relationship between systemnodes and applications?

A4: Application providers can host their services on the systemnode network once they have been verified by one of the networks ‘special’ ID verifiers. The application provider would agree to the systemnode owners terms of service.

Q5: Who controls CrownPlatform?

A5: No one entity will have control over the network, Crown will be completely decentralized.

Q6: When will CrownPlatform be ready?

A6: The Crown team are currently working on upgrading the network from Bitcoin Core 0.9 to 0.16. Governance being overhauled away from bug ridden Dash code. Once this work is complete, work on CrownPlatform will begin in earnest with testnet expected to be running in late 2018/early 2019.


The Crown team have unveiled plans to move network consensus from the existing Proof of Work system (PoW), to a new type of Proof of Stake (PoS) system. A proposal to change consensus in this way has been submitted to the governance system for consideration. This proposal currently has enough yes votes to pass and work will begin once this is confirmed after the voting deadline.

The proposed PoS system will rely on masternodes and systemnodes to form consensus on the network. The current 3.6CRW mining block reward will be distributed between both node networks once PoS is implemented.

Currently, block reward distribution looks like this:

Miner         3.6CRW   (Collateral: N/A)
Masternode      4.5CRW   (Collateral: 10,000 CRW)
Systemnode   0.9CRW   (Collateral: 500 CRW)

System-nodes actually a generate a greater block reward than masternodes, relative to the initial collateral requirement for each. As indicated above, one masternode will generate 4.5 CRW per block - however the same collateral could run 20 systemnodes which would instead generate 18 CRW per block. This is a deliberate action in order to incentivise smaller holders to create systemnodes that will support the upcoming CrownPlatform.

Once the new PoS system is implemented, the block reward distribution is expected to be as follows:

Masternode      7.38CRW   (+2.88 CRW)
Systemnode   1.62CRW   (+0.72 CRW)

This is expected to have a significant impact on node counts, creating a much stronger network for the new PoS system to thrive. Collateral requirements will remain the same.


Many third party services accept Crown or offer statistic services to the community:

Main Exchange
Bittrex -

Crown Central -
Crown Today -
Official Block Explorer 1 -
Official Block Explorer 2 -
Chainz Block Explorer -
Masternodes Pro -
MN Rank -

NodeVPS -
CrownVPS -
NodeSupply -
Stke -

Ideas / Voting tick box's to vote many on many.
« on: December 19, 2017, 05:14:59 pm »
Tick boxes next to proposals. Many box's can be selected at once.

Ability to vote yes or no on exactly the ones you want to vote on.
Instead of doing this process one by one, you click 10/12 proposals Yes,
click vote many to cast 'vote many' on 10/12 of the proposals.
The other 2 can then be clicked and voted no or abstain together

Ideas / Add "Proposer Name" to proposals.
« on: December 19, 2017, 05:08:49 pm »
Would it be possible to add proposer name to the governance system?

To see in the voting GUI who exactly made the proposal.

Pages: [1]