Draft for a development roadmap and focus areashttp://bitcredit-currency.org/viewtopic.php?f=24&t=653------------------------------
The resources that are available for development ahead are limited. It is therefore important to set a roadmap that is adapted to the requirements from the community. Here below are listed some key areas that have been identified as desired or otherwise are of high priority. There are no order of priority in the list below.
- Add feedback here on what areas you consider to be the highest ranking ones.- Feedback on what other key areas that you think have a high priority are very welcome.- Volunteers for development or other types of support are quite welcome.----------------------------------------------------------------------------
- Bitcredit blockchain explorer Online blockchain explorers are helpful in determining the state of the current blockchain and can be used for many purposes, among them to get an “official” image of which the current active chain is.
- Incorporate newer features from Bitcoin The version of Bitcoin used internally in Bitcredit is 0.9.1. This version was released last summer and several key areas in Bitcoin has seen quite a lot of development since then. These features should be incorporated into both the internal Bitcoin client, and also where applicable, be added to the source code of Bitcredit. These improvements are among lots of others “headers first” blockchain synching, preparations for increased block size and improvements for increased transaction volumes.
- Adding Bitcoin client capabilities Since the client is already downloading and tracking the Bitcoin blockchain adding the possibility to send Bitcoins from the client is quite straightforward. There are also other features of the Bitcoin client that could be incorporated, effectively turning the Bitcredit client into a Bitcoin client as well. Those features would remove the need to store the Bitcoin blockchain twice, if a user also has a Bitcoin client installed. This would actually enable a user to forget about the Bitcoin client altogether and instead use the Bitcredit client for both Bitcoin and Bitcredit.
- Lightweight client For the moment it is not possible to use Bitcredit without downloading a complete copy of the Bitcoin blockchain. This could be a blocker for wider adoption of Bitcredit. A client could be created that mostly uses online sources for verification, thereby simplifying the startup process and removing the storage requirements for the client.
- New seeders and fixed nodes For the stability of the network and for wider distribution it is important to decentralise the process of reaching the network as much as possible. Anyone who wants to volunteer a seeder node or a fixed node should get in contact with the Bitcredit developers for inclusion in the source code.
- Development or integration with exchanges Although this is a process that usually happens naturally with existing exchanges there may be a need to develop better coin exchange into the client, or develop freestanding exchanges.
- Evolve deposit features The deposit process is for the moment a manual one. A miner creates a set of deposits and then starts the miner, which uses the deposits to create new blocks. When the requirement for deposits grow, as the monetary base grows, the need for automated processes to handle deposits will grow as well. A streamlined process to prepare deposits automatically by the miner could prove useful in this situation.
- Develop miner-depositor integration A deposit-based proof-of-work system has two roles participating in the mining process, the miner and the depositor. These two are normally the same entities but as the system evolves, they will probably separate. The miner will provide the hashing power, and the depositor will offer up deposits for a fee taken from the reward. A system where these two roles can find each other and integrate can be built into the client, or be built as a separate miner system. Either way, this will be a natural step in the evolution of the transaction verification process.
- GPU mining A “natural” evolution in hash-based verification are improvements with the purpose of making the hashing process more efficient. The normal development phases are first CPU mining, then GPU mining, where a GPU is more efficient in running simple calculations in parallell, followed by creation of so called ASICs. It may be useful to assist in the development of GPU integration, to level the playfield for newcomers.
- Verification of the claiming process Auditors that can audit the claiming process are welcome. Contact the developers of Bitcredit for a run down of how the system works.