Skip to content

Development plans

Jump to bottom Edit New page
dnotestein edited this page Feb 4, 2014 · 11 revisions

Table of Contents

Near Term Release Plans

On-demand Releases

We will put out small updates in a rapid manner to address any serious bugs reported during alpha testing.

Setup Continuous Integration builds?

If I'm interpreting this correctly, we can setup a free CI builder using Travis CI for our github projects (I think it's free because we're not using a private repo).

Would be nice to set this up to build at least the Linux version, and also for other platforms if possible.

Milestone 1: Keyhotee with functioning blockchain

We're tentatively targeting Feb 28th for this release. Primary desired features for this version:

  • Stable process for creation/re-creation of profiles and new identities (likely done, still needs a little more testing).
  • Profile Database versioning mechanism to enable migrating existing profiles to new version of KH as they are released in the future.
  • Elimination of nearly all GUI bugs involved with contact editing and display, sending/receiving emails, and viewing of emails.
  • Fully enabled GUI for setting mining intensity and mining new KeyhoteeIDs
  • Compression of emails prior to encrypting/sending (done)
  • Proof-of-work required to send emails as spam-limiting system (code is written but not currently enabled, needs tuning and final validation).
  • Mined kID-blocks will be sent to the mail server, which will validate the blocks, and then send them out to all the Keyhotee clients. The clients will only accept blocks from the server into their blockchain, which will eliminate the need for any blockchain synchronization in this release.
  • Separate program to create KH genesis block from Founder Id registration database. Possibly this can be done with a bounty, but we need a backup plan to execute if no one takes it up quickly.
Reviewing the current issues in Github, most of the potential blockers for this release are in the back-end code. Therefore if all the GUI-side features for this release get completed before the back-end code is ready, the GUI developers should proceed to features needed for the next release. The next goal will be to fully enable basic instant messaging support, so this means adding support for contact authorization requests and request acceptance to the GUI.

Other planned features that we can start investigating include support for wallet functionality. Lightweight wallet functionality can be implemented via requests to blockchain info websites or via a JSON-RPC connection to a locally running wallet client. We still need to design what the GUI interface for this is going to look like and figure out which milestone to fit it in. This is another good potential bounty job, but we need to pick it up quickly if no one wants to take it on, since this is a blocker for release of the blockchain.

Milestone 2: Enhanced blockchain functionality

  • Support automatic expiration of non-founder kIDs on a yearly basis, requiring occassional re-mining by the kID holder to maintain their ID. This prevents KH users from squatting on a lot of IDs.
  • Ability for user to "revoke" any of their kIDs (issue a transaction that forces a near term expiration of their kID).
  • Support changing the public key associated with a kID.
  • Enable instant messaging support (most of this works, but is currently disabled)

Milestone 3: Decentralized blockchain

  • Peer-to-peer overlay network
  • Blockchain synchronization in case of forks (implemented, but not stable)

Long Term Feature Plans

Add a custom footer
Add a custom sidebar

Clone this wiki locally