為時1年的時程表(暫不翻譯,反正有興趣的人也不多 lol):
https://v.cash/forum/threads/12-month-timeline.349/1. Microsoft Azure
Submit final pull request to Azure Team for template inclusion for one click deploy on Microsoft's Azure BaaS platform. The exact services to be offered will be revealed at a later date when the time is right.
2. Thin clients
Currently there are 3 tiers of network nodes, full public nodes, firewalled public nodes and non-fully validating client nodes. We are adding a 4th tier "Thin Clients" which will download blocks containing only their transactions by use of remote Bloom Filters. The 1st tier will service up to 350 "Thin Clients" per node. The addition of this 4th tier will allow the network to scale to 100's of millions of nodes with ease.
3. Client Ledger Pruning
This feature has already been implemented but not integrated. Integrating pruning will allow systems to run nodes indefinately where previously storage would become an issue with time. Additionally this allows "non-fully validating client nodes" to continue to protect the network via Proof-of-Stake while using minimal disk space.
4. Streaming Initial Download
Initial syncronisation of the ledger will no longer fully validate blocks that are of N depth. Additionally, blocks will be streamed "in-order" and queued for validation. This will allow the ledger to be downloaded extremely quickly while validating it "in the background".
5. ChainBlender R3 Client Protocol
ChainBlender was designed as a client-side protocol which allows modyfing, adding or replacing blending algorithms without the need for a network backbone upgrade. All existing crypto-currencies with ledger anonymity technology is defeated by obtaining a copy of the wallet file or private keys. With the R3 protocol key flushing will be deployed to permanently destroy any private keys used previously in a blending operations. Key flushing solves two problems: 1. In a hypothetical situation where a Government agency may confiscate a wallet file in attempt to trace transactions the privaye keys required for proof will no longer exist. 2. Wallet size will not grow due to cryptographic key accumulation.
6. Decentralised Governance Protocol
Autonomous governance is key to the long term stability and evolution of a crypto-currency. This will enable technology change proposals, project proposals, salaries, etc all settled "in the ledger" removing the human element and extinguishing politics. All votes will be cast by incentivized nodes guaranteeing that those that vote also hold interest in the project.
7. Wallet Tools
We strongly feel that autonomous wallet management is key to the success of any crypto currency. Moving forward we cannot ask end users to perform operations on their wallet files due to the high risk involved. Instead we will be making available a subset of tools via RPC to fix wallet problems such as "stuck invalid transactions", "rescans", "repairs", "import", "export" and so on.
8. ZeroTime based online gambling.
The worlds fastest crypto-currency gambing platform with no operator risk of a double spend scenario.
9. DWAPI
DWAPI is a Decentralised Web API. It works simply by using encrypted websocket connections to a subset of public full nodes. Once connected transactions can be sent in raw form without the need to run a node of any type. The DWAPI can be easily extended to perform complex operations with ease.
10. Thin Client's with ZeroTime protocol support.
When thin-client support is deployed to the backbone we will be integrating ZeroTime into several already available thin-clients such as BreadWallet and Electrum.
11. Fix any known bugs and memory leaks.
No description required.
12. Patents and Trademarks
File all provisional patents and trademarks in the USA under a not for profit organisation.
13. Hire a dedicated web development and art staff.
No description required.
14. Hire more C++ engineers.
No description required.
15. Hire a fulltime public relations manager (candidate is already chosen).
No description required.
16. Mass deploy client/mobile nodes.
For the time being our Android and iOS "non-fully validating" wallets are not available in Google Play or Apple's App Store but you can use them via other means. Once we have "Thin Client" support we will deploy both types of node wallet's in mass to all application storefront's.
17. Deploy the Whisper protocol.
No description required (source code is in github).
18. Come out of Beta phase.
No description required.
* This is a mid-level overview that will continue to be updated in the coming weeks. Additionally as the crypto-currency ecosystem matures items may be updated/expanded/added but NOT removed unless due to obsolescence. Some details/items have been purposely withheld due to competition reasons and will be added when the time is right.
** This timeline starts promptly on day 21 of March 2016 and ends the same day in 2017.
Last edited: Saturday at 8:02 AM
john-connor, Thursday at 12:54 AM #1
