Author Topic: 200 PTS - Technical Specification for Keyhotee ID Blockchain [ACTIVE]  (Read 3498 times)

0 Members and 1 Guest are viewing this topic.

Offline barwizi

  • Hero Member
  • *****
  • Posts: 764
  • Noirbits, NoirShares, NoirEx.....lol, noir anyone?
    • View Profile
    • Noirbitstalk.org
I would like to try. Where should i submit the doc?


Sent from my iPhone using Tapatalk

Post a link to a google doc in this thread.

I have an interest in this as well.
--Bar--  PiNEJGUv4AZVZkLuF6hV4xwbYTRp5etWWJ

The magical land of crypto, no freebies people.

Offline bytemaster

I would like to try. Where should i submit the doc?


Sent from my iPhone using Tapatalk

Post a link to a google doc in this thread.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline BTSInvestor

  • Jr. Member
  • **
  • Posts: 20
    • View Profile
I would like to try. Where should i submit the doc?


Sent from my iPhone using Tapatalk

Offline bytemaster

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.

For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster

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.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline phoenix

  • Sr. Member
  • ****
  • Posts: 275
    • View Profile
How detailed should this design paper be? Should it deal with all the specific details, or mostly focus on a broad overview?
Protoshares: Pg5EhSZEXHFjdFUzpxJbm91UtA54iUuDvt
Bitmessage: BM-NBrGi2V3BZ8REnJM7FPxUjjkQp7V5D28

Offline bytemaster

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.
« Last Edit: January 09, 2014, 08:05:48 pm by bytemaster »
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.