Commit 0014d1be authored by Josh Wilcox's avatar Josh Wilcox

Update roadmap.md with markdown formatting and remove outdated info re: Trezor and UI overhaul

parent cbb2e63c
CROWN PRODUCT ROADMAP # CROWN PRODUCT ROADMAP - Summer 2018
1. CORE UPGRADES ## CORE UPGRADES
Bringing in all useful features, enhancements, bug fixes, and performance improvements from the bitcoin core codebase. Some of these include: Bringing in all useful features, enhancements, bug fixes, and performance improvements from the bitcoin core codebase. Some of these include:
A. Compiler updates - Compiler updates
B. Memory performance improvements - Memory performance improvements
C. Block and transaction handling - Block and transaction handling
D. Build system updates - Build system updates
E. Unit tests - Unit tests
F. Transaction malleability, fee sniping and other potential vulnerabilities fixes - Transaction malleability, fee sniping and other potential vulnerabilities fixes
G. Bitcoin Scripting language upgrade - Bitcoin Scripting language upgrade
H. P2P and network protocol optimization - P2P and network protocol optimization
I. Wallet improvements (ex. All transactions will use Instant Send) - Wallet improvements (ex. All transactions will use Instant Send)
2. GOVERNANCE ## GOVERNANCE
The voting system that funds community proposals and network development. New features, new voting nodes, and more! The voting system that funds community proposals and network development. New features, new voting nodes, and more!
A. Moving unspent proposal funds to the next budget - Moving unspent proposal funds to the next budget
B. Implement new Systemnode voting ability - Implement new Systemnode voting ability
C. Bug fixes - Bug fixes
D. In-wallet proposal notifications - In-wallet proposal notifications
3. PROGRESSIVELY EVOLVING CONSENSUS ## PROGRESSIVELY EVOLVING CONSENSUS
The part of the network that provides agreement on the order and validity of transactions is the consensus algorithm. Crown is currently secured by Proof-of-Work (PoW) through Bitcoin SHA256 merge-mining, which is Phase 1 of the process to a more energy-efficient form of network agreement and security. Phase 2 is the switch from PoW to Proof-of-Stake (PoS). Phase 3 is the implementation of a newer algorithm that is currently being researched and developed. The part of the network that provides agreement on the order and validity of transactions is the consensus algorithm. Crown is currently secured by Proof-of-Work (PoW) through Bitcoin SHA256 merge-mining, which is Phase 1 of the process to a more energy-efficient form of network agreement and security. Phase 2 is the switch from PoW to Proof-of-Stake (PoS). Phase 3 is the implementation of a newer algorithm that is currently being researched and developed.
A. Migrate network to the PoS algorithm - Migrate network to the PoS algorithm
B. Increase node incentives for Masternodes and Systemnodes - Increase node incentives for Masternodes and Systemnodes
C. Test and implement new algorithm once R&D and testnet auditing are complete - Test and implement new algorithm once R&D and testnet auditing are complete
D. Contracts Notarization - Contracts Notarization
4. REGISTRATION ## REGISTRATION
To become a provider in the Crown ecosystem, an application service must be registered in the Crown blockchain. For this goal, Crown Platform will provide registration agents and other infrastructure. To become a provider in the Crown ecosystem, an application service must be registered in the Crown blockchain. For this goal, Crown Platform will provide registration agents and other infrastructure.
A. Community Delegated Agents - Community Delegated Agents
B. Services Registration - Services Registration
C. Identity Verification - Identity Verification
5. API ## API
The Crown Platform API will be an access point for transacting on the network. With this implementation, network businesses and service providers will have programmatic access to the blockchain, providing easy hookup to user ID verification and payment mechanisms. Developers will be able to program dApps in any language and enable features of the Crown blockchain right in their code! The Crown Platform API will be an access point for transacting on the network. With this implementation, network businesses and service providers will have programmatic access to the blockchain, providing easy hookup to user ID verification and payment mechanisms. Developers will be able to program dApps in any language and enable features of the Crown blockchain right in their code!
A. RPC updates - RPC updates
B. REST implementation - REST implementation
C. Services payment hooks - Services payment hooks
D. Registration system integration - Registration system integration
6. DATA STORAGE ## DATA STORAGE
Decentralized file storage integration like Storj, filecoin, using IPFS or another file system designed for encrypted peer-to-peer distribution. Decentralized file storage integration like Storj, filecoin, using IPFS or another file system designed for encrypted peer-to-peer distribution.
A. dApps hosted on Crown Platform will be able to securely store and distribute files - dApps hosted on Crown Platform will be able to securely store and distribute files
7. TREZOR (95%)
Integration of support the Crown token into a hardware wallet will be a huge advance for CRW token holders in secure cold storage options. Previously only an offline computer or mobile phone or a paper wallet were the only options. The next Trezor firmware update will include CRW support!
A. Crown core software updates
B. Hardware wallet code updates
C. Firmware update
8. NATIVE WALLET INTERFACES
The interaction tool between users and the blockchain, the native software wallets present Crown to the public. In an effort to evolve the professionalism and usability of our features, a professional designer has been brought on to design a new UI that will match the current generation of branding.
A. A complete redesign of the native software wallet interfaces on all platforms by an industry professional
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment