Only by learning our history we can see our future.
November 2013 – Four Bitcoin enthusiast dream about launching a coin called Crowncoin. It all starts with a name and logo.
October 2014 – Crowncoin was fairly launched as a Bitcoin fork, not pre-mined, no ICO. bitcointalk.org >
November 2015 – BTC merge-mining (Auxpow - auxiliary proof of work) implemented. bitcointalk.org >
February 2016 – Timestaping feature (inspired by Namecoin) implemented, enabling first experimental timestamps on the CRW blockchain.reddit.org >
July 2016 – A Dash based Masternode model implemented (1MN=10k CRW). bitcointalk.org >
October 2016 – Crowncoin is renamed to Crown.bitcointalk.org >
March 2017 – Crown listed on Bittrex. bitcointalk.org >
June 2017 – Crown governance system / masternode voting was implemented to democratically fund project development. bitcointalk.org >
November 2017 – A second node layer – Systemnodes (500 CRW) implemented. bitcointalk.org >
July 2018 – Crown core architecture documentation was published. Docs >
September 2018 – Crown was listed on the largest Korean exchange Upbit. Medium.com >
March 2019 – Crown makes successful transition from BTC merge-mined POW to an industry leading and environment friendly Masternode Proof of Stake consensus system (MNPoS). Medium.com >
June 2019 – Non fungible token framework (NFT) specification released. Medium.com >
March 2020 – Crown releases its NFT framework into mainnet. Medium.com >
July 2020 – Update of Crown Electrum wallet and full functionality with Trezor implemented. Docs >
August 2020 – This feature extends the Bitcore API to include NFT framework functionality.GitHUB >
Bringing in all useful features, enhancements, bug fixes, and performance improvements from the bitcoin core codebase. Some of these include:. 1. Compiler updates. 2. Memory performance improvements. 3. Block and transaction handling. 4. Build system updates. 5. Unit tests. 6. Fixes for: transaction malleability, fee sniping and more. 7. Bitcoin Scripting language upgrade
. 85% complete1. Deterministic masternodes lists are fully derived from on-chain data (every participant in the network knows and agrees exactly what the active set of nodes is). 2. In the current Crown node model, nodes pass messages back and forwards between themselves and eventually mostly agree on what the current set is. But different nodes/wallets can see different sets. 3. Deterministic nodes store data on the chain instead of talking to each other, so anyone can generate a node list at any time and come up with exactly the same answer. 4. A deterministic MN model cuts down on network traffic, provides better consistency and reduces the possibility of phantom nodes.
initial community discussion / designDevelopers can already start building with the NFT framework, but in order to simplify the process for Javascript developers this feature extends the Bitcore API to include NFT framework functionality.
design document to be drafted by Artem