BitShares Forum

Other => Graveyard => Marketplace => Topic started by: bytemaster on December 28, 2013, 08:23:54 pm

Title: 200 PTS - Technical Specification for Keyhotee ID Blockchain [ACTIVE]
Post by: bytemaster on December 28, 2013, 08:23:54 pm
The Keyhotee ID blockchain is currently defined in the code with some basic documentation describing the fields and how it is supposed to work.   This bounty is for someone to reverse engineer a detailed design document from the code.  This document should clearly outline everything necessary to build a compliant clone in a new language. 

The document should be written and developed publicly in a github repository and must be done with professional style and formatting in a format that is mergable.   The first solution I find accurately and completely defines and describes the spec for the Keyhotee ID blockchain will win the bounty.

If a submission contains contributions from multiple parties (likely as teams can producer more faster) then all parties must agree among themselves how to divide the bounty.  I highly encourage cooperation.

This bounty is in the PENDING state while questions are asked/answered regarding the full scope and requirements.  There is also a 1 PTS bounty for referring the winners of this bounty to the bounty.
Title: Re: 200 PTS - Technical Specification for Keyhotee ID Blockchain [PENDING]
Post by: phoenix on December 28, 2013, 08:53:39 pm
How detailed should this design paper be? Should it deal with all the specific details, or mostly focus on a broad overview?
Title: Re: 200 PTS - Technical Specification for Keyhotee ID Blockchain [PENDING]
Post by: bytemaster on December 28, 2013, 09:03:23 pm
How detailed should this design paper be? Should it deal with all the specific details, or mostly focus on a broad overview?

It should be detailed enough that someone could write code to implement it from the specification.
Title: Re: 200 PTS - Technical Specification for Keyhotee ID Blockchain [PENDING]
Post by: bytemaster on December 28, 2013, 09:05:11 pm
How detailed should this design paper be? Should it deal with all the specific details, or mostly focus on a broad overview?

It should be detailed enough that someone could write code to implement it from the specification.

In particular, it should be compatible code.   Part of this effort is to make sure we don't have design holes prior to launching Keyhotee ID blockchain.  So if we missed something we may change our design slightly and this document would be the official design document that our code should conform to.

Title: Re: 200 PTS - Technical Specification for Keyhotee ID Blockchain [PENDING]
Post by: BTSInvestor on January 03, 2014, 04:46:07 am
I would like to try. Where should i submit the doc?


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Title: Re: 200 PTS - Technical Specification for Keyhotee ID Blockchain [PENDING]
Post by: bytemaster on January 03, 2014, 04:41:48 pm
I would like to try. Where should i submit the doc?


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)

Post a link to a google doc in this thread.
Title: Re: 200 PTS - Technical Specification for Keyhotee ID Blockchain [PENDING]
Post by: barwizi on January 09, 2014, 09:20:19 am
I would like to try. Where should i submit the doc?


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)

Post a link to a google doc in this thread.

I have an interest in this as well.