<commit_before># Crown 0.13.0 Release Notes

Crown Core tree 0.13.x release notes can be found here:
- [v0.13.0](release-notes/crown/release-notes-0.13.0.md)

Crown Core tree 0.13.x was originally forked from Bitcoin Core tree 0.10.2

Bitcoind can now (optionally) asynchronously notify clients through a
ZMQ-based PUB socket of the arrival of new transactions and blocks.
This feature requires installation of the ZMQ C API library 4.x and
configuring its use through the command line or configuration file.
Please see docs/zmq.md for details of operation.
>>>>>>> 6e18268... Switch to libsecp256k1-based validation for ECDSA
<commit_msg>initial stab at Jade release notes<commit_after># Crown v0.13.0 (Codename "Jade") Release Notes

Crown Core v0.13.0 is a major release and a mandatory upgrade.

It features 2 main changes over the previous v0.12.5.x version:
* new address prefixes
* switch from Proof of Work to Proof of Stake
 

## New address prefixes
When Crown originally forked from Bitcoin it retained the Bitcoin address format. 
Nowadays that is not a desirable legacy because it prevents use of Crown with 
hardware wallets such as Ledger and Trezor. Thos devices cannot distinguish 
between different coins with the same address prefixes.

v0.13.0 introduces new prefixes for both mainnet and testnet. 
Mainnet addresses now begin with the prefix "CRW", eg:```CRWP934B9FbM5RaTUfT7zCH12a259j4PYbSE```
and testnet addresses now begin with the prefix "tCRW", eg:```tCRWZpkQ8aJ4wyWx5MiZup23WG8aw5JmKRAaQ```

These unique and distinctive prefixes will enable the use of Crown with hardware 
wallets. We hope to see the first integration soon. 
The change is friction-free from the user's perspective. Users who upgrade won't 
need to do anything to explicitly convert their old wallet addresses.   
blah blah blah

## Block generation change from Proof of Work to Proof of Stake
New address prefixes are a substantial change but are dwarfed in scope by the
change from Proof of Work (PoW) for block generation to Proof of Stake (PoS).

Proof of Work is a computationally intensive process which consumes a lot of power.
Proof of Stake is more environmentally friendly and removes the block generation
process from miners and gives the task to stakers instead.

Several dozen coins have already made this change but Crown's implementation is 
unique and has several advantages. The first coin with PoS was Peercoin which
used a combination PoW/PoS implementation. Blackcoin was the first PoS-only coin.
The majority of PoS coins rely on hot-wallet staking and have some dependence on
coin-age or wallet balance to decide which node wins the right to generate the 
next block and receive the block reward. Hot-wallet staking means the user's 
wallet must be online and open to stake.

The Crown implementation was designed and built by <NAME> (@presstab) at
<company name> over a period of several months. It features cold-staking on the
masternode and systemnode network. Users do not need to keep their wallets open
and online in order to stake. Instead, their collateral balance(s) is/are 
delegated to their masternode(s) and/or systemnode(s) to be staked there.

Contemporary staking systems generally work on the entire balance of a user's
wallet. Thus in a contemporary system a user with 100,000 coins in their
wallet stakes with all of them. 
The Crown system works only on coins locked as collateral in masternodes
or systemnodes. This encourages users to support the network by running one or
more nodes in order to ensure they get a share of the staking rewards. 
In the Crown system a user with 100,000 coins in their wallet only stakes with 
the ones locked in a masternode or systemnode. If they choose not to support the
network by not running any nodes then they have no chance to earn staking rewards.
If they lock all of their coins in masternodes or systennodes then all of their
coins are eligible to earn rewards. Therefore the minimum wallet balance which
can stake is 500 coins and those coins must be locked as the collateral for a 
systemnode. 

more blah blah blah about our several advantages including fake stake threat 
and how it's not an issue for us.

### The switchover
The switchover from PoW to PoS will take place at block height 2330000, approximately
2 weeks after release of v0.13.0.
This will allow time for users and exchanges to upgrade and get accustomed to the
new address prefixes and for the network to stabilise. At a dynamically determined
block height (about a day before the consensus change kicks in) nodes which have
not upgraded will be excluded from the network by activation of a spork. Nodes
which have upgraded will continue on the network uninterrupted. The network will
have time to stabilise again until at block height
2330000 it will say goodbye to the miners and the first PoS block will 
be generated by one of the masternodes or systemnodes.
The block generation time will remain 1 minute, as it is now. Every minute a
masternode or systemnode will generate ("mint") a block and share it with the
network. The node will be rewarded for it's efforts with a minting reward. 
This replaces the reward previously given to the miner which generated a block. 
The node will also pay the usual per block masternode and systemnode rewards.

### PoS FAQ
1. How much can I earn through staking?
2. What's the minimum amount of Crown required for staking?
3. What do I have to do to enable staking?
4. Do I need to keep my wallet open to stake?
5. What about the much publicised fake stake attack vector?
6. What if I have a gazillion coins but don't want to lock them all up in masternodes or systemnodes?
7. 


## Changelog
Possibly include changelog here or make it a separate file for ease of maintenance.
{'fraction_non_alphanumeric': 0.03499047289104452, 'fraction_numerical': 0.019227438073791788, 'mean_word_length': 4.366171003717472, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 12, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2840339', 'n_tokens_mistral': 1595, 'n_tokens_neox': 1478, 'n_words': 926}