Crown Core staging tree 0.12
master: 
v0.12.0.x: 
v0.12.1.x:
Copyright (c) 2009-2015 Bitcoin Core Developers
Copyright (c) 2014-2017 Crown Core Developers
What is Crown?
Crown is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. Crown uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Crown Core is the name of open source software which enables the use of this currency.
For more information, as well as an immediately useable, binary version of the Crown Core software, see http://crown.tech/wallet.
License
Crown Core is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.
Development Process
Bug Reporting
Bugs can be reported via the github issues page: https://github.com/Crowndev/crowncoin/issues or emailing support@crown.tech
Merging and Updating
- A Pull request is submitted.
- It will then be reviewed and tested by the Crown development team.
- After initial code inspection and internal testing the update will be deployed to the testnet for public testing.
- A minimum of 15 days of testnet function per upgrade is required to fully validate and test the upgrade.
- Once tested and validated, the pull request will be merged to master code and included in the next update.
Procedures for bounty development
The Crown team will post a request for development and the requirements to receive the bounty reward and the size of the reward. 1.Developers at large can then post their interest in seeking the bounty on github and being developing on the change. 2. Once the at-large developer deems his code complete, they will submit a pull request via ionomy github with the label of the Bounty Feature. 3. It will then be reviewed and tested by the internal development team at ionomy.com. 4. After initial code inspection and internal testing the update will be deployed to the testnet. 5. A minimum of 15 days of testnet function per upgrade is required to fully validate and test the upgrade. 6. Once tested and validated, the pull request will be merged to master code and included in the next update. 7. When the version update is deployed Bounty funds will be released to the developer of the completed feature.